From: Xi Ruoyao <xry111@xry111.site>
To: Dennis Clarke <dclarke@blastwave.org>, gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: stage1 gcc bootstrap fails looking for bits/libc-header-start.h
Date: Tue, 10 May 2022 02:14:25 +0800 [thread overview]
Message-ID: <84ae93717f8000f670df64eea48bdc45b0f5b329.camel@xry111.site> (raw)
In-Reply-To: <78ed50e6-c0b5-1002-49a4-e11ec14ee727@blastwave.org>
On Mon, 2022-05-09 at 13:15 -0400, Dennis Clarke via Gcc-help wrote:
>
> Not sure what is causing this on a Linux armv7 32-bit machine but I
> have
> libc6-dev installed and that provides :
>
> # ls -lapb /usr/include/arm-linux-gnueabihf/bits/libc-header-start.h
Normally GCC won't search /usr/include/{multiarch directory} for
headers. So if you want to bootstrap GCC on a distro with such a
directory you'll need --enable-multiarch.
> This is a reasonable little Debian machine
Maybe it's reasonable or not, Debian multiarch is described at:
https://wiki.debian.org/Multiarch/
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2022-05-09 18:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 17:15 Dennis Clarke
2022-05-09 18:14 ` Xi Ruoyao [this message]
2022-05-09 18:51 ` Jonathan Wakely
2022-05-09 18:53 ` Jonathan Wakely
2022-05-09 18:58 ` Dennis Clarke
2022-05-09 19:42 ` Jonathan Wakely
2022-05-09 19:49 ` Dennis Clarke
2022-05-10 0:53 ` Dennis Clarke
2022-05-10 5:50 ` Xi Ruoyao
2022-05-10 7:00 ` Jonathan Wakely
2022-05-10 15:51 ` Dennis Clarke
2022-05-10 15:54 ` Xi Ruoyao
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=84ae93717f8000f670df64eea48bdc45b0f5b329.camel@xry111.site \
--to=xry111@xry111.site \
--cc=dclarke@blastwave.org \
--cc=gcc-help@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).