From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Dennis Clarke <dclarke@blastwave.org>
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 08:06:18 +0100 [thread overview]
Message-ID: <CAH6eHdSrwTUGF8G5zGuThutNZSk77RNKYS=VJC6+ZcrskSaujA@mail.gmail.com> (raw)
In-Reply-To: <f0382fcf-96ad-c571-7b7e-2eb033e5dceb@blastwave.org>
On Sat, 14 May 2022 at 00:22, Dennis Clarke <dclarke@blastwave.org> wrote:
>
>
> >>> Honestly, I find that hard to believe.
> >>
> >> Me too!
> >>
> >>>
> >>> One or the other is needed. If you need both, I think you're the only
> >>> person in the world who needs that.
> >>>
> >>
> >> Not bloody likely right? I am looking into that and I think the real
> >> issue is that the versions wanted in the source tree must be the same as
> >> the stuff dragging in by the script kicker download_prerequisites :
> >>
> >> https://gcc.gnu.org/install/prerequisites.html
> >>
> >> The in-tree build is only supported with the GMP version that
> >> download_prerequisites installs.
> >
> > Right, you should be using that script.
> >
> > https://gcc.gnu.org/wiki/InstallingGCC
> >
>
> Well what difference does it make anyways?
> The correct versions are the correct versions.
Well you keep running into problems doing things your way, so I'm
suggesting you just use the well-tested route that is known to work.
>
> > Or (as that page says) just install the debian packages and stop
> > installing them by hand.
>
> But I want to have the libs around as fully non-optimized and no
> assembly single steppable debug enabled full of goodness. Which I
> can certianly do.
>
>
> >> However what do I know? There is another page that says do a bootstrap4
> >> for extra spice and flavour in your result. That doesn't fly.
> >
> > Well stop trying to do weird stuff and just Keep It Simple.
> >
>
> That just drains the joy out of everything.
OK, I'll leave you to it then, have fun.
> >> Okay so it needs 'wget'. Fine. Easy to fix that.
> >
> > It uses curl instead if wget is not found. Most people have one or the
> > other already installed.
>
> Yeah, I prefer curl. Regardless ...
>
> >
> >> Same stuff I use however the mpfr *needs* a patch.
> >
> > Eh? Why?
>
> 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.
next prev parent reply other threads:[~2022-05-14 7:06 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 [this message]
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='CAH6eHdSrwTUGF8G5zGuThutNZSk77RNKYS=VJC6+ZcrskSaujA@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).