Re: [Mingw-users] configure with cross compiler

Earnie Boyd <[email protected]> Tue, 05 Nov 2002 13:42:23 -0500
Newsgroups gmane.linux.debian.ports.windows
Message-ID <[email protected]>
[email protected] wrote:
> Earnie Boyd <[email protected]> said:
> 
> 
>>[email protected] wrote:
>>
>>>I've installed the Debian mingw32 package, but can't figure out how to 
>>
> build software with it.
> 
>>>The binaries appear to be installed in /usr/i586-mingw32msvc/bin, and 
>>
> running i586-mingw32msvc-gcc -v gives
> 
>>>Reading specs from /usr/lib/gcc-lib/i586-mingw32msvc/3.2/specs
>>>Configured with: /home/ron/devel/debian/mingw32/mingw32-
>>
> 3.2/build_dir/src/gcc-3.2-20020817-1/configure -v --prefix=/usr --target=i586-
> mingw32msvc --enable-languages=c,c++ --enable-threads --disable-multilib --
> enable-version-specific-runtime-libs
> 
>>>Thread model: win32
>>>gcc version 3.2 (mingw special 20020817-1)
>>>
>>>So that's alright. But how do I go about getting a configure script to 
>>
> use these binaries instead of the native ones? I've tried just about every 
> combination of --host, --target, and --build that I can think of, and I've 
> read http://www.libsdl.org/extras/win32/cross/README.txt , and that hasn't 
> seemed to help me either. Can anyone point me in the right direction?
> 
>>Based on the directory configuration that you give above you should be 
>>able to just do  `./configure --host=i586-mingw32msvc' but that may be 
>>dependent on the version of autoconf that configure was built with.  I 
>>would tend to do `./configure --host=i586-mingw32msvc 
>>--target=i586-mingw32msvc --build=`./config.guess`' to remove any doubt 
>>about what the default is.
>>
>>Earnie.
>>
>>
> 
> 
> Here's what I get:
> 
> phil@rama:~/SDL-1.2.5$ ./configure --host=i586-mingw32msvc --target=i586-
> mingw32msvc --build='.config.guess'
                       ^             ^ should be a backquote not a 
single quote (key left of 1 on my american keyboard, ymmv).  Your 
missing a backslash as well, --build=`./config.guess`, your executing 
the script named config.guess in the working directory.  If of course 
that script is else where in your package then, you need to point to it 
appropriately.

Earnie.