Andreas Persson wrote: > OK. This is exactly the behavior you would get if you run libgig without > the fix. So, I'm sure that you somehow failed to build or install or > link with the fixed version. Maybe you have an old libgig file in > /usr/lib, and your "make install" installed the new one in /usr/local/lib? > > Line 1888 in gig.cpp should end with +, not with |. That was the whole fix. > > /Andreas
Hi again Andreas You're exactly right. The files in /usr/lib (libgig.so.6 and libgig.so.6.4.0) date from last year. The ones in /usr/local/lib (libgig.a, libgig.la, libgig.so, libgig.so.6 and libgig.so.6.4.0) all date from this evening. As I don't know any better ;-) I've renamed the files in /usr/lib and copied over the files from /usr/local/lib and everything works perfectly now -- again, many thanks for your help. I assume this occurs with anything you compile from source, that it defaults to /usr/local/lib unless you tell it otherwise, causing problems if older versions have been installed elsewhere by other means. (I make this assumption on the fact that all the libraries in /usr/local/lib look to be for the few things I've compiled myself rather than using a package manager for.) How does one solve this problem -- put a link in /usr/lib pointing to the actual library in /usr/local/lib, or at compile time tell it to put the lib in /usr/lib? In either case, how does one do that? Once again, apologies for my naivety and many thanks for your patience and help. Best wishes Q ------------------------------------------------------------------------------ Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d _______________________________________________ Linuxsampler-devel mailing list Linuxsampler-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
