Problems compiling libgcj-snapshot-2000-10-29

Tom.Williams@diversifiedsoftware.com Tom.Williams@diversifiedsoftware.com
Mon Oct 30 16:25:00 GMT 2000


Thanks for the heads-up.  Here is the output from gcj when I run it in the
shell where I'm building libgcj:

bash$ gcj -v
Reading specs from /usr/local/egcs/lib/gcc-lib/i586-pc-linux-gnu/2.97/specs
Reading specs from /usr/local/egcs/lib/gcc-lib/i586-pc-linux-gnu/2.97/../../../libgcj.spec
rename spec lib to liborig
rename spec startfile to startfileorig
Configured with:  --prefix=/usr/local/egcs --enable-languages=c,c++,java --enable-shared --enable-threads
gcc version 2.97 20001023 (experimental)
bash$

I used egcs-20001016 (I think) to build egcs-20001023.  Do you think I have a bad gcj?

Peace......

Tom




Alexandre Petit-Bianco <apbianco@cygnus.com> on 10/30/2000 04:05:46 PM

Please respond to apbianco@redhat.com

To:   Tom.Williams@diversifiedsoftware.com
cc:   java-discuss@sources.redhat.com
Subject:  Re: Problems compiling libgcj-snapshot-2000-10-29




Tom.Williams@diversifiedsoftware.com writes:

> Hi!  I downloaded a fresh snapshot
> (libgcj-snapshot-2000-10-29.tar.bz2) from ftp.freesoftware.com and
> I'm building it now.

Note that I found yesterday that if I accidently used a previous egcs
build to compile gcj (instead of using the default installed gcc) I
would have problems building some of the library files, jc1
complaining about some methods missing a return statement and later on
complaining about not being able to find certain file it couldn't
generate -- I'm pretty sure that java/io/ObjectInputStream was one of
them.

Before I realized my mistake, I found that this line

  BLOCK_EXPR_BODY (DECL_FUNCTION_BODY (mdecl)) = exit_block ();

in parse.y:end_artificial_method_body() wouldn't execute correctly and
instead of using exit_block() returned value, BLOCK_EXPR_BODY
(DECL_FUNCTION_BODY (mdecl)) would be set to NULL. I tried to use a
temporary variable, the bug went away and then I realized I was using
an old egcs build to compile jc1. I switched to the installed compiler
and the bug went away. Most likely a glitch in the previous egcs I
attempted to build.

Just make sure you're not in this situation.

./A








More information about the Java mailing list