----- Original Message -----
From: "Jon Leichter" <[EMAIL PROTECTED]>
> First off... thanks again to both Robert and Earnie for taking part in
this
> discussion. I appreciate it a lot.
>
> Recapping once again...
>
> Robert says to use:
>
> $ ./configure --host=i686-pc-mingw32 --build=i686-pc-cygwin
>
> (no need to set CC if i686-pc-mingw32-gcc exists)
>
> Earnie says to use:
>
> $ ./configure --host=i686-pc-mingw32 --build=i686-pc-mingw32
>
> (still need to explicitly set CC)
Both invocations need to explicitly set CC - because of older configure
scripts in the first case.
> Using Robert's invocation WOULD put configure in cross-compile mode.
But
> since using Cygwin GCC to generate MinGW is ALMOST like a
cross-compile, it
> will work out ok. In fact, one compelling reason to use Robert's
method is
> because one wants the configure script to use the correct build tools,
e.g.
> cp instead of copy, rm instead of del, etc. I tend to agree that the
build
> environment IS Cygwin for this very reason.
>
> So here's a question. If configure is put into cross-compile mode
(with
> Robert's method), then wouldn't it be the case that configure would
NOT
> execute test binaries? If so, does that hurt the configuration process
in
> any way? Is this a problem?
Errgle. It _can_ affect the configure process. Say for instance, squid.
Squid uses test binaries to determine socket sizes, maximum fd limits
and the like, which it can't do during a cross compile run, so the cross
compiler (individual) has to provide those on the command line.
Cross-compiling certainly reduces the 'magic' detection that can take
place.
Rob
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
