From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Dennis Clarke <dclarke@blastwave.org>
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 08:00:50 +0100 [thread overview]
Message-ID: <CAH6eHdQSpJktZaV1BLJwopg+mCEUN-CN5JNcveS0RqfK2DxJaA@mail.gmail.com> (raw)
In-Reply-To: <2db3724d-b2a0-6356-3d0b-d7716b5c8e38@blastwave.org>
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
> >>
> >
> >
> > 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.
> >
>
> Sadly things have not worked out any better. :(
>
> Configure still looks nice :
>
> io$
> io$ uname -a
> Linux io 4.4.194 #52 SMP Tue Oct 26 08:35:58 UTC 2021 armv7l GNU/Linux
> io$ gcc --version
> gcc (Debian 8.3.0-6) 8.3.0
> Copyright (C) 2018 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions. There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>
> io$
>
> All the usual baseline tools are around. Also gmp/mpfr/mpc are extracted
> in the source tree as per normal.
>
> io$ CC='gcc -march=armv7-a -mtune=cortex-a17 -mfpu=vfpv4-d16 -marm' \
> > CXX='g++ -march=armv7-a -mtune=cortex-a17 -mfpu=vfpv4-d16 -marm' \
> > LD_RUN_PATH='/opt/gcc/imed/gcc12/lib:/opt/bw/lib' \
> > ../gcc-12.1.0/configure --prefix=/opt/gcc/imed/gcc12 \
> > --enable-multiarch \
> > --disable-nls --enable-threads=posix --enable-shared \
> > --with-gmp=/opt/bw --with-mpfr=/opt/bw --with-mpc=/opt/bw \
Wait, what? You said "gmp/mpfr/mpc are extracted in the source tree as
per normal" so why are you telling GCC to get them from /opt/bw?
Xi Ruoyao is sending replies that you're apparently not receiving, see
https://gcc.gnu.org/pipermail/gcc-help/2022-May/141536.html
next prev parent reply other threads:[~2022-05-10 7:01 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 [this message]
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=CAH6eHdQSpJktZaV1BLJwopg+mCEUN-CN5JNcveS0RqfK2DxJaA@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--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).