This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Compiling apps to Mingw32 with cygwin

----- Original Message -----
From: "Jon Leichter" <>

> Thus... returning to the ORIGINAL topic of this thread... I had
> the following to the OP:
> $ env CC=mgcc ./configure --host=i686-pc-mingw32
> My new understanding of switches gives me new perspective. 'build' and
> 'target' will pickup the value of 'host'. In this context, you're
> configure that the host == build == MinGW. I've said before that MinGW
> Cygwin is a loose cross-compile. So, it seems to me that this
> is ok, especially since 'host' binaries CAN successfully run in the
> environment.

Nope. because an autoconf script for mingw32 'build' may expect cp to be
'copy', sh to be cmd.exe and further stuff that will break or misbehave
on cygwin.

 $ env CC=mgcc ./configure --host=i686-pc-mingw32 --build=i686-pc-cygwin
is acceptable.

> We agreed that as of today that 'build', if not specified, gets the
value of
> 'host'. Even if this were to change, i.e. 'build' gets checked for
> automatically, my solution STILL works. In this case, it would be a
> compile, but it should still work.

See above why it doesn't. mingw != cygwin :}.

> This leads one to draw the following conclusions:
> This whole thread went off on a tangent suggesting that my solution
> wrong. So tell me. If my solution works more often than the "proper"
> how is it wrong?

Well.. I came in the thread late, so I get to say, 'huh, what, waddya


Unsubscribe info:
Bug reporting:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]