* [Bug target/106271] Bootstrap on RISC-V on Ubuntu 22.04 LTS: bits/libc-header-start.h: No such file or directory
2022-07-12 17:53 [Bug target/106271] New: Bootstrap on RISC-V on Ubuntu 22.04 LTS: bits/libc-header-start.h: No such file or directory tkoenig at gcc dot gnu.org
@ 2022-07-12 18:02 ` pinskia at gcc dot gnu.org
2022-07-12 20:55 ` tkoenig at gcc dot gnu.org
` (8 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: pinskia at gcc dot gnu.org @ 2022-07-12 18:02 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106271
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Ever confirmed|0 |1
Last reconfirmed| |2022-07-12
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
I suspect configure is not detecting multi-arch correctly or --disable-multilib
interacting with multi-arch support which causes things to be broken.
OR multi-arch support is not in the riscv backend yet.
^ permalink raw reply [flat|nested] 11+ messages in thread
* [Bug target/106271] Bootstrap on RISC-V on Ubuntu 22.04 LTS: bits/libc-header-start.h: No such file or directory
2022-07-12 17:53 [Bug target/106271] New: Bootstrap on RISC-V on Ubuntu 22.04 LTS: bits/libc-header-start.h: No such file or directory 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
` (7 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: tkoenig at gcc dot gnu.org @ 2022-07-12 20:55 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106271
--- Comment #2 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #1)
> I suspect configure is not detecting multi-arch correctly or
> --disable-multilib interacting with multi-arch support which causes things
> to be broken.
> OR multi-arch support is not in the riscv backend yet.
I get the same result without --disable-multilib.
^ permalink raw reply [flat|nested] 11+ messages in thread
* [Bug target/106271] Bootstrap on RISC-V on Ubuntu 22.04 LTS: bits/libc-header-start.h: No such file or directory
2022-07-12 17:53 [Bug target/106271] New: Bootstrap on RISC-V on Ubuntu 22.04 LTS: bits/libc-header-start.h: No such file or directory 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
2023-05-31 15:17 ` tschwinge at gcc dot gnu.org
` (6 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: tschwinge at gcc dot gnu.org @ 2023-05-31 15:12 UTC (permalink / raw)
To: gcc-bugs
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
^ permalink raw reply [flat|nested] 11+ messages in thread
* [Bug target/106271] Bootstrap on RISC-V on Ubuntu 22.04 LTS: bits/libc-header-start.h: No such file or directory
2022-07-12 17:53 [Bug target/106271] New: Bootstrap on RISC-V on Ubuntu 22.04 LTS: bits/libc-header-start.h: No such file or directory tkoenig at gcc dot gnu.org
` (2 preceding siblings ...)
2023-05-31 15:12 ` tschwinge at gcc dot gnu.org
@ 2023-05-31 15:17 ` tschwinge at gcc dot gnu.org
2023-05-31 15:42 ` tschwinge at gcc dot gnu.org
` (5 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: tschwinge at gcc dot gnu.org @ 2023-05-31 15:17 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106271
Thomas Schwinge <tschwinge at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |doko at gcc dot gnu.org
--- Comment #4 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
..., and then I wondered: but how, then, are Debian/Ubuntu building GCC?
Per <https://packages.debian.org/experimental/gcc-13>,
<http://deb.debian.org/debian/pool/main/g/gcc-13/gcc-13_13.1.0-3.debian.tar.xz>,
there is a 'debian/patches/gcc-multiarch.diff' file, which contains "Remaining
multiarch patches, not yet submitted upstream", which (amongst others)
includes:
--- a/src/gcc/config/riscv/t-linux
+++ b/src/gcc/config/riscv/t-linux
@@ -1,3 +1,5 @@
# Only XLEN and ABI affect Linux multilib dir names, e.g. /lib32/ilp32d/
MULTILIB_DIRNAMES := $(patsubst rv32%,lib32,$(patsubst
rv64%,lib64,$(MULTILIB_DIRNAMES)))
MULTILIB_OSDIRNAMES := $(patsubst lib%,../lib%,$(MULTILIB_DIRNAMES))
+
+MULTIARCH_DIRNAME := $(call if_multiarch,$(firstword $(subst -,
,$(target)))-linux-gnu)
^ permalink raw reply [flat|nested] 11+ messages in thread
* [Bug target/106271] Bootstrap on RISC-V on Ubuntu 22.04 LTS: bits/libc-header-start.h: No such file or directory
2022-07-12 17:53 [Bug target/106271] New: Bootstrap on RISC-V on Ubuntu 22.04 LTS: bits/libc-header-start.h: No such file or directory tkoenig at gcc dot gnu.org
` (3 preceding siblings ...)
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
` (4 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: tschwinge at gcc dot gnu.org @ 2023-05-31 15:42 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106271
--- Comment #5 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
With the latter hunk applied (plus manual 'rm gcc/s-mlib gcc/multilib.h' to
regenerate the latter file), I find that this apparently does only address the
'--disable-multilib' case, but not my '--enable-multilib'?
^ permalink raw reply [flat|nested] 11+ messages in thread
* [Bug target/106271] Bootstrap on RISC-V on Ubuntu 22.04 LTS: bits/libc-header-start.h: No such file or directory
2022-07-12 17:53 [Bug target/106271] New: Bootstrap on RISC-V on Ubuntu 22.04 LTS: bits/libc-header-start.h: No such file or directory tkoenig at gcc dot gnu.org
` (4 preceding siblings ...)
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
` (3 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: tschwinge at gcc dot gnu.org @ 2023-08-30 8:16 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106271
Thomas Schwinge <tschwinge at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |law at gcc dot gnu.org,
| |palmer at gcc dot gnu.org,
| |rzinsly at ventanamicro dot com
--- Comment #6 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
I noticed recent commit r14-3387-g47f95bc4be4eb14730ab3eaaaf8f6e71fda47690
"RISC-V: Add multiarch support on riscv-linux-gnu" -- but can't tell off-hand
whether that fixed all the issues here?
^ permalink raw reply [flat|nested] 11+ messages in thread
* [Bug target/106271] Bootstrap on RISC-V on Ubuntu 22.04 LTS: bits/libc-header-start.h: No such file or directory
2022-07-12 17:53 [Bug target/106271] New: Bootstrap on RISC-V on Ubuntu 22.04 LTS: bits/libc-header-start.h: No such file or directory tkoenig at gcc dot gnu.org
` (5 preceding siblings ...)
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
` (2 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: tkoenig at gcc dot gnu.org @ 2023-08-30 11:15 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106271
--- Comment #7 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
(In reply to Thomas Schwinge from comment #6)
> I noticed recent commit r14-3387-g47f95bc4be4eb14730ab3eaaaf8f6e71fda47690
> "RISC-V: Add multiarch support on riscv-linux-gnu" -- but can't tell
> off-hand whether that fixed all the issues here?
As soon as gcc92 is back up, we can test...
https://lists.tetaneutral.net/pipermail/cfarm-users/2023-August/000975.html
^ permalink raw reply [flat|nested] 11+ messages in thread
* [Bug target/106271] Bootstrap on RISC-V on Ubuntu 22.04 LTS: bits/libc-header-start.h: No such file or directory
2022-07-12 17:53 [Bug target/106271] New: Bootstrap on RISC-V on Ubuntu 22.04 LTS: bits/libc-header-start.h: No such file or directory tkoenig at gcc dot gnu.org
` (6 preceding siblings ...)
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
9 siblings, 0 replies; 11+ messages in thread
From: law at gcc dot gnu.org @ 2023-10-07 20:10 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106271
Jeffrey A. Law <law at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |FIXED
--- Comment #8 from Jeffrey A. Law <law at gcc dot gnu.org> ---
I wasn't aware of this BZ when I made the commit referenced in c#6. But yes,
the whole point of that commit was to fix this problem.
^ permalink raw reply [flat|nested] 11+ messages in thread
* [Bug target/106271] Bootstrap on RISC-V on Ubuntu 22.04 LTS: bits/libc-header-start.h: No such file or directory
2022-07-12 17:53 [Bug target/106271] New: Bootstrap on RISC-V on Ubuntu 22.04 LTS: bits/libc-header-start.h: No such file or directory tkoenig at gcc dot gnu.org
` (7 preceding siblings ...)
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
9 siblings, 0 replies; 11+ messages in thread
From: doko at gcc dot gnu.org @ 2023-10-12 6:12 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106271
--- Comment #9 from Matthias Klose <doko at gcc dot gnu.org> ---
yes, that's one which could be also backported. Let me submit the other bits
upstream as well.
^ permalink raw reply [flat|nested] 11+ messages in thread
* [Bug target/106271] Bootstrap on RISC-V on Ubuntu 22.04 LTS: bits/libc-header-start.h: No such file or directory
2022-07-12 17:53 [Bug target/106271] New: Bootstrap on RISC-V on Ubuntu 22.04 LTS: bits/libc-header-start.h: No such file or directory tkoenig at gcc dot gnu.org
` (8 preceding siblings ...)
2023-10-12 6:12 ` doko at gcc dot gnu.org
@ 2023-10-13 20:41 ` pinskia at gcc dot gnu.org
9 siblings, 0 replies; 11+ messages in thread
From: pinskia at gcc dot gnu.org @ 2023-10-13 20:41 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106271
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |14.0
^ permalink raw reply [flat|nested] 11+ messages in thread