Building GCC 3.3 / MingW

Tue Feb 11 15:57:00 GMT 2003

Hi Ranjit,
Thanks for your response.
>The binutils patches are necessary and cross-binutils builds without any
>hassles for MinGW on Linux after these patches. You can just download
>the latest patched binutils sources from:

Before I went to bed last night (and before my post), I tried following
your instructions on Linux:
http://ranjitmathew.tripod.com/phartz/gcj/bldgcj.html
using these from MingW SF:
binutils-2.13.90-20021006-2-src.tar.gz
mingw-runtime-2.4-src.tar.gz
regex-0.12-20010123.zip
w32api-2.2-src.tar.gz
(The above binutils untars to "binutills-2.13.90-20021006-2" (with
two "l"s). Strange.)
...as well as the GCC 3.3 branch I pulled from CVS. I didn't try to apply
any MingW GCC or GCJ patches.
As you predicted, the cross binutils built beautifully. It was pretty
exciting. The GCC build failed, however, on libgcc and I retaliated
by going to bed.
I am prepared to roll up my sleeves and see what's going on, but I just
wanted to make sure that I wasn't doing anything flagrantly wrong and
that the MingW versions I was using (i.e. 2.4 instead of 2.3 of the runtime,
binutils-2.13.90, etc.) are okay.
Thanks for your tips and your offer to help. Could you verify that the
MingW versions I'm using are sane and that it's still viable to follow
your build procedure (except for the MingW GCC patches and your GCJ patches)?
I'll check out the crossed-native configury patch link you sent.
Thanks again.
-- Mohan