On Wednesday 27 January 2010, Chris Cannam wrote: > Also, of course, you might _not_ want to look in either lib32 or > lib64, especially if both exist...
Yeah, that is kind of a tricky issue. I have /usr/lib, /usr/lib32 and /usr/lib64 here. /usr/lib64 is a symlink to /usr/lib, and /usr/lib32 is there for all the random legacy crapola that doesn't work in 64-bit for whatever reason. Searching lib64/ would be harmless here, since it's the same as lib/, but that probably isn't a safe bet for a good practice to perform across all Linuxdom. The suggestion about looking at the LADSPA_PATH environment variable is sound enough, but I don't have that set myself in an out of the box setup. That suggests leading down a road where we have some "Could not find your LADSPA thingummies, please set this environment variable" dialog, and then get massive uproar from userland about the horribly confusing dialog upsetting our »realities« about something or other, because the word "environment variable" needs to be translated to what it truly is (impactulescent dinglefarffle, obviously), and yadda yadda blah. The best thing to do does not seem particularly clear to me. -- D. Michael McIntyre ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
