From: Segher Boessenkool <segher@kernel.crashing.org>
To: Xi Ruoyao <xry111@xry111.site>
Cc: Dennis Clarke <dclarke@blastwave.org>, gcc-help@gcc.gnu.org
Subject: Re: bootstrap fails on Debian ppc64 with fatal error: bits/libc-header-start.h: No such file or directory
Date: Fri, 13 May 2022 12:29:26 -0500 [thread overview]
Message-ID: <20220513172926.GX25951@gate.crashing.org> (raw)
In-Reply-To: <d2de2d4cc721d64c1ed26093f858c9e8b847c37e.camel@xry111.site>
Hi!
On Sat, May 14, 2022 at 12:20:30AM +0800, Xi Ruoyao via Gcc-help wrote:
> On Fri, 2022-05-13 at 12:15 -0400, Dennis Clarke via Gcc-help wrote:
> > > There has to be some other configure option in the salad to mix in.
>
> No, not "has to be". It depends on what you want.
>
> If you don't need multilib (i. e. the ability to compile "Hello world"
> program for 32-bit PPC), then --disable-multilib.
That is not the best idea. It disables *all* multilibs: for example,
for soft float as well. If you want to not enable all targets, just say
so in your --enable-targets=, that is what it is for.
--disable-multilib means "kneecap the compiler, I don't care about all
the functionality this may disable".
> If you need it, you really need to RTFM to get how to install 32-bit
> libraries with headers on Debian, as it's OT with gcc-help.
Yeah, and all this "multiarch" stuff is as well. (GCC does biarch just
fine of course, it is a similar concept, but much older, and it does
work fine. It's not the same thing :-) )
Segher
prev parent reply other threads:[~2022-05-13 17:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 15:11 Dennis Clarke
2022-05-13 15:24 ` Xi Ruoyao
2022-05-13 15:31 ` Xi Ruoyao
2022-05-13 16:15 ` Dennis Clarke
2022-05-13 16:20 ` Xi Ruoyao
2022-05-13 16:43 ` Jonathan Wakely
2022-05-13 20:54 ` Dennis Clarke
2022-05-13 21:03 ` Jonathan Wakely
2022-05-13 22:06 ` Dennis Clarke
2022-05-13 22:49 ` Jonathan Wakely
2022-05-13 23:21 ` Dennis Clarke
2022-05-14 7:06 ` Jonathan Wakely
2022-05-14 16:42 ` Dennis Clarke
2022-05-13 17:29 ` Segher Boessenkool [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=20220513172926.GX25951@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=dclarke@blastwave.org \
--cc=gcc-help@gcc.gnu.org \
--cc=xry111@xry111.site \
/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).