From: Jan Beulich <jbeulich@suse.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
bonzini@gnu.org, aoliva@gcc.gnu.org, neroden@gcc.gnu.org
Subject: Re: [PATCH] configure: arrange to use appropriate objcopy
Date: Tue, 7 Jun 2022 08:12:26 +0200 [thread overview]
Message-ID: <2e3d0a43-89a6-11ac-21f9-efa6d6d0aaed@suse.com> (raw)
In-Reply-To: <YpsYjd7ZYbvK4pQa@tucnak>
On 04.06.2022 10:32, Jakub Jelinek wrote:
> On Thu, Jun 02, 2022 at 05:32:10PM +0200, Jan Beulich via Gcc-patches wrote:
>> Using the system objcopy is wrong when other configure checks have
>> probed a different set of binutils (I've noticed the problem on a system
>> where the base objcopy can't deal with compressed debug sections).
>> Arrange for the matching one to be picked up, first and foremost if an
>> "in tree" one is available, by mirroring respective logic already
>> present for nm.
>>
>> gcc/
>>
>> * Makefile.in (ORIGINAL_OBJCOPY_FOR_TARGET): New.
>> * configure.ac: Check for objcopy, producing
>> ORIGINAL_OBJCOPY_FOR_TARGET.
>> * configure: Update accordingly.
>> * exec-tool.in (ORIGINAL_OBJCOPY_FOR_TARGET): New.
>> Handle objcopy.
>
> This regressed
> Executing on host: /home/jakub/src/gcc/obj44/gcc/xgcc -B/home/jakub/src/gcc/obj44/gcc/ -fdiagnostics-plain-output -flto -g -gsplit-dwarf -c -o c_lto_pr83719_0.o /home/jakub/src/gcc/gcc/testsuite/gcc.dg/lto/pr83719_0.c (timeout = 300)
> spawn -ignore SIGHUP /home/jakub/src/gcc/obj44/gcc/xgcc -B/home/jakub/src/gcc/obj44/gcc/ -fdiagnostics-plain-output -flto -g -gsplit-dwarf -c -o c_lto_pr83719_0.o /home/jakub/src/gcc/gcc/testsuite/gcc.dg/lto/pr83719_0.c
> cc1: note: '-gsplit-dwarf' is not supported with LTO, disabling
> /home/jakub/src/gcc/obj44/gcc/objcopy: line 120: exec: --: invalid option
> exec: usage: exec [-cl] [-a name] [command [argument ...]] [redirection ...]
> compiler exited with status 1
> FAIL: gcc.dg/lto/pr83719 c_lto_pr83719_0.o assemble, -flto -g -gsplit-dwarf
> for me, both on x86_64-linux and i686-linux.
Hmm, it surely worked for me for both, with and without in-tree binutils
(you don't say which variant you saw the failure with).
> For some reason, I have
> grep OBJCOPY *gcc/Makefile
> gcc/Makefile:ORIGINAL_OBJCOPY_FOR_TARGET =
> prev-gcc/Makefile:ORIGINAL_OBJCOPY_FOR_TARGET =
> stage1-gcc/Makefile:ORIGINAL_OBJCOPY_FOR_TARGET =
What about the corresponding ORIGINAL_NM_FOR_TARGET? And could you provide
one of the config.log instances?
Jan
next prev parent reply other threads:[~2022-06-07 6:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 15:32 Jan Beulich
2022-06-03 6:44 ` Alexandre Oliva
2022-06-04 8:32 ` Jakub Jelinek
2022-06-07 6:12 ` Jan Beulich [this message]
2022-06-07 7:41 ` Jakub Jelinek
2022-06-07 8:13 ` Jan Beulich
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=2e3d0a43-89a6-11ac-21f9-efa6d6d0aaed@suse.com \
--to=jbeulich@suse.com \
--cc=aoliva@gcc.gnu.org \
--cc=bonzini@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=neroden@gcc.gnu.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).