building from source

building from source

[Jakob Praher]

hi all,

out of curiosity I was trying to build eclipse from source.
I am using debian/unstable and did a fresh cvs co and build of gcc head,
which is using the tree-ssa stuff and I think the otable/atable gcj
engine already.

I was able to compile the first bunch of jars successfully, but at least
after org.apache.coyote plugin gcj segfaults with:

internal compiler error: segmentation fault
...

Is there a version of gcc/gcj which is stable enough to work?

Why is the compiler reporting a segfault in .java files, when the
command line tells to build from a binary jar file? 

Is there any trick?

thanks
-- Jakob

Re: building from source

[Nathan Bryant]

well the compiler issues are pretty interesting. the best way to fix 
them going forward may be to get things working on gcc 3.4, since that's 
what fedora 3 will ship.

the eclipse that ships with red hat enterprise used a "3.5-ssa" snapshot 
from the tree-ssa branch, but the issues surrounding this are murky: it 
corresponds to a snapshot from the tree-ssa branch from before 3.4 was 
released, and thus I'm not even certain that its C++/java abi 
corresponds exactly to any FSF compiler that will ever be released. 
Whether binaries compiled against its shared libraries will continue to 
be supported by redhat is anyone's guess. Even if a recent stabilized 
3.5-mainline snapshot were to be incorporated into rawhide for Eclipse 
purposes, there are still questions about giving nonstandard sonames to 
its shared libraries.

if you're not a gcc hacker you'll probably have more success with gcc3.4 
or the older gcc-ssa snapshots that are currently in red hat enterprise.

gcc3.4 may have more issues but the ones i've found so far appear to be 
more "peripheral" than what you are describing: there are problems with 
the verifier, but bytecode verification can probably be trivially turned 
off, for example.

3.5-ssa from RH enterprise is known to work, but it uses some hacks that 
aren't good enough for the main FSF respository - presumably, it just 
comments out bytecode verification entirely. Would a patch that 
implements a command line switch / environment variable equivalent in 
functionality to Sun Java's -Xverify:{none,all,remote} option have a 
chance of making it into the main FSF gcj/libgcj repository?

Jakob Praher wrote:

>hi all,
>
>out of curiosity I was trying to build eclipse from source.
>I am using debian/unstable and did a fresh cvs co and build of gcc head,
>which is using the tree-ssa stuff and I think the otable/atable gcj
>engine already.
>
>I was able to compile the first bunch of jars successfully, but at least
>after org.apache.coyote plugin gcj segfaults with:
>
>internal compiler error: segmentation fault
>...
>
>Is there a version of gcc/gcj which is stable enough to work?
>
>Why is the compiler reporting a segfault in .java files, when the
>command line tells to build from a binary jar file? 
>
>Is there any trick?
>
>thanks
>-- Jakob
>
>
>  
>