About building test suite for Windows
webmaster at korosoft.net
Sun Jun 12 12:03:45 CDT 2011
On 06/12/11 07:03, André Hentschel wrote:
> i had a look in my config.log and found in my 32-bit tree:
> configure:7022: checking for i686-mingw32msvc-gcc
> configure:7052: result: no
> configure:7022: checking for i586-mingw32msvc-gcc
> configure:7038: found /usr/bin/i586-mingw32msvc-gcc
> configure:7049: result: i586-mingw32msvc-gcc
> configure:7065: checking whether i586-mingw32msvc-gcc works
> configure:7078: i586-mingw32msvc-gcc -c -g -O2 conftest.c >&5
> configure:7078: $? = 0
> configure:7079: result: yes
> so i had a look at configure and if i understand it correct it simply searches for one of these in your $PATH:
> i686-w64-mingw32-gcc i586-w64-mingw32-gcc i486-w64-mingw32-gcc i386-w64-mingw32-gcc
> i686-pc-mingw32-gcc i586-pc-mingw32-gcc i486-pc-mingw32-gcc i386-pc-mingw32-gcc
> i686-mingw32msvc-gcc i586-mingw32msvc-gcc i486-mingw32msvc-gcc i386-mingw32msvc-gcc
> i686-mingw32-gcc i586-mingw32-gcc i486-mingw32-gcc i386-mingw32-gcc
> so to state Maartens question more precisely: where is your mingw32-gcc binary, what's its name and is its path in your $PATH?
My mingw32-gcc is in /usr/local/bin, its name is simply "mingw32-gcc"
(no CPU name in there) and yes it's in $PATH.
On 06/12/11 07:10, Nicolas Le Cam wrote:
> If I read the port's makefile right, using ./configure
> CROSSCC="mingw32-gcc" should help.
I tried this actually, and indeed the makefile stopped complaining, then
winebuild started doing this instead:
winebuild: Invalid target specification 'mingw32'
A quick look in tools/winebuild/main.c (function set_target, line 194)
shows that it chokes if the target specification does not contain at
least one dash.
Now I am wondering if it's my system which is at fault for being badly
configured or if I should just modify winebuild so that it is more
lenient in its parsing of the target?
More information about the wine-devel