From: Vineet Gupta <vineetg@rivosinc.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: libc-alpha@sourceware.org, Carlos O'Donell <carlos@redhat.com>,
Fangrui Song <maskray@google.com>,
nelson Chu <nelson@rivosinc.com>,
palmer@rivosinc.com, gnu-toolchain@rivosinc.com
Subject: Re: [PATCH] Revert "Correctly determine libc.so 'OUTPUT_FORMAT' when cross-compiling."
Date: Mon, 28 Nov 2022 11:04:20 -0800 [thread overview]
Message-ID: <88c99025-5017-96a7-b17f-c52de0b24e99@rivosinc.com> (raw)
In-Reply-To: <875yezccpv.fsf@gnu.org>
On 11/28/22 07:37, Ludovic Courtès wrote:
> It does seem that we’ll have either one issue or the other though.
Not necessarily.
> Downstream we can adjust either way, so that’s okay.
If $CC -print-prog-name=objdump is used, I don't see why wrong objdump
would be picked up in your setup.
-Vineet
next prev parent reply other threads:[~2022-11-28 19:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 2:59 [PATCH] Revert "Correctly determine libc.so 'OUTPUT_FORMAT' when cross-compiling." Vineet Gupta
2022-11-26 14:57 ` Ludovic Courtès via Libc-alpha
2022-11-28 2:24 ` Vineet Gupta
2022-11-28 15:37 ` Ludovic Courtès via Libc-alpha
2022-11-28 19:04 ` Vineet Gupta [this message]
2022-11-28 23:25 ` Palmer Dabbelt
2022-11-30 12:39 ` Adhemerval Zanella Netto via Libc-alpha
2022-12-01 0:45 ` Vineet Gupta
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=88c99025-5017-96a7-b17f-c52de0b24e99@rivosinc.com \
--to=vineetg@rivosinc.com \
--cc=carlos@redhat.com \
--cc=gnu-toolchain@rivosinc.com \
--cc=libc-alpha@sourceware.org \
--cc=ludo@gnu.org \
--cc=maskray@google.com \
--cc=nelson@rivosinc.com \
--cc=palmer@rivosinc.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).