From: Tom Tromey <tromey@redhat.com>
To: Jeff Sturm <jsturm@one-point.com>
Cc: Matthias Klose <doko@cs.tu-berlin.de>, java@gcc.gnu.org
Subject: Re: [3.1 branch] libgcjgc's soname conflicts with gcc-3.0's?
Date: Mon, 22 Apr 2002 15:56:00 -0000 [thread overview]
Message-ID: <87elh7l9io.fsf@creche.redhat.com> (raw)
In-Reply-To: Jeff Sturm's message of "Mon, 22 Apr 2002 16:53:20 -0400 (EDT)"
>>>>> "Jeff" == Jeff Sturm <jsturm@one-point.com> writes:
>> In the 3.0 and 3.1 branch, libgcjgc.so.1.0.1 is used. Is this
>> intended, or should the soname changed for the 3.1 release? If not,
>> can the libgcjgc.so.1.0.1 from 3.1 used as a replacement for 3.0's
>> libgcjgc?
Jeff> Actually I don't think libgcjgc.so is used anymore, and needn't
Jeff> be installed, right?
I was just going to say the same thing. I think the same applies to
zlib as well. We can just use noinst_ and then we don't need to worry
about the soname.
Tom
prev parent reply other threads:[~2002-04-22 21:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-22 11:42 Matthias Klose
2002-04-22 13:55 ` Jeff Sturm
2002-04-22 15:56 ` Tom Tromey [this message]
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=87elh7l9io.fsf@creche.redhat.com \
--to=tromey@redhat.com \
--cc=doko@cs.tu-berlin.de \
--cc=java@gcc.gnu.org \
--cc=jsturm@one-point.com \
/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).