This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] allow setting LDFLAGS_FOR_TARGET in top-level configuration.

From: Paolo Bonzini <bonzini at gnu dot org>
To: "Joseph S. Myers" <joseph at codesourcery dot com>
Cc: Doug Kwan <dougkwan at google dot com>, gcc-patches <gcc-patches at gcc dot gnu dot org>, "Beare, Bruce J" <bruce dot j dot beare at intel dot com>
Date: Mon, 09 May 2011 13:41:58 +0200
Subject: Re: [PATCH] allow setting LDFLAGS_FOR_TARGET in top-level configuration.
Newsgroups: gmane.comp.gcc.patches
References: <BANLkTi=5i+a89scjKDFDoZ+SsrJMJaznoQ@mail.gmail.com> <Pine.LNX.4.64.1105090948260.14069@digraph.polyomino.org.uk>

On 05/09/2011 11:49 AM, Joseph S. Myers wrote:

>       The x86 Android toolchain needs setting LDFLAGS_FOR_TARGET to
>  build.  This patch does that.  The patch was tested by bootstrapping
>  natively on x86_64 linux.  Do I also need to submit this to binutils
>  as well?

My view is that you don't need to*submit*  it separately, but a toplevel
commit to GCC should always be immediately followed by committing the same
changes to the src repository without needing separate approval.

This is correct; but if you want to CC binutils, that's also kind.

Paolo

References:
- [PATCH] allow setting LDFLAGS_FOR_TARGET in top-level configuration.
  - From: Doug Kwan (éæå)
- Re: [PATCH] allow setting LDFLAGS_FOR_TARGET in top-level configuration.
  - From: Joseph S. Myers

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]