[Xastir] Geotiff

[N1OFZ]

>>>   -I/opt/include  -I/usr/X11R6/include -L/usr/local/lib  -L/sw/lib
>>> -L/opt/lib  -L/usr/X11R6/lib
>>> conftest.c -lgeotiff  -lXpm -lintl -lcurl -lXm -lXt -lXp -lXext   
>>> -lSM
>>> -lICE -lX11  -lshp -lpcre
>>> -lproj -ltiff >&5
>>> ld: table of contents for archive: /sw/lib/libgeotiff.a is out of 
>>> date;
>>> rerun ranlib(1)
>>> (can't load from it)
>>>
>>> Any ideas?  I have also done the configure explicitly stating 
>>> geotiff's
>>> path but it made no difference.
>>
>> Interesting that it's trying to mess with the .a library, instead of
>> a .so.  .a is a static library.  .so is a shared library.  You
>> should be trying to use the .so instead.  Anyone know why it'd be
>> trying to link to a static library?
>>
>> This is on Mac OSX, right?
>
> incidentally, the hacks in the darwinports geotiff package to build a 
> dylib are probably useful for fixing the "you have a .so, i want a 
> .dylib" problem here. i never figured out how to extract them to 
> recontribute

To Curt's question, yes it OS X.

libtiff was installed with fink.  As you can see below it built it as 
.a and .dylib and linked .so to .dylib.  I built libgeotiff form the 
latest source using ./configure --prefix=/sw and after the make and 
install all I got was the static library.  There is an OS X precompiled 
(but older) version on the geotiff site but it also just contains the 
static library.  Is there a reason why static libraries are bad?

  dr$ ls -l |grep tiff
-rw-r--r--    1 root  dr       170356 18 Jan 11:04 libgeotiff.a
-rwxr-xr-x    1 dr    dr       780992 15 Jan 09:26 libtiff.3.6.1.dylib
lrwxr-xr-x    1 dr    dr           19 15 Jan 09:24 libtiff.3.dylib -> 
libtiff.3.6.1.dylib
-rw-r--r--    1 dr    dr      1107336 12 Jul  2002 libtiff.a
lrwxr-xr-x    1 dr    dr           15 15 Jan 09:24 libtiff.dylib -> 
libtiff.3.dylib
lrwxr-xr-x    1 dr    dr           13 15 Jan 09:24 libtiff.so -> 
libtiff.dylib