On Sun, Mar 09, 2008 at 11:05:58AM +0000, Artem Pavlenko wrote: > > On 8 Mar 2008, at 12:59, Dominic Hargreaves wrote:
> >http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=468770 > > > >It looks like this might be a problem with boost rather than mapnik > >itself, but I just wondered whether anyone else had seen this problem? > > It looks like mismatched ABIs . Is it possible boost_python and > mapnik were built using different compilers? > > libstdc++6 4.3-20080219-1 --- GCC 4.3 (Mapnik) > > libboost_python-gcc42-mt-1_34_1.so.1.34.1 -- GCC 4.2 (boost) Hrm, Mapnik itself should have been compiled with gcc 4.2 (4.3 is not yet the default compiler in Debian unstable). It looks like this might be related to http://www.python.org/dev/peps/pep-0353/ I wonder if my patch to be Debian-compatible (Debian's amd64 port doesn't use lib64): --- branches/upstream/current/SConstruct 2008-02-24 13:49:55.000000000 +0000 +++ trunk/SConstruct 2008-02-04 18:49:02.000000000 +0000 @@ -23,7 +23,7 @@ import os, sys, platform if platform.uname()[4] == 'x86_64': - LIBDIR_SCHEMA='lib64' + LIBDIR_SCHEMA='lib' else: LIBDIR_SCHEMA='lib' has had some unforeseen consequence. Does this seem likely? Dominic. -- Dominic Hargreaves | http://www.larted.org.uk/~dom/ PGP key 5178E2A5 from the.earth.li (keyserver,web,email) _______________________________________________ Mapnik-users mailing list [email protected] https://lists.berlios.de/mailman/listinfo/mapnik-users
