Fixed it... I did get the error when I tried it in f14--I'm not sure why the boost libraries would be different on f14, but now the build process detects the problem and should figure out the right thing to do. I'll get a new release tarball out tomorrow. -David
On Sat, 2011-03-19 at 11:11 -0700, Fernando Lopez-Lezcano wrote: > On 03/18/2011 06:07 PM, David Psenicka wrote: > > I just compiled fomus 0.1.15 with boost 1.44 on Ubuntu and had no > > issues... > > I must be doing something wrong then... this is the boost I'm using in > Fedora 14: > > boost-1.44.0-7.fc14.i686 > > Maybe a problem with lilypond itself? > > > I'll have to install fc14 somewhere and try to compile it in > > that environment to figure out what's going wrong. I'm almost sure that > > undefined symbol has to do with the API change in boost 1.44. I'll post > > a solution as soon as I figure this out. > > Very grateful that you are looking into this, let me know if I can help > in any way. > > -- Fernando > > > > BTW the option "--with-boost=/usr/local" on the ./configure command line > > causes it to link with a local install of boost instead of the distro > > version (the boost libs are in /usr/local/lib)--on my machine it > > compiled against the local boost and worked properly (output a lilypond > > file and displayed it). To run it I also had to export > > "LD_LIBRARY_PATH=/usr/local/lib". > > > > On Fri, 2011-03-18 at 14:46 -0700, Fernando Lopez-Lezcano wrote: > >> AFAICT Grace does not link with fomus, I imagine it just calls the fomus > >> executable? > >> > > Grace loads libfomus.so dynamically at run time (the Grace build doesn't > > link with it at compile time)... So recompiling Grace shouldn't be > > necessary, it should load and use whatever version of fomus is installed > > (and run without it if it can't find it)
_______________________________________________ Cmdist mailing list Cmdist@ccrma.stanford.edu http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist
