public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tromey at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgcj/28698] [gcj] libgcj-bc only used when building shared libs, not executables Date: Thu, 17 Aug 2006 01:24:00 -0000 [thread overview] Message-ID: <20060817012412.10229.qmail@sourceware.org> (raw) In-Reply-To: <bug-28698-5724@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from tromey at gcc dot gnu dot org 2006-08-17 01:24 ------- For a simple example it does not do this: opsy. gcj -O2 -fPIC -fjni -findirect-dispatch -o H --main=HelloWorld HelloWorld.class opsy. eu-readelf -d H|fgrep lib NEEDED Shared library: [libgcc_s.so.1] NEEDED Shared library: [libgcj_bc.so.1] NEEDED Shared library: [libm.so.6] NEEDED Shared library: [libpthread.so.0] NEEDED Shared library: [librt.so.1] NEEDED Shared library: [libdl.so.2] NEEDED Shared library: [libc.so.6] I wonder if something else is going on here... maybe some optimization is generating a symbol that necessitates pulling in libgcj itself? (I'm thinking of the builtins ... though I thought Andrew fixed these. So, maybe that is wrong.) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28698
next prev parent reply other threads:[~2006-08-17 1:24 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-08-11 13:04 [Bug libgcj/28698] New: " debian-gcc at lists dot debian dot org 2006-08-17 1:24 ` tromey at gcc dot gnu dot org [this message] 2006-08-17 22:40 ` [Bug libgcj/28698] " doko at ubuntu dot com 2006-08-18 11:38 ` doko at ubuntu dot com 2006-08-22 23:34 ` tromey at gcc dot gnu dot org 2006-08-22 23:46 ` bryce at mckinlay dot net dot nz 2006-08-23 9:21 ` debian-gcc at lists dot debian dot org 2006-08-23 16:58 ` tromey at gcc dot gnu dot org 2006-08-31 17:24 ` tromey at gcc dot gnu dot org 2006-08-31 22:00 ` tromey at gcc dot gnu dot org 2006-09-01 16:16 ` tromey at gcc dot gnu dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20060817012412.10229.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).