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 go/103889] gccgo is unable to find its standard library by default on 64-Bit RISC-V
Date: Sun, 02 Jan 2022 13:00:28 +0000	[thread overview]
Message-ID: <bug-103889-4-ers65BxT8k@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 #7 from John Doe <bau2wux4sh at pkv73 dot anonbox.net> ---
(In reply to Andrew Pinski from comment #5)
> I should note that libgo is not able to compile for musl on the FSF GCC
> until just recently, after r12-5979.

This patch is included with the Alpine version of GCC, see
https://git.alpinelinux.org/aports/tree/main/gcc/0040-stddef.h-add-support-for-musl-typedef-macro-guards.patch
there are also additional patches which need to be merged upstream before one
can use gcc-go on musl (see the Alpine Git for the complete list).  As I said:
Alpine is currently working on upstreaming these patches. For example,
https://gcc.gnu.org/pipermail/gcc-patches/2021-December/587142.html

The problem described in this bug report should not be specific to any of those
gccgo/libgo patches, it rather seems to be a problem with the default
LIBRARY_PATH (see my previous comment).

> Is there a way you can test GCC 12?

I need to rebase the Alpine patchset for that GCC 12 then I assume, I could
that do that if all else fails.

  parent reply	other threads:[~2022-01-02 13:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-02 11:20 [Bug go/103889] New: " 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 [this message]
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
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-ers65BxT8k@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).