This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: 3.3 configure static
> In the current case, it might be that we need to link dynamically
> against libgcc even if we link statically against libgcj.
That is exactly what I tried. Linking dynamically against libgcc and statically
against libgcj works, by removing the symbolic link to libgcj in the 3.3 lib
directory.
There problems occur when i try to link statically against libgcc as well. Then I get
all these error messages
> I want Erik to test that, but his environment seems to be broken.
Don't worry. My environment still works. The experiments that I carried out were only
partially successful, though.
> Erik, can you look and see why you're linking with libgcc from gcc
> 3.2? Did you do a clean "make install" from gcc 3.3?
I did this on purpose. I removed the libgcc_s link and tried to see if things would
work out by just linking libgcj statically. They don't. You also need libgcc_s of
version 3.3, and you apparently can't link libgcc_s statically.
By the way, I've also tried deploying libgcj and libgcc to an older machine and set
the LD_LIBRARY_PATH to reference them first. The executables still failed... I can
try this again, but if you know from the top of your hat why it doesn't work, feel
free to tell me.