From: Paolo Bonzini <bonzini@gnu.org>
To: Ian Lance Taylor <iant@google.com>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>,
Diego Novillo <dnovillo@google.com>,
gcc@gcc.gnu.org, java@gcc.gnu.org,
Fortran List <fortran@gcc.gnu.org>
Subject: Re: [LTO merge][0/15] Description of the final 15 patches
Date: Tue, 29 Sep 2009 16:45:00 -0000 [thread overview]
Message-ID: <4AC23984.7090702@gnu.org> (raw)
In-Reply-To: <mcrmy4ddcyw.fsf@dhcp-172-17-9-151.mtv.corp.google.com>
> So all Diego needs to do is pass --enable-shared down to libiberty
> when --enable-lto/--enable-gold. The way to do that is something like
> the appended.
What about just always adding --enable-shared to the host libiberty?
Paolo
next prev parent reply other threads:[~2009-09-29 16:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-29 0:58 Diego Novillo
2009-09-29 2:03 ` Joseph S. Myers
2009-09-29 14:48 ` Ian Lance Taylor
2009-09-29 14:56 ` Diego Novillo
2009-09-29 16:45 ` Paolo Bonzini [this message]
2009-09-29 16:53 ` Ian Lance Taylor
2009-09-29 16:56 ` Paolo Bonzini
2009-09-29 18:54 ` Ian Lance Taylor
2009-09-29 2:07 ` Joseph S. Myers
2009-09-29 13:06 ` Diego Novillo
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=4AC23984.7090702@gnu.org \
--to=bonzini@gnu.org \
--cc=dnovillo@google.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=iant@google.com \
--cc=java@gcc.gnu.org \
--cc=joseph@codesourcery.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).