From: Alexandre Oliva <oliva@gnu.org>
To: Jan Beulich via Gcc-patches <gcc-patches@gcc.gnu.org>
Cc: Jan Beulich <jbeulich@suse.com>, bonzini@gnu.org, neroden@gcc.gnu.org
Subject: Re: [PATCH] configure: arrange to use appropriate objcopy
Date: Fri, 03 Jun 2022 03:44:07 -0300 [thread overview]
Message-ID: <orpmjq456w.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <0fddf82b-750a-67b8-028e-ba0a71a35cf6@suse.com> (Jan Beulich via Gcc-patches's message of "Thu, 2 Jun 2022 17:32:10 +0200")
On Jun 2, 2022, Jan Beulich via Gcc-patches <gcc-patches@gcc.gnu.org> wrote:
> * 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.
Ok, thanks
--
Alexandre Oliva, happy hacker https://FSFLA.org/blogs/lxo/
Free Software Activist GNU Toolchain Engineer
Disinformation flourishes because many people care deeply about injustice
but very few check the facts. Ask me about <https://stallmansupport.org>
next prev parent reply other threads:[~2022-06-03 6:44 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 [this message]
2022-06-04 8:32 ` Jakub Jelinek
2022-06-07 6:12 ` Jan Beulich
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=orpmjq456w.fsf@lxoliva.fsfla.org \
--to=oliva@gnu.org \
--cc=bonzini@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jbeulich@suse.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).