From: "H. J. Lu" <hjl@lucon.org>
To: DJ Delorie <dj@redhat.com>
Cc: binutils@sources.redhat.com, gcc-patches@gcc.gnu.org
Subject: Re: PATCH: Fix shared library build for libiberty
Date: Fri, 17 Dec 2004 15:41:00 -0000 [thread overview]
Message-ID: <20041217154126.GA31731@lucon.org> (raw)
In-Reply-To: <20041217052058.GA21455@lucon.org>
On Thu, Dec 16, 2004 at 09:20:58PM -0800, H. J. Lu wrote:
> On Thu, Dec 16, 2004 at 09:10:41PM -0500, DJ Delorie wrote:
> >
> > > I believe libiberty is the only library which uses config/mh-CPUpic
> > > for building shared library. Other libraries use libtool for that,
> > > which doesn't use config/mh-CPUpic.
> >
> > I'd rather libiberty use libtool, then. Any reason not to? Would you
> > like to try changing it?
>
> I can give it a try.
Just to make sure that everyone understands that we don't build
libiberty.so for libiberty. But we do build an archive compiled with
-fPIC which can be used by other libraries. Are we going to build
libiberty.so or keep the same? If we build libiberty.so, we have to
be very careful about the ABI. We have to treat it like libstdc++ when
we change/add/remove things to libiberty. If we don't build
libiberty.so, I don't see there is a need for libtool. My top level
patch is better.
H.J.
next prev parent reply other threads:[~2004-12-17 15:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-16 23:01 H. J. Lu
2004-12-17 2:01 ` DJ Delorie
2004-12-17 2:08 ` H. J. Lu
2004-12-17 2:10 ` DJ Delorie
2004-12-17 2:56 ` Zack Weinberg
2004-12-17 4:16 ` Gabriel Dos Reis
2004-12-17 6:03 ` Zack Weinberg
2004-12-17 5:21 ` H. J. Lu
2004-12-17 15:41 ` H. J. Lu [this message]
2004-12-17 17:48 ` DJ Delorie
2004-12-17 19:01 ` H. J. Lu
2004-12-17 19:11 ` DJ Delorie
2004-12-18 0:22 ` H. J. Lu
2004-12-18 0:49 ` DJ Delorie
2004-12-18 1:44 ` H. J. Lu
2004-12-18 1:51 ` DJ Delorie
2004-12-18 21:38 ` Andrew Pinski
2004-12-24 14:10 ` Andreas Jaeger
2004-12-24 15:23 ` DJ Delorie
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=20041217154126.GA31731@lucon.org \
--to=hjl@lucon.org \
--cc=binutils@sources.redhat.com \
--cc=dj@redhat.com \
--cc=gcc-patches@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).