From: Dennis Clarke <dclarke@blastwave.org>
To: 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:15:20 -0400 [thread overview]
Message-ID: <05fc1487-9080-5822-4e32-81cf49d13961@blastwave.org> (raw)
In-Reply-To: <7f1f1a2f-6c9f-d3ad-8aa1-499c87eb8caf@blastwave.org>
> There has to be some other configure option in the salad to mix in.
>
> Would love to hear thoughts.
>
Other than just RTFM.
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
GreyBeard and suspenders optional
next prev parent reply other threads:[~2022-05-13 16:15 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 [this message]
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
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=05fc1487-9080-5822-4e32-81cf49d13961@blastwave.org \
--to=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).