This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
RE: libgcc_s.so.1 and libgcj.so.4
- From: "Erik Poupaert" <erik dot poupaert at chello dot be>
- To: "David Young" <dvd at OCF dot Berkeley dot EDU>
- Cc: <java at gcc dot gnu dot org>
- Date: Sat, 19 Apr 2003 17:52:30 +0200
- Subject: RE: libgcc_s.so.1 and libgcj.so.4
>>>>> I seem to have statically linked libgcc_s.a and libgcj.a by
configuring
>>>>> the gcc suite with the option "--disable-shared". When I run ldd on
my
>>>>> gcj/swt-motif app, I get the following results
As I can see from your input, all shared objects referred to by your
executable are stable, "platform-type" dependencies. As Adrew pointed out,
libgcc itself could also be referenced dynamically -- instead of
statically -- but I guess the option is not necessarily available in the GCC
configure script, is it? But then, I can live with libgcc referenced
statically as well.
>>>>> Does disabling sharing, however, create other complications for the
application?
I don't think so, at this point. In my impression, "--disable-shared" should
do. I'll give it a shot. Thanks.