From: Andrew Pinski <pinskia@gmail.com>
To: Jeff Law <law@redhat.com>, binutils <binutils@sourceware.org>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, Ian Lance Taylor <ian@airs.com>
Subject: Re: [PATCH/TopLevel] Fix compiling libgo with a combined sources
Date: Sat, 03 Jan 2015 22:55:00 -0000 [thread overview]
Message-ID: <CA+=Sn1kLwMubQ_9b7sPsu2JhEgnAmcg3M61DQkyMOf_zNXoR7g@mail.gmail.com> (raw)
In-Reply-To: <5473A3D3.901@redhat.com>
On Mon, Nov 24, 2014 at 1:32 PM, Jeff Law <law@redhat.com> wrote:
> On 11/22/14 21:20, Andrew Pinski wrote:
>>
>> Hi,
>> The problem here is here is that OBJCOPY is not being set to the
>> newly built objcopy when compiling libgo. This patch adds
>> OBJCOPY_FOR_TARGET to the toplevel configure/Makefile so that when
>> libgo is compiled OBJCOPY is set to OBJCOPY_FOR_TARGET.
>>
>> I noticed this issue when building an aarch64 cross compile on an
>> older system where objcopy did not understand aarch64.
>>
>> OK? Bootstrapped and tested on x86_64 with no regressions. Also
>> tested with a combined build for a cross compiler to
>> aarch64-linux-gnu.
>>
>> Thanks,
>> Andrew Pinski
>>
>>
>> * Makefile.def (flags_to_pass): Pass OBJCOPY_FOR_TARGET also.
>> * Makefile.tpl (HOST_EXPORTS): Add OBJCOPY_FOR_TARGET.
>> (BASE_TARGET_EXPORTS): Add OBJCOPY.
>> (OBJCOPY_FOR_TARGET): New variable.
>> (EXTRA_TARGET_FLAGS): Add OBJCOPY.
>> * Makefile.in: Regenerate.
>> * configure.ac: Check for already installed target objcopy.
>> Also GCC_TARGET_TOOL on objcopy.
>> * configure: Regenerate.
>
> OK
Committed to GCC and gdb/binutils repos now.
Thanks,
Andrew
> Jeff
>
>
next parent reply other threads:[~2015-01-03 22:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+=Sn1nMV44+3jMMZ0WJQbX=KTaETk7ZC5ZzOv3K-wYdQiCPkw@mail.gmail.com>
[not found] ` <5473A3D3.901@redhat.com>
2015-01-03 22:55 ` Andrew Pinski [this message]
2015-01-04 9:35 ` Bin.Cheng
2015-01-04 10:31 ` pinskia
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='CA+=Sn1kLwMubQ_9b7sPsu2JhEgnAmcg3M61DQkyMOf_zNXoR7g@mail.gmail.com' \
--to=pinskia@gmail.com \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=ian@airs.com \
--cc=law@redhat.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