Tim Van Holder wrote:
Of course, if you need to specify CC anyway, you might as well specify
your host system too:
./configure CC='gcc -mno-cygwin' --host=i386-pc-mingw32
After all, you're basically cross-compiling, aren't you.
Earnie Boyd wrote:
This is the correct way to do it.
On Tue, 5 Jun 2001, Teun Burgers wrote:
Tim Van Holder wrote:
Of course, if you need to specify CC anyway, you might as well specify
your host system too:
./configure CC='gcc -mno-cygwin' --host=i386-pc-mingw32
After all, you're basically cross-compiling, aren't you.
Teun Burgers wrote:
Tim Van Holder wrote:
Of course, if you need to specify CC anyway, you might as well specify
your host system too:
./configure CC='gcc -mno-cygwin' --host=i386-pc-mingw32
After all, you're basically cross-compiling, aren't you.
Earnie Boyd wrote:
On 29 May 2001 23:20:26 +0200, Teun Burgers wrote:
Hi
I am maintaining the configure script for
gnugo (http://www.fsf.org/software/gnugo/)
Under autoconf 2.13 when you had AC_EXEEXT
in you configure.in you could do under cygwin
a mingw32 build as follows:
env CC='gcc -mno-cygwin'
Tim Van Holder wrote:
On 29 May 2001 23:20:26 +0200, Teun Burgers wrote:
Hi
I am maintaining the configure script for
gnugo (http://www.fsf.org/software/gnugo/)
Under autoconf 2.13 when you had AC_EXEEXT
in you configure.in you could do under cygwin
a mingw32 build as follows:
Hi
I am maintaining the configure script for
gnugo (http://www.fsf.org/software/gnugo/)
Under autoconf 2.13 when you had AC_EXEEXT
in you configure.in you could do under cygwin
a mingw32 build as follows:
env CC='gcc -mno-cygwin' ./configure
AC_EXEEXT would set ac_cv_mingw32=yes,
so you were
