[mapserver-users] Sudden failure to find libttf.so.4.0
gisweb at lmi.net
gisweb at lmi.net
Wed Oct 9 19:12:44 PDT 2002
Mighty List:
Successful install of mapserver version 3.6.1 on our FreeBSD platform put smiles
on all faces. Performance and cartographic quality were magnificent. The build
consisted of the following options:
> /usr/home/gisweb/www/cgi-bin/mapserv -v
MapServer version 3.6.1 OUTPUT=PNG OUTPUT=JPEG OUTPUT=WBMP SUPPORTS=PROJ SUPPORT
S=TTF SUPPORTS=WMS_SERVER INPUT=TIFF INPUT=EPPL7 INPUT=JPEG INPUT=SHAPEFILE
Smiles vanished, however, when mapserver suddenly ceased working yesterday. The
apache error_log reports the following:
> tail -3 /usr/home/gisweb/www/logs/error_log
ld.so failed: Can't find shared library "libttf.so.4.0"
[Wed Oct 9 18:53:58 2002] [error] [client 32.102.91.129] Premature end of scrip
t headers: /usr/home/gisweb/www/cgi-bin/mapserv
And yet, gentle reader, the supposedly missing libttf.so.4.0 library remains
where it has always been, exactly where mapserv expects to find it (as
illustrated by the output of ldd and confirmed by the output of ls -l).
> ldd /usr/home/gisweb/www/cgi-bin/mapserv
/usr/home/gisweb/www/cgi-bin/mapserv:
-lm.2 => /usr/lib/libm.so.2.0 (0x2007a000)
-lpng.3 => /usr/local/lib/libpng.so.3.0 (0x20094000)
-lz.2 => /usr/lib/libz.so.2.0 (0x200ad000)
-ljpeg.9 => /usr/local/lib/libjpeg.so.9.0 (0x200b9000)
-lttf.4 => /usr/home/gisweb/local/lib/libttf.so.4.0 (0x200d5000)
-lpdf.1 => /usr/local/lib/libpdf.so.1.1 (0x200fa000)
-ltiff.3 => /usr/local/lib/libtiff.so.3.0 (0x20121000)
-lproj.3 => /usr/local/lib/libproj.so.3.1 (0x2015e000)
-lc.3 => /usr/lib/libc.so.3.1 (0x2018c000)
> ls -l /usr/home/gisweb/local/lib
total 1396
-rw-r--r-- 2 gisweb wheel 10194 Sep 20 09:04 gd.h
-rw-r--r-- 2 gisweb wheel 917 Sep 20 09:04 gd_io.h
-rw-r--r-- 1 gisweb wheel 185736 Sep 20 09:04 libgd.a
-rw-r--r-- 1 gisweb wheel 436250 Sep 24 13:54 libmap.a
-rwxr-xr-x 1 gisweb wheel 641 Sep 20 08:33 libttf.la
-rwxr-xr-x 1 gisweb wheel 757868 Sep 20 08:33 libttf.so.4.0
Who can explain this unusual twist of fate and restore mapserv to its original
triumphant glory?
Don't hesitate, gentle reader; speak up! Let the bells of freedom ring!
Ever hopefull,
Jonathan W. Lowe
www.giswebsite.com
More information about the MapServer-users
mailing list