From: Nick Clifton <nickc@redhat.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: Paolo Bonzini <bonzini@gnu.org>,
binutils@sourceware.org, gcc-patches@gcc.gnu.org
Subject: Re: *FLAGS_FOR_BUILD vs cross-compiling
Date: Mon, 08 Oct 2007 09:31:00 -0000 [thread overview]
Message-ID: <4709F8E9.6020602@redhat.com> (raw)
In-Reply-To: <200710071130.42177.vapier@gentoo.org>
Hi Mike,
>>>> * configure.ac (CFLAGS_FOR_BUILD, CXXFLAGS_FOR_BUILD,
>>>> LDFLAGS_FOR_BUILD): Default them to host flags only for $host = $build.
>>>> Set default CXXFLAGS_FOR_BUILD to CXXFLAGS, not CFLAGS. Set default
>>>> LDFLAGS_FOR_BUILD to LDFLAGS, not CFLAGS.
>> Yes, ok. Thanks, and sorry.
>
> so how does the committing work here ? i can commit in sourceware, but not
> gcc ...
I have checked your patch into both the gcc and sourceware repositories.
Cheers
Nick
next prev parent reply other threads:[~2007-10-08 9:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200710061910.23606.vapier@gentoo.org>
2007-10-07 4:25 ` Daniel Jacobowitz
2007-10-07 7:19 ` Paolo Bonzini
2007-10-07 15:30 ` Mike Frysinger
2007-10-08 9:31 ` Nick Clifton [this message]
2007-10-08 11:30 ` Mike Frysinger
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=4709F8E9.6020602@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=bonzini@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=vapier@gentoo.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).