On Jan 6, 2010, at 10:04 AM, Thomas Woodham wrote: > Sorry, forgot to include that detail. That boost version (1.33) is > a prerequisite for a number of virtual server packages, similar to > Ludwig's situation. I can't get rid of it, though I thought about > pointing all the boost sym links to the propper versions installed > in /usr/local/lib, though that seems to be asking for trouble. I > may go back and reinstall boost and set the prefix to /usr so it > overwrites that version.
Ah, gocha. Well installing latest boost on top of /usr/lib could be bad news for existing applications that are using it. I think the issue is that our SCons implementation stores several default search paths as /usr/lib, so setting the BOOST_LIBS/INCLUDES to /usr/local may not secure the linking because -L/usr/lib is still put on the linkers path. Short of reworking some things in the build scripts to allow forcing / usr/local to come before /usr/ in g++/linker flags, what you can try to do is set the LIBS/INCLUDES for each of 'PNG', 'JPEG', 'TIFF','PROJ','ICU' dependencies to /usr/local (if possible) to ensure that SCons will not default to putting /usr/lib onto the linker. Sorry, for inelegant solution. Dane _______________________________________________ Mapnik-users mailing list [email protected] https://lists.berlios.de/mailman/listinfo/mapnik-users
