public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Xi Ruoyao <xry111@xry111.site>
Cc: Dennis Clarke <dclarke@blastwave.org>, 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 17:43:50 +0100	[thread overview]
Message-ID: <CAH6eHdS3pQ+1pbh013KtPyT_Jh42VeTDhm_2xsnr4fi7W+4Bgg@mail.gmail.com> (raw)
In-Reply-To: <d2de2d4cc721d64c1ed26093f858c9e8b847c37e.camel@xry111.site>

On Fri, 13 May 2022 at 17:21, Xi Ruoyao via Gcc-help
<gcc-help@gcc.gnu.org> 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.
>
> 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.
>
> > Other than just RTFM.

Yeah, the point is that unless you use --disable-multilib you need both:

/usr/include/powerpc64-linux-gnu
*and*
/usr/include/powerpc-linux-gnu

i.e. the 64-bit libc headers *and* the 32-bit libc headers.

  reply	other threads:[~2022-05-13 16:44 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 [this message]
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=CAH6eHdS3pQ+1pbh013KtPyT_Jh42VeTDhm_2xsnr4fi7W+4Bgg@mail.gmail.com \
    --to=jwakely.gcc@gmail.com \
    --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).