Re: Support for MinGW compilers in the Cygwin environment

[JonY]

On 10/25/2013 15:23, Daniel Richard G. wrote:
> On Thu, 2013 Oct 24 8:59-0400, Earnie Boyd wrote:
>>
>> Daniel, you can have configure use i686-pc-mingw32 or any other host
>> triplet by specifying it in your environment rather than on the
>> command line.  Then config.guess doesn't have to guess.
>>
>> export ac_cv_host=i686-pc-mingw32 ./configure
> 
> (I thought host_alias was the "official" variable to use there, along
> with {build,target}_alias)
> 
> You can set the triplet explicitly, but the whole purpose of
> config.guess is to save you the trouble. Given that the script already
> does the right thing on e.g. Solaris if it notices CC with 64-bit flags,
> do you see a way that it can similarly get things right if CC is set to
> the MinGW compiler on Cygwin?
> 

No, config.guess is for build machine detection, it is not there for you
to save keystrokes. Solaris was an isolated case, lets see how far you
can push if you did the same for -m32/-m64 on Linux.

> (I recognize that the MinGW compiler now takes the form of a cross-
> compiler, and that's great, but whether or not Autotools uses it as
> a cross compiler is independent of that. After all, if you had an
> old-style package with a standalone makefile, and you wanted to
> build using the MinGW compiler, you'd have to set CC/CXX/CFLAGS in a
> non-cross-ish way.)
> 

That's their fault for writing custom makefiles, I could very well write
makefiles that use C_COMPILER instead CC. Besides, setting CC/CXX does
not change the fact you are still on the same machine and is lying to
configure.

>> The same is true for build as well.  If host == build then it is
>> considered native else it is considered a cross compile.
> 
> So far, it seems that building with host==build==i686-pc-mingw32 on
> Cygwin breaks only because of that "cmd //c" thing in Libtool.
> 

You forgot build-time generators.

signature.asc
Description: OpenPGP digital signature