Re: [linux-audio-dev] Re: MusE 0.8.1 released

Hopefully it's configuration. I'll check for ladcca to be sure.

To answer the previous question, the support is for lash-0.5.0, I've tested it
and it works reasonbly (closing the project leads to a double-delete error in
glibc which I don't know what causes)

---
Also, for some reason lash has a tendency of taking down jack when closing on 
my system (regardless if muse is used). Does someone else see this? I should 
debug this a bit..
Regards,
Robert
On Tuesday 28 March 2006 07:31, Dave Robillard wrote:
> On Tue, 2006-28-03 at 12:21 +1000, Loki Davison wrote:
> > On 3/28/06, Florian Schmidt <mista.tapas@email-addr-hidden> wrote:
> > > Hmm, i don't know what's up with that, but ./configure says "build
> > > without lash support" and lateron it fails:
> > >
> > > /bin/sh ../../libtool --tag=CXX --mode=link g++ -g -fno-exceptions
> > > -Wall -W -D_G
> > > NU_SOURCE -D_REENTRANT   -DQT_CLEAN_NAMESPACE -DQT_NO_COMPAT   -I../..
> > > -I../../m
> > > use/widgets -I/usr/share/qt3/include -I.. -I../../synti
> > > -I../../muse/widgets -DQ
> > > T_SHARED -DQT_THREAD_SUPPORT -DQT_PLUGIN -fPIC -O3 -ffast-math
> > > -fno-exceptions -
> > > g -O2   -o fluidsynth.la -rpath /usr/local/lib/muse/synthi -module
> > > -avoid-versio
> > > n fluidsynti.lo fluidsynthgui.lo fluidsynthguibase.lo
> > > moc_fluidsynthgui.lo ../li
> > > bsynti/libsynti.la -lfluidsynth -lasound -lm -ldl -L/usr/share/qt3/lib
> > > -lqt-mt -
> > > lqui
> > > grep: /usr/lib/libladcca.la: No such file or directory
> > > /bin/sed: can't read /usr/lib/libladcca.la: No such file or directory
> > > libtool: link: `/usr/lib/libladcca.la' is not a valid libtool archive
> > > make[5]: *** [fluidsynth.la] Error 1
>
> [snip]
>
> > What lash is this anyway? is the modern, useful, actually handy for
> > stuff lash as in http://www.nongnu.org/lash/ or the ladcca from dawn
> > of time one?
>
> 0.5.0+ versions of LASH do not contain the phrase "ladcca" in any way
> (including filenames).
>
> >From a quick glance, neither does Muse 0.8.1, so I would assume this is a
> > system
>
> configuration problem.
>
> -DR-