public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "michele at focuseek dot com" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug java/43302] New: [Regression] gcc creates "dummy" resources in object files Date: Tue, 09 Mar 2010 09:22:00 -0000 [thread overview] Message-ID: <bug-43302-11683@http.gcc.gnu.org/bugzilla/> (raw) gcj adds a java resource named ".dummy" to most (all?) the object file it produces. That resource doesn't appear anywhere in the sources. This is a problem when I try to link an application made from multiple .o produced by separate gcj invocations: I get the link-time error: multiple definition of `java resource .dummy' Also this is a regression as gcj 4.2.2 didn't add it and thus the linker didn't complain. gcc was built with the following options: ../gcc-4.4.3/configure --prefix="/opt/focuseek-build-fsk" \ --program-suffix=-fsk \ --enable-languages=c,c++,java \ --enable-shared --enable-threads \ --enable-__cxa_atexit \ --enable-libgcj-multifile on a centos 5.4. The md5 for ecj.jar is d7cd6a27c8801e66cbaa964a039ecfdb which, as of today, is what contrib/download_ecj retrieves. I'm aware of bug 42143 but I'm not able to say whether this is the same bug or another one. I will attach a test case as soon as possible. -- Summary: [Regression] gcc creates "dummy" resources in object files Product: gcc Version: 4.4.3 Status: UNCONFIRMED Severity: normal Priority: P3 Component: java AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: michele at focuseek dot com GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43302
next reply other threads:[~2010-03-09 9:22 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-03-09 9:22 michele at focuseek dot com [this message] 2010-03-09 9:25 ` [Bug java/43302] " michele at focuseek dot com 2010-03-10 8:30 ` michele at focuseek dot com 2010-05-03 18:37 ` glarkin at FreeBSD 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=bug-43302-11683@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=java-prs@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).