Thank you, Paul - I wish I could say it fixed my problem.

Here's all of the libboost stuff in /usr/lib, does it make sense? FWIW I still have the ones in /usr/local/lib suggested by firetree.net guy, should I get rid of those or are they harmless?

    libboost_filesystem.a -> libboost_filesystem-gcc-mt-1_33_1.a
    libboost_filesystem-gcc-1_33_1.a
libboost_filesystem-gcc-1_33_1.so -> libboost_filesystem- gcc-1_33_1.so.1.33.1
    libboost_filesystem-gcc-1_33_1.so.1.33.1
    libboost_filesystem-gcc-mt-1_33_1.a
libboost_filesystem-gcc-mt-1_33_1.so -> libboost_filesystem-gcc- mt-1_33_1.so.1.33.1
    libboost_filesystem-gcc-mt-1_33_1.so.1.33.1
libboost_filesystem-mt.so -> /usr/lib/libboost_filesystem-gcc- mt-1_33_1.so
    libboost_filesystem.so -> libboost_filesystem-gcc-mt-1_33_1.so
libboost_iostreams-gcc-mt-1_33_1.so -> libboost_iostreams-gcc- mt-1_33_1.so.1.33.1
    libboost_iostreams-gcc-mt-1_33_1.so.1.33.1
libboost_iostreams-mt.so -> /usr/lib/libboost_iostreams-gcc- mt-1_33_1.so
    libboost_iostreams.so -> libboost_iostreams-gcc-mt-1_33_1.so
libboost_program_options.a -> libboost_program_options-gcc- mt-1_33_1.a
    libboost_program_options-gcc-1_33_1.a
libboost_program_options-gcc-1_33_1.so -> libboost_program_options-gcc-1_33_1.so.1.33.1
    libboost_program_options-gcc-1_33_1.so.1.33.1
    libboost_program_options-gcc-mt-1_33_1.a
libboost_program_options-gcc-mt-1_33_1.so -> libboost_program_options-gcc-mt-1_33_1.so.1.33.1
    libboost_program_options-gcc-mt-1_33_1.so.1.33.1
libboost_program_options-mt.so -> /usr/lib/ libboost_program_options-gcc-mt-1_33_1.so libboost_program_options.so -> libboost_program_options-gcc- mt-1_33_1.so libboost_python-gcc-1_33_1.so -> libboost_python-gcc-1_33_1.so. 1.33.1
    libboost_python-gcc-1_33_1.so.1.33.1
libboost_python-gcc-mt-1_33_1.so -> libboost_python-gcc- mt-1_33_1.so.1.33.1
    libboost_python-gcc-mt-1_33_1.so.1.33.1
    libboost_python-mt.so -> /usr/lib/libboost_python-gcc-mt-1_33_1.so
    libboost_python.so -> libboost_python-gcc-mt-1_33_1.so
    libboost_regex.a -> libboost_regex-gcc-mt-1_33_1.a
    libboost_regex-gcc-1_33_1.a
    libboost_regex-gcc-1_33_1.so -> libboost_regex-gcc-1_33_1.so.1.33.1
    libboost_regex-gcc-1_33_1.so.1.33.1
    libboost_regex-gcc-mt-1_33_1.a
libboost_regex-gcc-mt-1_33_1.so -> libboost_regex-gcc- mt-1_33_1.so.1.33.1
    libboost_regex-gcc-mt-1_33_1.so.1.33.1
    libboost_regex-mt.so -> /usr/lib/libboost_regex-gcc-mt-1_33_1.so
    libboost_regex.so -> libboost_regex-gcc-mt-1_33_1.so
    libboost_serialization.a -> libboost_serialization-gcc-mt-1_33_1.a
    libboost_serialization-gcc-1_33_1.a
    libboost_serialization-gcc-mt-1_33_1.a
    libboost_thread.a -> libboost_thread-gcc-mt-1_33_1.a
    libboost_thread-gcc-mt-1_33_1.a
libboost_thread-gcc-mt-1_33_1.so -> libboost_thread-gcc- mt-1_33_1.so.1.33.1
    libboost_thread-gcc-mt-1_33_1.so.1.33.1
    libboost_thread-mt.so -> /usr/lib/libboost_thread-gcc-mt-1_33_1.so
    libboost_thread.so -> libboost_thread-gcc-mt-1_33_1.so
libboost_wserialization.a -> libboost_wserialization-gcc- mt-1_33_1.a
    libboost_wserialization-gcc-1_33_1.a
    libboost_wserialization-gcc-mt-1_33_1.a


On May 1, 2008, at 1:48 PM, Paul Smith wrote:

Mike:

I'm not following the gentlemen at firetree.net: there's no copy the boost libs to a new directory. There is some naming impedance mismatch which you can correct with the script below.

    #!/bin/sh
    for lib in `find /usr/lib -name 'libboost_*-gcc-mt-1_33_1.so'`; do
        name=`echo ${lib} | sed -r -e 's/.*boost_(.*)-gcc.*/\1/'`
        ln -s ${lib} /usr/lib/libboost_${name}-mt.so
    done
    ldconfig

Execute as root and try building again.

Cheers,
Paul.

On Thu, May 1, 2008 at 3:35 PM, Michal Migurski <[EMAIL PROTECTED]> wrote:
This is a followup to a previous mail of mine:
       https://lists.berlios.de/pipermail/mapnik-users/2008-April/000844.html

I'm still trying to get a "clean" installation of Mapnik going for
near-future deployment. I'm aiming for Mapnik 0.5.1 on Debian Etch,
compiled from source. At the first stage of the build process, I get
failures to recognize libboost_filesystem-mt.

I am following the OSM instructions for Mapnik 0.5:
       
http://wiki.openstreetmap.org/index.php/Mapnik#For_Debian_Etch_.28stable.29_.28Mapnik_0.5.29



There have been two problems along the way that I'm running into. One
was that `apt-get source mapnik` came up empty-handed, so I added this
to my sources.list:
deb-src http://http.us.debian.org/debian unstable main contrib non-free

So that's fine, I now get the mapnik-0.5.1 source code that I
expected. The second is exactly the same libboost_filesystem-mt issue
described here:
       http://blog.firetree.net/2008/04/29/mapnik-on-debian-etch/

Except that when I follow the advice on that page, I still get the
same build error:
       "Could not find header or shared library for boost filesystem,
exiting!"

FWIW, here's my libboost installation, post-symbolic-linking:

       # ls -l /usr/local/lib/libboost_*
       lrwxrwxrwx 1 root staff 25 2008-05-01 18:43 /usr/local/lib/
libboost_filesystem-gcc-mt-1_33_1.so.1.33.1 -> libboost_filesystem- mt.so
       lrwxrwxrwx 1 root staff 31 2008-05-01 18:42 /usr/local/lib/
libboost_filesystem-mt.so -> /usr/lib/libboost_filesystem.so
       lrwxrwxrwx 1 root staff 24 2008-05-01 18:43 /usr/local/lib/
libboost_iostreams-gcc-mt-1_33_1.so.1.33.1 -> libboost_iostreams-mt.so
       lrwxrwxrwx 1 root staff 30 2008-05-01 18:42 /usr/local/lib/
libboost_iostreams-mt.so -> /usr/lib/libboost_iostreams.so
       lrwxrwxrwx 1 root staff 30 2008-05-01 18:43 /usr/local/lib/
libboost_program_options-gcc-mt-1_33_1.so.1.33.1 ->
libboost_program_options-mt.so
       lrwxrwxrwx 1 root staff 36 2008-05-01 18:42 /usr/local/lib/
libboost_program_options-mt.so -> /usr/lib/libboost_program_options.so
       lrwxrwxrwx 1 root staff 21 2008-05-01 18:43 /usr/local/lib/
libboost_python-gcc-mt-1_33_1.so.1.33.1 -> libboost_python-mt.so
       lrwxrwxrwx 1 root staff 27 2008-05-01 18:42 /usr/local/lib/
libboost_python-mt.so -> /usr/lib/libboost_python.so
       lrwxrwxrwx 1 root staff 20 2008-05-01 18:43 /usr/local/lib/
libboost_regex-gcc-mt-1_33_1.so.1.33.1 -> libboost_regex-mt.so
       lrwxrwxrwx 1 root staff 26 2008-05-01 18:42 /usr/local/lib/
libboost_regex-mt.so -> /usr/lib/libboost_regex.so
       lrwxrwxrwx 1 root staff 21 2008-05-01 18:43 /usr/local/lib/
libboost_thread-gcc-mt-1_33_1.so.1.33.1 -> libboost_thread-mt.so
       lrwxrwxrwx 1 root staff 27 2008-05-01 18:42 /usr/local/lib/
libboost_thread-mt.so -> /usr/lib/libboost_thread.so

Any thoughts on where to proceed here? I'm doing all of this on
Amazon's EC2, firing up and tearing down machines as I go along.

-mike.

----------------------------------------------------------------
michal migurski- [EMAIL PROTECTED]
                 415.558.1610



_______________________________________________
Mapnik-users mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/mapnik-users



--
Paul Smith
http://www.pauladamsmith.com/

----------------------------------------------------------------
michal migurski- [EMAIL PROTECTED]
                 415.558.1610



_______________________________________________
Mapnik-users mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/mapnik-users

Reply via email to