From: Xi Ruoyao <xry111@xry111.site>
To: Dennis Clarke <dclarke@blastwave.org>,
Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: 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 13:50:00 +0800 [thread overview]
Message-ID: <1481bed41648c4d50d82028cf9738ecd31bc4f44.camel@xry111.site> (raw)
In-Reply-To: <2db3724d-b2a0-6356-3d0b-d7716b5c8e38@blastwave.org>
On Mon, 2022-05-09 at 20:53 -0400, Dennis Clarke via Gcc-help wrote:
> So that sort of looks the same but also I am not sure what is needed
> here. As usual the package libc6-dev provides :
>
> /usr/include/arm-linux-gnueabihf/bits/libc-header-start.h
>
> However that is in a weird place. Do I need host/target/foobar etc?
Generally multiarch directory names are encoded in gcc/config/{arch}/t-
linux* files and they have not to be exactly same as --target.
Try:
/opt/bw/build/gcc-12.1.0_debian_10_armv7l_imed.004/./gcc/xgcc -print-multiarch
This command will print the multiarch directory name. And you can
compare it with "arm-linux-gnueabihf" to see what's happening.
(The OP's mail server doesn't like me, hope he can see the thread via
list or someone can forward me.)
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2022-05-10 5:50 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
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 [this message]
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=1481bed41648c4d50d82028cf9738ecd31bc4f44.camel@xry111.site \
--to=xry111@xry111.site \
--cc=dclarke@blastwave.org \
--cc=gcc-help@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
/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).