public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bau2wux4sh at pkv73 dot anonbox.net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/103889] gccgo is unable to find its standard library by default on 64-Bit RISC-V due to musl not using multilib but still uses t-linux
Date: Sun, 02 Jan 2022 15:31:23 +0000	[thread overview]
Message-ID: <bug-103889-4-Vdl8o4eFvi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103889-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103889

--- Comment #13 from John Doe <bau2wux4sh at pkv73 dot anonbox.net> ---
(In reply to Andrew Pinski from comment #12)
> Because the Linux-gnu folks will always use lib64 instead of lib here. So
> there is no need to fix gcc/config/riscv/t-linux. There is a LSF on purpose
> which I thought defined this all for *-*-linux-gnu across distros.

What is LSF? Do you mean LSB (Linux Standard Base)? Because the comment in the 
t-linux64 i386 configuration file explicitly states:

> The LSB does not enforce the use of /lib64 and /usr/lib64

I might be repeating myself but other architecture configuration files
explicitly include a check to ensure that this directory exists, e.g.:

> $(if $(wildcard $(shell echo $(SYSTEM_HEADER_DIR))/../../usr/lib32),../lib32,../lib)

Then again I am personally not very familiar with these configuration files, it
just seems odd to me that the RISC-V one doesn't have such a check.

  parent reply	other threads:[~2022-01-02 15:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-02 11:20 [Bug go/103889] New: gccgo is unable to find its standard library by default on 64-Bit RISC-V bau2wux4sh at pkv73 dot anonbox.net
2022-01-02 11:22 ` [Bug go/103889] " bau2wux4sh at pkv73 dot anonbox.net
2022-01-02 11:45 ` schwab@linux-m68k.org
2022-01-02 11:48 ` bau2wux4sh at pkv73 dot anonbox.net
2022-01-02 12:15 ` schwab@linux-m68k.org
2022-01-02 12:52 ` pinskia at gcc dot gnu.org
2022-01-02 12:54 ` bau2wux4sh at pkv73 dot anonbox.net
2022-01-02 13:00 ` bau2wux4sh at pkv73 dot anonbox.net
2022-01-02 13:01 ` pinskia at gcc dot gnu.org
2022-01-02 13:20 ` bau2wux4sh at pkv73 dot anonbox.net
2022-01-02 13:25 ` [Bug go/103889] gccgo is unable to find its standard library by default on 64-Bit RISC-V due to musl not using multilib but still uses t-linux pinskia at gcc dot gnu.org
2022-01-02 14:01 ` [Bug target/103889] " bau2wux4sh at pkv73 dot anonbox.net
2022-01-02 14:05 ` pinskia at gcc dot gnu.org
2022-01-02 15:31 ` bau2wux4sh at pkv73 dot anonbox.net [this message]
2022-01-03 21:32 ` wilson at gcc dot gnu.org
2022-01-07 10:06 ` bau2wux4sh at pkv73 dot anonbox.net

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=bug-103889-4-Vdl8o4eFvi@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).