This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Why long command line for libgcj.so?
- From: "H . J . Lu" <hjl at lucon dot org>
- To: gcc at gcc dot gnu dot org
- Date: Tue, 4 Jun 2002 13:55:54 -0700
- Subject: Why long command line for libgcj.so?
When I tried to cross compile gcc 3.1.1 to Linux/mipsel, ld died in
libjava. However, core dump doesn't give me much info:
Core was generated by `lt-ld-new -EL -shared -o .libs/libgcj.so.3.0.0
-L/export/build/gnu/tools-3.1/bu'.
Program terminated with signal 11, Segmentation fault.
Cannot access memory at address 0x40014658
#0 0x40049279 in ?? ()
(gdb) bt
#0 0x40049279 in ?? ()
Cannot access memory at address 0xbfff0028
I suspect stack/heap/memory limit. My machine has 1GB RAM. The problem
is it is almost impossible to run ld in gdb since the command line
for building libgcj.so is way too long. May I ask why we can't use
"ld -r" or "ar"/--whole-archive to build libgcj.so? Is that because
libtool doesn't support it?
H.J.