[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AC_OBJEXT again

From: Peter Eisentraut
Subject: Re: AC_OBJEXT again
Date: Tue, 12 Dec 2000 17:36:53 +0100 (CET)

Akim Demaille writes:

> * host or build characteristic?

It's neither, nor should it matter.  It's a feature of the compiler.  If
there's an alternative Cygwin compiler that generates .com files, then
that's what EXEEXT is.  If there's a regular Unix compiler that generates
a file 'foo.bazoo' when invoked 'cc ... -o foo', then EXEEXT='.bazoo'.
Also, a compiler suite could theoretically choose just about anything for
OBJEXT, since those files go from the compiler to the linker and neither
the host nor the build operating system or CPU care.

Any solution that uses 'uname', preprocessor symbols, or other random
features of a particular affected system is not going to be general.
That's the imake way.

If Cygwin treats conftest and conftest.exe equivalent in some situations
then you only need to find a sitation where this is not the case and test
with that.  Using cp or rm instead of test -f would be good candidates.

Peter Eisentraut      address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]