public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/106271] Bootstrap on RISC-V on Ubuntu 22.04 LTS: bits/libc-header-start.h: No such file or directory
Date: Wed, 31 May 2023 15:12:53 +0000 [thread overview]
Message-ID: <bug-106271-4-4zChnzmGke@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106271-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106271
Thomas Schwinge <tschwinge at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tschwinge at gcc dot gnu.org
--- Comment #3 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
Gah, I ran into the same issue on gcc92.
I 'configure'd '--with-arch=rv64imafdc --with-abi=lp64d --enable-multilib'.
(In reply to Andrew Pinski from comment #1)
> OR multi-arch support is not in the riscv backend yet.
That seems to be the case indeed; at least I'm not seeing any 'if_multiarch'
etc. in 'gcc/config/riscv/'.
$ find /usr/include/ -name libc-header-start.h
/usr/include/riscv64-linux-gnu/bits/libc-header-start.h
Also, do potentially further distribution packages have to be installed, for
additional multilibs? Like I have on an Ubuntu x86_64 GN/Linux system:
$ find /usr/include/ -name libc-header-start.h
/usr/include/i386-linux-gnu/bits/libc-header-start.h
/usr/include/x86_64-linux-gnu/bits/libc-header-start.h
$ dpkg -S /usr/include/i386-linux-gnu/bits/libc-header-start.h
/usr/include/x86_64-linux-gnu/bits/libc-header-start.h
libc6-dev:i386: /usr/include/i386-linux-gnu/bits/libc-header-start.h
libc6-dev:amd64: /usr/include/x86_64-linux-gnu/bits/libc-header-start.h
next prev parent reply other threads:[~2023-05-31 15:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 17:53 [Bug target/106271] New: " tkoenig at gcc dot gnu.org
2022-07-12 18:02 ` [Bug target/106271] " pinskia at gcc dot gnu.org
2022-07-12 20:55 ` tkoenig at gcc dot gnu.org
2023-05-31 15:12 ` tschwinge at gcc dot gnu.org [this message]
2023-05-31 15:17 ` tschwinge at gcc dot gnu.org
2023-05-31 15:42 ` tschwinge at gcc dot gnu.org
2023-08-30 8:16 ` tschwinge at gcc dot gnu.org
2023-08-30 11:15 ` tkoenig at gcc dot gnu.org
2023-10-07 20:10 ` law at gcc dot gnu.org
2023-10-12 6:12 ` doko at gcc dot gnu.org
2023-10-13 20:41 ` pinskia at gcc dot gnu.org
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-106271-4-4zChnzmGke@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).