From: Jim Blandy <jimb@redhat.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: SID public developers <sid@sources.redhat.com>
Subject: Re: SID configury, libtoolery updated
Date: Sat, 04 Jun 2005 15:22:00 -0000 [thread overview]
Message-ID: <vt24qcem9mc.fsf@zenia.home> (raw)
In-Reply-To: <20050604122432.GA14056@redhat.com>
"Frank Ch. Eigler" <fche@redhat.com> writes:
> > [...] One oddity is that the tree must be configured with
> > --enable-shared; otherwise, there is no PIC libiberty built, and
> > thus we can't produce shared libraries for the components that
> > depend on it. [...]
>
> At one point we considered (or actually _did_) building individiaul
> libiberty source files within the sid build tree, so that its notion
> of sharedness would be independent of $build/libiberty. Maybe this
> could work.
That's a good idea.
> Thanks for doing this auto* upgrading, it was overdue.
You're welcome!
next prev parent reply other threads:[~2005-06-04 15:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-04 3:18 Jim Blandy
2005-06-04 12:25 ` Frank Ch. Eigler
2005-06-04 15:22 ` Jim Blandy [this message]
2005-06-10 20:21 ` Dave Brolley
2005-06-10 20:34 ` Dave Brolley
2005-06-17 19:18 ` Jim Blandy
2005-06-17 19:24 ` Frank Ch. Eigler
2005-06-17 21:20 ` Dave Brolley
2005-06-20 15:22 ` Jim Blandy
2005-06-20 16:00 ` Dave Brolley
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=vt24qcem9mc.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=fche@redhat.com \
--cc=sid@sources.redhat.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).