3.3 configure static

Wed Jul 9 17:48:00 GMT 2003

> It is only safe to static link libgcc if you are certain there will be
> only one copy throughout your application. That means if you link it into
> your main executable, you cannot link to any DSO that needs libgcc. But a
> static linked libgcc is possible, and is what the Windows builds currently

So, if I understand this right, the executable crashes when compiled with gcj,
configured with--disable-shared, because one or more of the executable's dependencies
link against another copy of libgcc_s.so.
I've been trying to find the culprit, but ldd hasn't revealed a second dependency
on libgcc_s.so by recursively looking at the ldd output of each of the libraries
linked dynamically:
 libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0 (0x4c827000)
 libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0 (0x4ca7c000)
 libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0x4caea000)
 libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 (0x4c66e000)
 libm.so.6 => /lib/libm.so.6 (0x4c0de000)
 libpangoxft-1.0.so.0 => /usr/lib/libpangoxft-1.0.so.0 (0x4c7dc000)
 libpangox-1.0.so.0 => /usr/lib/libpangox-1.0.so.0 (0x4c812000)
 libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0x4c7a7000)
 libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0x4c456000)
 libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0x4c4e6000)
 libdl.so.2 => /lib/libdl.so.2 (0x4c0d9000)
 libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x4c3e0000)
 libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0x4c683000)
 libpthread.so.0 => /lib/libpthread.so.0 (0x4c218000)
 libc.so.6 => /lib/libc.so.6 (0x4bfa6000)
 libXrandr.so.2 => /usr/X11R6/lib/libXrandr.so.2 (0x4c821000)
 libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x4c1e4000)
 libXft.so.2 => /usr/X11R6/lib/libXft.so.2 (0x4c568000)
 libXrender.so.1 => /usr/X11R6/lib/libXrender.so.1 (0x4c55e000)
 libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x4c534000)
 libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x4c103000)
 libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x4c48d000)
 libz.so.1 => /usr/lib/libz.so.1 (0x4c26b000)
 /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x4bf90000)
 libexpat.so.0 => /usr/lib/libexpat.so.0 (0x4c50c000)
Could the problem occur for another reason as well? Or can this be the only reason?