host=i686-pc-linux-gnu target=i386-pc-mingw32,i386-pc-msdosdjgpp

Dara Hazeghi
Mon Jul 14 00:37:00 GMT 2003


I'm in the process of building a mingw32 toolchain
from source. Here's what's worked for me:

0) grabbed binutils (cvs), gcc (cvs),
mingw32-runtime-3.0-src.tar.gz, and

1) built binutils: ./configure
--target=i386-pc-mingw32 --prefix=$prefix; make; make
1.5) added $prefix/bin to path.
2) copied the headers from mingw32-runtime-3.0/include
and w32-api-2.3/include to
3) built gcc (c compiler only): ./configure
--target=i386-pc-mingw32 --enable-languages=c
--prefix=$prefix; make; make install
4) built w32-api: ./configure --host=i386-pc-mingw32
--prefix=$prefix/i386-pc-mingw32; make; make install
5) built mingw32-runtime: first need to copy
w32-api-2.3/include to mingw32-runtime-3.0/include,
then ./configure --prefix=$prefix/i386-pc-mingw32
--host=i386-pc-mingw32, cd mingwex; make
CC=i386-pc-mingw32-gcc; cd ..; make; make install

You _must_ build mingwex before the rest of the
runtime, and for some dumb reason it sets $CC to cc,
so you must override in that directory.

6) do a full build of gcc: ./configure
--prefix=$prefix --target=i386-pc-mingw32; make; make

So far tested a few simple console programs under
wine, and they've worked.

hope this helps,


Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!

Want more information?  See the CrossGCC FAQ,
Want to unsubscribe? Send a note to

More information about the crossgcc mailing list