From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Eric Fisher <joefoxreal@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: [lto] LDFLAGS get lost in stage2
Date: Tue, 19 May 2009 17:56:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.0905191517410.16199@digraph.polyomino.org.uk> (raw)
In-Reply-To: <d6afecde0905182329s6ce8bf98r8386fea2c4c5dbc3@mail.gmail.com>
On Tue, 19 May 2009, Eric Fisher wrote:
> Hello,
>
> I have the libelf installed in a non-standard path, so when I build
> the lto branch, I set the such env variables,
>
> $ export CPPFLAGS="-I<path-to-libelf-headers>" <- Only needed if
> libelf is in a non-standard path
> $ export LDFLAGS="-L<path-to-libelf-lib>" <- Only needed if
> libelf is in a non-standard path
LTO needs a --with-libelf configure option before it merges to trunk, if
it doesn't already have one, as with the options for all the other host
libraries used by GCC.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2009-05-19 15:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-19 12:23 Eric Fisher
2009-05-19 12:57 ` Diego Novillo
2009-05-19 17:56 ` Joseph S. Myers [this message]
2009-05-19 18:26 ` 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=Pine.LNX.4.64.0905191517410.16199@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=joefoxreal@gmail.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).