public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/38396] [4.4 Regression] libgcj_bc for 4.3 and 4.4 are binary incompatible but have the same SONAME
Date: Wed, 10 Dec 2008 11:09:00 -0000	[thread overview]
Message-ID: <20081210110933.19480.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38396-10053@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from jakub at gcc dot gnu dot org  2008-12-10 11:09 -------
-findirect-dispatch compiled/linked programs built with 4.3 work just fine
against 4.4 libgcj_bc.so.1 (that's why libgcj_bc.so.1 was added).
The only problem is if you link a program against both -lgcj_bc and -lgcj,
because if you link say with 4.3, then it will be linked against libgcj_bc.so.1
and libgcj.so.9 and if you then dynamically link it against 4.4 libgcj_bc.so.1,
which depends on libgcj.so.10, both libgcj.so.9 and libgcj.so.10 will be
dynamically linked into the same program, which for obvious reasons can't work
at all (same as for e.g. libstdc++.so.5 and libstdc++.so.6 etc.).

The answer is simple, never link against both -lgcj_bc and -lgcj if you want
the program to work against newer libjava versions.  If a program is
-findirect-dispatch as whole, it should be linked against -lgcj_bc, otherwise
against -lgcj.

This is nothing new, for 4.2 to 4.3 you get exactly the same problems.


-- 

jakub at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |aph at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38396


  parent reply	other threads:[~2008-12-10 11:09 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-04 12:08 [Bug libgcj/38396] New: " rguenth at gcc dot gnu dot org
2008-12-10 10:35 ` [Bug libgcj/38396] [4.4 Regression] " rguenth at gcc dot gnu dot org
2008-12-10 10:55 ` jakub at gcc dot gnu dot org
2008-12-10 11:03 ` rguenth at gcc dot gnu dot org
2008-12-10 11:09 ` jakub at gcc dot gnu dot org [this message]
2008-12-10 11:12 ` rguenth at gcc dot gnu dot org
2008-12-10 11:14 ` jakub at gcc dot gnu dot org
2008-12-10 11:17 ` rguenth at gcc dot gnu dot org
2008-12-10 11:23 ` jakub at gcc dot gnu dot org
2008-12-10 11:29 ` rguenth at gcc dot gnu dot org
2008-12-10 11:32 ` aph at gcc dot gnu dot org
2008-12-10 11:32 ` aph at gcc dot gnu dot org
2008-12-10 12:17 ` aph at gcc dot gnu dot org
2008-12-10 12:33 ` rguenther at suse dot de
2008-12-10 12:46 ` aph at redhat dot com
2008-12-10 13:14 ` rguenther at suse dot de
2008-12-10 13:26 ` aph at gcc dot gnu dot org
2008-12-10 13:30 ` jakub at gcc dot gnu dot org
2008-12-10 13:46 ` aph at redhat dot com
2008-12-10 14:08 ` jakub at gcc dot gnu dot org
2008-12-10 14:29 ` aph at gcc dot gnu dot org
2008-12-19 14:58 ` jakub at gcc dot gnu dot org
2008-12-19 15:02 ` [Bug libgcj/38396] [4.3 Regression] ecj1 linked against both -lgcj and -lgcj_bc jakub at gcc dot gnu dot org
2009-01-08 22:59 ` rguenth at gcc dot gnu dot org
2009-01-11  8:30 ` doko at ubuntu dot com
2009-01-12 17:36 ` aph at gcc dot gnu dot org
2009-01-24 10:26 ` rguenth at gcc dot gnu dot org
2009-04-04 21:01 ` dominiq at lps dot ens dot fr
2009-04-04 21:13 ` aph at redhat dot com
2009-04-04 21:17 ` dominiq at lps dot ens dot fr
2009-06-25 12:40 ` rguenth at gcc dot gnu dot org
2009-06-25 12:40 ` rguenth 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=20081210110933.19480.qmail@sourceware.org \
    --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: link
Be 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).