FYI: Problems solved by switching to gcc 3.3

Tue Jun 10 18:43:00 GMT 2003

Hi Jost,
>Thanks for pointing me to gcc 3.3. I have created a i386-pc-mingw cross
>compiler and all of the issues are gone.
>> I have used the official 3.3 version of gcc and the latest binutils
>(binutils-2.13.90-20030111-1.tar.gz; see
>http://sourceforge.net/project/showfiles.php?group_id=2435).

>You don't need any patches.

Are you sure? Are you building on Linux? I think the only reason this worked is
that you happen to have 3.3 as your default Linux compiler. The cross
compilation process didn't really "work" because the gcjh used to create
the headers was your Linux gcjh, and not the cross gcjh built as part of the
cross build process. If you hide your Linux gcjh, the build will probably fail.
I think the above is also true for the gcj used to build the classfiles: your Linux
gcj got used instead.
This cross-configury patch (which didn't make it to 3.3) is needed to get
things working properly:
http://gcc.gnu.org/ml/java-patches/2003-q2/msg00111.html
>There is a small glitch when creating a cross compiler with gcc 3.3. One
>file looks for FIONREAD and then calls a method that does not exist in
>mingw. One could either remove the code or call the appropriate function
>declared in windows.h (I forgot its name)

Tom: see my followup post for more details.
>Creating dll's (including libgcj itself) also works as described in this
>list(using pseudo-reloc).

Can you describe the process you used or point to the list message?
Can you describe your computer's configuration? In particular, how
much RAM do you have? I was dying on my 256M Linux box and
wasn't sure how much memory you actually needed to make this
work. This will be happily received by other GCJ MingW users.
I'd be very grateful if you posted your sources and build scripts for
everything you did. Thanks so much for following up on this.
-- Mohan
http://www.thisiscool.com/
http://www.animalsong.org/