On Wed, 2010-04-07 at 19:41 -0500, Heinrich Taube wrote: > i think i see whats going on. linking fails because im use a function > (lo_bundle_free_messages) in liblo-2.6.0 that is not in your 2.4 lib. > even though ive build my own static 2.6.0 liblo (~hkt/Software/ > liblo-2.6.0/lib/liblo.a )
There is no 2.6.0 version (or "so" name, or anything like that), you probably mean 0.26 (or 0.24). > and have a -L ../liblo-2.6/0/lib in my > linking command the linker itself chooses /usr/lib/liblo.so > instread. Well, if you want to link dynamically the linker does not have much of a choice. I imagine it can't use your own .so because everybody else would run the program and it would fail to link, right? You have to link statically (against your .a static version of the library), but then the program would be bigger. I don't quite remember how you do that, but try not putting a "-llo" statement in the linking phase and including your liblo.a explicitly in the list of things to link. -- Fernando > if i remove -L/usr/lib from my linker command set by hand then I > can build Grace statically linked to my 2.6.0 liblo. im not sure what > the right to do this is. > > > On Apr 7, 2010, at 7:14 PM, Fernando Lopez-Lezcano wrote: > > > On Wed, 2010-04-07 at 14:04 -0500, Heinrich Taube wrote: > >> if i could figure out why l cant link with liblo at ccrma (i can on > >> my ubuntu...) then id be happy to do all my linux builds there > > > > What error message are you getting? > > We do have liblo-devel 0.24 installed. > > > > -- Fernando > > > > > > _______________________________________________ > Cmdist mailing list > [email protected] > http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist _______________________________________________ Cmdist mailing list [email protected] http://ccrma-mail.stanford.edu/mailman/listinfo/cmdist
