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 23:54:45 +0800 [thread overview]
Message-ID: <e3d4718ace08b48d7beac4fa7bafe71baf1bfc30.camel@xry111.site> (raw)
In-Reply-To: <633a2d74-9f81-8770-7860-50306186fd5e@blastwave.org>
On Tue, 2022-05-10 at 11:51 -0400, Dennis Clarke via Gcc-help wrote:
> On 5/10/22 03:00, Jonathan Wakely wrote:
> > On Tue, 10 May 2022 at 01:54, Dennis Clarke <dclarke@blastwave.org>
> > wrote:
> > >
> > > On 5/9/22 14:51, Jonathan Wakely wrote:
> > > > On Mon, 9 May 2022, 18:16 Dennis Clarke via Gcc-help,
> > > > <gcc-help@gcc.gnu.org>
> > > > 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
/* snip */
> io$
> io$ /opt/bw/build/gcc-12.1.0_debian_10_armv7l_imed.004/./gcc/xgcc
> -print-multiarch
> arm-linux-gnueabi
> io$
Adding --with-float=hard then?
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
prev parent reply other threads:[~2022-05-10 15:55 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
2022-05-10 7:00 ` Jonathan Wakely
2022-05-10 15:51 ` Dennis Clarke
2022-05-10 15:54 ` Xi Ruoyao [this message]
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=e3d4718ace08b48d7beac4fa7bafe71baf1bfc30.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).