public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
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: Fri, 13 May 2022 22:03:12 +0100	[thread overview]
Message-ID: <CAH6eHdSWEK9BjmFiv5CsRahP2nYpY+YjYKss-TxB1yHMJgL+ag@mail.gmail.com> (raw)
In-Reply-To: <91d0b89c-2001-1b2c-cbd7-d9b390c9ee8b@blastwave.org>

On Fri, 13 May 2022 at 21:55, Dennis Clarke wrote:
> However "configure" always runs just fine regardless of much of anything
> other than the mysterious --with-gmp and mpfr and mpc options. If I do
> not provide those *and* also have the sources extracted into the gcc
> source tree then I get a complaint and configure fails.  If I do provide
> those *and* yes the libs have been prebuilt *and* the sources are in the
> gcc source tree then I get no complaint and the compile then rebuilds
> them anyways. No idea why. [1]

Honestly, I find that hard to believe.

One or the other is needed. If you need both, I think you're the only
person in the world who needs that.

> enceladus$
> enceladus$ ls -lapb --full-time ./stage1-gcc/xgcc ./prev-gcc/xgcc ./gcc/xgcc
> -rwxr-xr-x 1 dclarke devl 5981584 2022-05-13 20:17:17.398378278 +0000
> ./gcc/xgcc
> -rwxr-xr-x 1 dclarke devl 2077720 2022-05-13 19:34:28.401954705 +0000
> ./prev-gcc/xgcc
> -rwxr-xr-x 1 dclarke devl 5145688 2022-05-13 17:18:49.299039174 +0000
> ./stage1-gcc/xgcc
> enceladus$
>
> No stage4 result but whatever :\ we didn't want that anyways ?

Good, there should only be three stages.


> checking for the correct version of gmp.h... yes
> checking for the correct version of mpfr.h... yes
> checking for the correct version of mpc.h... no
> configure: error: Building GCC requires GMP 4.2+, MPFR 3.1.0+ and MPC
> 0.8.0+.

Which version of mpc have you got in the GCC source tree, and how did
you add it there?

What does 'ls -d ../gcc-12.1.0/mpc*' show?

What does config.log (in the build dir) say before it fails? It should
tell you where it found mpc.h and which version it found.

  reply	other threads:[~2022-05-13 21:03 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 [this message]
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=CAH6eHdSWEK9BjmFiv5CsRahP2nYpY+YjYKss-TxB1yHMJgL+ag@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).