AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2005.09.29 16:34 "[Tiff] libtiff.so.4", by Sid Boyce
2005.09.30 04:16 "Re: [Tiff] libtiff.so.4", by Jay Berkenbilt
2005.09.30 07:35 "Re: [Tiff] libtiff.so.4", by Sid Boyce
2005.09.30 14:49 "Re: [Tiff] libtiff.so.4", by Jay Berkenbilt
2005.09.30 15:34 "Re: [Tiff] libtiff.so.4", by Sid Boyce

2005.09.30 07:35 "Re: [Tiff] libtiff.so.4", by Sid Boyce

I have an app that needs the above lib, but the latest version is 3.7.4. I'm not on the list, please cc: me with replies.

What software/distribution are you running? Some Linux distributions including Debian as well as some other systems including Cygwin and, I think, NetBSD, have renumbered the shared library because of incompatibilities introduced around 3.6.1 or so. It is most likely that the software would work with 3.7.4 if you built it in such a way to get the library named as required by your application. (Maybe even just renaming it or making a symbolic link would work.) If you are still having difficulty, you probably need to include information about where you got the application and what distribution you're running. Hope that helps.

I'm running SuSE 9.3. I shall try the symlink first. It's a Linux app after Nasa WorldWind/Google Earth.

# ./ww2d

./ww2d: error while loading shared libraries: libtiff.so.4: cannot open shared object file: No such file or directory

# ln -s /usr/lib/libtiff.so.3.7.4 /usr/lib/libtiff.so.4 barrabas:/ftp/sep05/WW2D/linux # ldconfig ./ww2dbarrabas:/ftp/sep05/WW2D/linux # ./ww2d ./ww2d: error while loading shared libraries: libexpat.so.1: cannot open shared object file: No such file or directory

# ln -s /usr/lib/libexpat.so.0.5.0 /usr/lib/libexpat.so.1

barrabas:/ftp/sep05/WW2D/linux # ./ww2d ./ww2d: //usr/lib/libpng12.so.0: no version information available (required by ./ww2d)

The program 'ww2d' received an X Window System error. This probably reflects a bug in the program.

The error was 'BadMatch (invalid parameter attributes)'.

   (Details: serial 588 error_code 8 request_code 144 minor_code 5)
   (Note to programmers: normally, X errors are reported asynchronously;
    that is, you will receive the error a while after causing it.
    To debug your program, run it with the --sync command line
    option to change this behavior. You can then get a meaningful
    backtrace from your debugger if you break on the gdk_x_error()
function.)

barrabas:/ftp/sep05/WW2D/linux #
barrabas:/ftp/sep05/WW2D/linux # l /usr/lib/libpng12.

libpng12.a           libpng12.so          libpng12.so.0 

libpng12.so.0.1.2.8 barrabas:/ftp/sep05/WW2D/linux # l /usr/lib/libpng12.so.0 lrwxrwxrwx 1 root root 19 2005-05-02 14:53 /usr/lib/libpng12.so.0 -> libpng12.so.0.1.2.8*

Thanks, at least the libtiff.so.4 error has gone.

Regards
Sid.

--
Sid Boyce... Hamradio License G3VBV, licensed Private Pilot
Retired IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Specialist
Microsoft Windows Free Zone - Linux used for all Computing Tasks