This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: Problems with Mohans GCJ 20030522 build
- From: Mohan Embar <gnustuff at thisiscool dot com>
- To: Øyvind Harboe <oyvind dot harboe at zylin dot com>, Ranjit Mathew <rmathew at hotmail dot com>
- Cc: dannysmith at users dot sourceforge dot net, GCJ Java <java at gcc dot gnu dot org>
- Date: Wed, 04 Jun 2003 02:01:13 -0500
- Subject: Re: Problems with Mohans GCJ 20030522 build
- Reply-to: gnustuff at thisiscool dot com
Hi People,
>> I have discussed this with Mohan, but we haven't figured out
>> why GCJ as of >20030409 must have thisiscool-gcc\gcc-3.3\bin
>> in the path.
>
>Probably because these have the "mingw-local" patches
>applied...
I thought that Øyvind had this problem with my build prior to the
last one, which didn't have the mingw-local patches. Øyvind?
>> - If I fix the path, it dies with:
>>
>> [apply] com/cyviz/xyzmodem/Upload.java:164: warning: unreachable
>> bytecode from 221 to before 224
>> [apply] Error: 0-bit reloc in dll
>> [apply] Error: 0-bit reloc in dll
>
>The latter seems to be a bug in recent MinGW binutils
>on large objects/DLLs:
Should I put out a new release with a prior version of binutils? Or
the new release candidate? Should I just stop combining binutils
and gcc like Andrew suggested (and like I have been tempted to
do on more than one occasion)?
Does this binutils bug have anything to do with my segfault when
trying to build libgcj.dll? If so, will I perhaps fare better with the
release candidate?
-- Mohan
http://www.thisiscool.com/
http://www.animalsong.org/