From: Dennis Clarke <dclarke@blastwave.org>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: gcc-help <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: Sat, 14 May 2022 12:42:13 -0400 [thread overview]
Message-ID: <31226bc8-df0d-94f7-65fd-1002715e0539@blastwave.org> (raw)
In-Reply-To: <CAH6eHdSrwTUGF8G5zGuThutNZSk77RNKYS=VJC6+ZcrskSaujA@mail.gmail.com>
On 5/14/22 03:06, Jonathan Wakely wrote:
> On Sat, 14 May 2022 at 00:22, Dennis Clarke <dclarke@blastwave.org> wrote:
>>
>>
>>>>> Honestly, I find that hard to believe.
>>>>
>>>> Me too!
.
.
.
>> Those folks working on gmp and mpfr really are the experts. The page
>> says :
>>
>> https://www.mpfr.org/mpfr-current/#download
>>
>> The bugs listed below have been fixed (latest update: 2021-05-17).
>>
>> See https://www.mpfr.org/mpfr-current/#fixed
>>
>> Thirteen bug fixes and from what I have heard directly from some good
>> folks the code in GMP has been subjected to an actual proof. The MPFR
>> code is in process. I gather those bug fixes are valuable and trivial
>> to apply. In fact the download_prerequisites script could be updated
>> to fetch the patches and just apply them.
>
> They don't affect the code GCC uses.
In that case I will apply them.
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
GreyBeard and suspenders optional
next prev parent reply other threads:[~2022-05-14 16:42 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 [this message]
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=31226bc8-df0d-94f7-65fd-1002715e0539@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).