From: Dennis Clarke <dclarke@blastwave.org>
To: 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: Mon, 9 May 2022 15:49:27 -0400 [thread overview]
Message-ID: <f942d102-0d2a-9789-7a02-1b1eb22ebaa2@blastwave.org> (raw)
In-Reply-To: <CAH6eHdRXgyBHk9Md0es0Bc3YA_Kz5J--W-gTmRj+K4DEsMD_AQ@mail.gmail.com>
On 5/9/22 15:42, Jonathan Wakely wrote:
> On Mon, 9 May 2022 at 19:58, 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
>>>>
>>>
>>>
>>> But this is not a standard header location, so GCC won't look there.
>>>
>>> You need to use --enable-multiarch to use the Debian MultiArch directory
>>> layout.
>>>
>>
>> Wild. This is not a multi-arch machine but sure let me give that a twirl
>> and see what happens.
>
> It is though. All Debian machines have been for years.
>
> Maybe you're thinking of "multilib" which is different.
Yep. That would be what my brain was pondering. Regardless the little
armv7l unit here seems to be happily churning away on a bootstrap.
Should have a result in a few days. :\
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
GreyBeard and suspenders optional
next prev parent reply other threads:[~2022-05-09 19:49 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 [this message]
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=f942d102-0d2a-9789-7a02-1b1eb22ebaa2@blastwave.org \
--to=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).