AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2007.10.22 17:40 "[Tiff] bad version number 10752", by Kai-Uwe Behrmann
2007.10.22 18:31 "Re: [Tiff] bad version number 10752", by Bob Friesenhahn
2007.10.22 18:50 "Re: [Tiff] bad version number 10752", by Kai-Uwe Behrmann
2007.10.22 18:57 "Re: [Tiff] bad version number 10752", by Bob Friesenhahn
2007.10.23 15:05 "Re: [Tiff] bad version number 10752", by Kai-Uwe Behrmann
2007.10.23 15:45 "Re: [Tiff] bad version number 10752", by Bob Friesenhahn
2007.10.22 20:07 "Re: [Tiff] bad version number 10752", by Toby Thain
2007.10.23 02:33 "Re: [Tiff] bad version number 10752", by Graeme Gill
2007.10.23 06:28 "Re: [Tiff] bad version number 10752", by Kai-Uwe Behrmann
2007.10.23 07:41 "Re: [Tiff] bad version number 10752", by Graeme Gill
2007.10.23 08:10 "Re: [Tiff] bad version number 10752", by John

2007.10.22 18:57 "Re: [Tiff] bad version number 10752", by Bob Friesenhahn

Does the problem have anything to do with the library being built as a universal binary?

Certainly. The files where written and read by a libtiff v3.8.2 as pure big endian version and the Preview app shows them correctly. The universal built libtiff gives up.

Apple recommends to use runtime endianess checking. Very often software checks on compile time.

Libtiff definitely checks at compile time. Runtime checking is often less efficient.

Maybe you can do two separate builds and then use 'lipo' to create a working universal binary?

http://developer.apple.com/documentation/Darwin/Reference/ManPages/man1/lipo.1.html

Bob
======================================
Bob Friesenhahn
bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/