unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "Ludovic Courtès via Libc-alpha" <libc-alpha@sourceware.org>
To: Vineet Gupta <vineetg@rivosinc.com>
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 16:37:00 +0100	[thread overview]
Message-ID: <875yezccpv.fsf@gnu.org> (raw)
In-Reply-To: <b186deab-64c5-91f4-4dba-38591ef0f3ce@rivosinc.com> (Vineet Gupta's message of "Sun, 27 Nov 2022 18:24:47 -0800")

Hi,

Vineet Gupta <vineetg@rivosinc.com> skribis:

> On 11/26/22 06:57, Ludovic Courtès wrote:
>> Hi,
>>
>> Vineet Gupta <vineetg@rivosinc.com> skribis:

[...]

>>> riscv glibc multilib builds lack riscv32 prefix binaries. They have a
>>> single set of "riscv64" prefixed binaries supporting both 32 and 64-bit
>>> abis: ilp32/ilp32d/lp64/lp64d using -march/-mabi.

[...]

> The issue is this patch makes an assumption that a triplet prefixed
> cross binary exists, which may not always happen in multilib setups.

Sorry, I had overlooked that.  I trust your judgment.

It does seem that we’ll have either one issue or the other though.
Downstream we can adjust either way, so that’s okay.

Thanks,
Ludo’.

  reply	other threads:[~2022-11-28 15:37 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 [this message]
2022-11-28 19:04       ` Vineet Gupta
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=875yezccpv.fsf@gnu.org \
    --to=libc-alpha@sourceware.org \
    --cc=carlos@redhat.com \
    --cc=gnu-toolchain@rivosinc.com \
    --cc=ludo@gnu.org \
    --cc=maskray@google.com \
    --cc=nelson@rivosinc.com \
    --cc=palmer@rivosinc.com \
    --cc=vineetg@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).