python mapscript compile errors

[Umberto Nicoletti]

You did not mention the architecture (x86, amd64 or other) so I will
assume that you are on x86.

You are using a custom GD (in /usr/local) which might conflict with gd
installed by ubuntu and the same probably goes with agg too.
On Ubuntu 7.10 you get a very recent GD and agg so there is no reason
(that I know of or imagine) to compile your own.

On my system (Ubuntu 7.10 x86) agg and gd are:

unicoletti at ziggy ~ $apt-cache show libagg-dev | grep Version
Version: 2.4+20060719-3

unicoletti at ziggy ~ $apt-cache show libgd2-xpm | grep Version
Version: 2.0.34~rc1-2ubuntu1.1

which are both very recent and stable with mapserver.
Try to use those and python mapscript will build flawlessy.

Umberto


On 10/14/07, Matthew Perry <perrygeo at gmail.com> wrote:
> Hey folks,
>
>  Trying to install mapscript on ubuntu 7.10 and I'm getting this error:
>
> ------------------------------
> ./configure --without-tiff --with-jpeg --with-png --with-freetype \
> --with-zlib --with-threads --with-proj \
>  --with-gdal=/usr/local/bin/gdal-config --with-wcs --with-ogr \
> --with-wmsclient --with-wfsclient --with-wfs \
> --without-pdf --with-geos --enable-debug --with-agg=/home/perry/src/agg-2.4 \
> --with-postgis=/usr/bin/pg_config \
> --with-curl-config=/usr/bin/curl-config --with-httpd=/usr/sbin/apache2
> --with-gd=/usr/local \
> --with-fastcgi
> make
> cd mapscript/python
> swig -python -shadow -modern -templatereduce -fastdispatch -fvirtual
> -fastproxy \
>      -modernargs -castmode -dirvtable -fastinit -fastquery
> -noproxydel -nobuildnone  \
>     -o mapscript_wrap.c ../mapscript.i
> python setup.py build
> cd tests/cases && python runalltests.py -v
> ........
>  File "../../build/lib.linux-i686-2.5/mapscript.py", line 6, in <module>
>    import _mapscript
> ImportError: ../../build/lib.linux-i686-2.5/_mapscript.so: undefined
> symbol: _ZN3agg17g_elder_bit_tableE
>
> --------------
>
>
> This occurs with both mapserver svn and 5.0. I've also tried with the
> system libagg as well as a self-compiled libagg with fPIC and
> freetype. I've tried the simple swig statement as well as the newer
> optimized swig flags. The same outcome occurs each under every combo.
>
> I'm out of ideas (and patience). Has anyone else experienced this
> issue and solved it?
>
> --
> Matthew T. Perry
> http://www.perrygeo.net
>
> "Never ascribe to malice, that which can be adequately explained by
> incompetence."
>