From: Paolo Bonzini <bonzini@gnu.org>
To: gcc-patches@gcc.gnu.org, binutils@sourceware.org,
gdb-patches@sourceware.org
Subject: Re: RFA: Save LDFLAGS and CPPFLAGS at the top level
Date: Wed, 22 Oct 2008 03:53:00 -0000 [thread overview]
Message-ID: <48FEA381.3020509@gnu.org> (raw)
In-Reply-To: <20081021201533.GA17491@caradoc.them.org>
Daniel Jacobowitz wrote:
> This patch should make all of {CPP,LD}FLAGS{,_FOR_TARGET,_FOR_BUILD}
> work from the top level. The GDB simulator directories don't always
> listen to them (partially tested patch posted), and I'm sure there are
> other omissions, but this fixes what I could find by inspection.
>
> Tested by building an arm-none-eabi simulator for both current Linux
> host and cross-built Windows host, with CPPFLAGS/LDFLAGS set before
> running configure, and checking every command in the log. Without
> this patch those CPPFLAGS and LDFLAGS are not used, with it they are.
>
> OK?
Yes, thanks.
Paolo
next prev parent reply other threads:[~2008-10-22 3:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 20:16 Daniel Jacobowitz
2008-10-22 3:53 ` Paolo Bonzini [this message]
2008-10-24 21:42 ` Andreas Schwab
2008-10-24 21:57 ` Daniel Jacobowitz
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=48FEA381.3020509@gnu.org \
--to=bonzini@gnu.org \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.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).