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.23 15:05 "Re: [Tiff] bad version number 10752", by Kai-Uwe Behrmann

Here is what Mike Sweet suggests:

http://lists.freedesktop.org/archives/cairo/2006-October/008292.html

in short:
     #ifdef __APPLE__
     #  ifdef __i386__
     #    define LITTLE_ENDIAN
     #    undef BIG_ENDIAN
     #  else
     #    undef LITTLE_ENDIAN
     #    define BIG_ENDIAN
     #  endif /* __i386__ */
     #endif /* __APPLE__ */

It is a pure compile time check and should run as well. It would have to be tested.

kind regards

Kai-Uwe Behrmann
--
developing for colour management
www.behrmann.name + www.oyranos.org + www.cinepaint.org

Am 22.10.07, 13:57 -0500 schrieb Bob Friesenhahn:

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