AWARE [SYSTEMS] Imaging expertise for the Delphi developer
AWare Systems, Imaging expertise for the Delphi developer, Home TIFF and LibTiff Mailing List Archive

LibTiff Mailing List

TIFF and LibTiff Mailing List Archive
October 2007

Previous Thread
Next Thread

Previous by Thread
Next by Thread

Previous by Date
Next by Date

Contact

The TIFF Mailing List Homepage
This list is run by Frank Warmerdam
Archive maintained by AWare Systems



Valid HTML 4.01!



Thread

2007.10.23 08:38 "universal build patch", by Kai-uwe Behrmann
2007.10.23 15:37 "Re: universal build patch", by Bob Friesenhahn
2007.10.23 15:50 "Re: universal build patch", by Andrey Kiselev
2007.10.23 16:12 "Re: universal build patch", by Bob Friesenhahn
2007.10.23 19:17 "Re: universal build patch", by Andrey Kiselev
2007.10.23 20:44 "Re: universal build patch", by Bob Friesenhahn
2007.10.24 07:19 "Re: universal build patch", by Andrey Kiselev
2007.10.24 08:32 "Re: universal build patch", by Kai-uwe Behrmann
2007.10.24 11:26 "Re: universal build patch", by Andrey Kiselev
2007.10.24 15:44 "Re: universal build patch", by Bob Friesenhahn
2007.10.23 20:56 "Re: universal build patch", by Toby Thain

2007.10.24 07:19 "Re: universal build patch", by Andrey Kiselev

On Tue, Oct 23, 2007 at 03:44:33PM -0500, Bob Friesenhahn wrote:
> >I am sure that AC_C_BIGENDIAN macro can deduce the target byte order
> >using some heuristics (that macro works in case of
> >cross-compilation).  So it can be adopted for OS X case too. The only
> >problem for me is that I do not have a proper environment to develop
> >and test such a macro. It shouldn't be too complicated. So my
> >preference is to modify a test rather than libarary itself. I don't
> >see any serious reason to replace the compile time switch.
> 
> The problem seems to be that the compiler is run just "once" with same
> options and header files to produce object code for completely
> different targets.  Any executables that configure builds and runs in
> order to implement tests will be tested on the current host CPU/OS.
> That is why there is a problem.  The problem is not limited to
> endianness, although that is the most obvious issue.

Ah, I see now. But I am sure that it still can be addressed at configure
stage. It seems that latest autoconf already has some support for
universal binary case:

 http://lists.gnu.org/archive/html/autoconf-patches/2007-02/msg00023.html

It is not a complete solution, but it should work for libtiff I think
(few changes in sources required).

Best regards,
Andrey


-- 
Andrey V. Kiselev
ICQ# 26871517