AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2005.04.01 23:11 "[Tiff] make fails when upgrading v3.7.1 --> v3.7.2 on OSX 10.3.8", by OpenMacNews
2005.04.02 12:13 "Re: [Tiff] make fails when upgrading v3.7.1 --> v3.7.2 on OSX 10.3.8", by Andrey Kiselev
2005.04.02 18:00 "Re: [Tiff] make fails when upgrading v3.7.1 --> v3.7.2 on OSX 10.3.8", by OpenMacNews
2005.05.13 14:37 "[Tiff] Troubles compiling libtiff on Mac OSX 10.4", by Naveen Nathan
2005.05.13 14:55 "Re: [Tiff] Troubles compiling libtiff on Mac OSX 10.4", by Bob Friesenhahn
2005.05.13 20:12 "Re: [Tiff] Troubles compiling libtiff on Mac OSX 10.4", by Naveen Nathan
2005.05.14 13:32 "[Tiff] libtiff+libjpeg on mingw/msys?", by Thom DeCarlo
2005.05.16 05:08 "Re: [Tiff] libtiff+libjpeg on mingw/msys?", by Andrey Kiselev
2005.05.18 15:38 "[Tiff] Another libtiff+libjpeg problem", by Thom DeCarlo
2005.06.13 13:33 "[Tiff] libstdc : cannot read symbols", by Maximus
2005.06.13 13:37 "Re: [Tiff] libstdc : cannot read symbols", by Frank Warmerdam

2005.04.01 23:11 "[Tiff] make fails when upgrading v3.7.1 --> v3.7.2 on OSX 10.3.8", by OpenMacNews

hi all,

i've had v3.7.1 of libtiff built on OSX 10.3.8 for awhile.

noting the update to v3.7.2, a like attempt with the new version, with simply:

wget http://dl.maptools.org/dl/libtiff/tiff-3.7.2.tar.gz
gnutar zxf tiff-3.7.2.tar.gz
cd /usr/ports/tiff-3.7.2

./configure
make
make install

fails on 'make' with:

    /bin/sh ../libtool --tag=CXX --mode=link g++  -g -O2   -o libtiffxx.la

-rpath /usr/local/lib -no-undefined -version-number 3:7:2 tif_stream.lo -ljpeg -lz -lc

g++ -dynamiclib -single_module -o .libs/libtiffxx.3.7.2.dylib .libs/tif_stream.o /usr/local/lib/libjpeg.dylib -lz -lc -install_name /usr/local/lib/libtiffxx.3.dylib -compatibility_version 11 -current_version 11.2

ld: Undefined symbols:
_TIFFClientOpen
/usr/bin/libtool: internal link edit command failed

    make[2]: *** [libtiffxx.la] Error 1
    make[1]: *** [all] Error 2
    make: *** [all-recursive] Error 1

wheras the same steps with v3.7.1 are, still, trouble-free.

is this a known issue? i can't get to bugzilla (no site response) to check at
the moment...

cheers,

richard