public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] glibc-2.33-r1 crashes out at the start before building.
Date: Wed, 7 Jul 2021 20:42:30 +0000	[thread overview]
Message-ID: <YOYRtuQDWIa/rjpf@ACM> (raw)
In-Reply-To: <2d894e7e-aa9e-92e0-08b5-153f9944db5a@gmail.com>

Hello, Dan.

On Wed, Jul 07, 2021 at 12:28:35 -0700, Daniel Frey wrote:
> On 7/7/21 11:16 AM, Alan Mackenzie wrote:
> > Hello, Gentoo.

> > Would somebody help me here, please.

> > When I try to emerge glibc-2.33-r1, the very first phase of the build
> > crashes out with:

> >   x86_64-pc-linux-gnu-gcc -O2 -pipe -march=native   -Wl,-O1 -Wl,--as-needed  glibc-test.c   -o glibc-test
> >   * Checking that IA32 emulation is enabled in the running kernel ...
> > /usr/portage/sys-libs/glibc/glibc-2.33-r1.ebuild: line 608:   199 Segmentation fault      "${T}/check-ia32-emulation.elf32"
> > [ !! ]
> >   * ERROR: sys-libs/glibc-2.33-r1::gentoo failed (pretend phase):
> >   *   CONFIG_IA32_EMULATION must be enabled in the kernel to compile a multilib glibc.
> >   *
> >   * Call stack:
> >   *              ebuild.sh, line 127:  Called pkg_pretend
> >   *   glibc-2.33-r1.ebuild, line 721:  Called sanity_prechecks
> >   *   glibc-2.33-r1.ebuild, line 670:  Called die
> >   * The specific snippet of code:
> >   *                      [[ $STAT -eq 0 ]] || die "CONFIG_IA32_EMULATION must be enabled in the kernel to compile a multilib glibc."
> >   *
> >   * If you need support, post the output of `emerge --info '=sys-libs/glibc-2.33-r1::gentoo'`,
> >   * the complete build log and the output of `emerge -pqv '=sys-libs/glibc-2.33-r1::gentoo'`.
> >   * The complete build log is located at '/var/tmp/portage/sys-libs/glibc-2.33-r1/temp/build.log'.
> >   * The ebuild environment file is located at '/var/tmp/portage/sys-libs/glibc-2.33-r1/temp/die.env'.
> >   * Working directory: '/var/tmp/portage/sys-libs/glibc-2.33-r1/empty'
> >   * S: '/var/tmp/portage/sys-libs/glibc-2.33-r1/work/glibc-2.33'

> >>>> Failed to emerge sys-libs/glibc-2.33-r1, Log file:

> >>>>   '/var/tmp/portage/sys-libs/glibc-2.33-r1/temp/build.log'

> > What is clearly happening is that the C Compiler is crashing out with a
> > segfault.  I actually have CONFIG_IA32_EMULATION in my kernel config.

> > I've tried this with both GCC-10.3.0 and GCC-9.3.0 with the same results
> > on both.

> > What is going wrong? (Horrible thought - maybe my RAM is failing.)


> It looks to me that it ran a test to see if you have a kernel option 
> enabled.

That's what the test is trying to discern, yes.

> It didn't, looks like it crashed. And then the build warns you 
> that you have to enable CONFIG_IA32_EMULATION in your kernel?

I do have CONFIG_IA32_EMULATION enable in my kernel, and have had for a
long time.  Something segfaulted (?the compiler), which looks like a bug
in wherever.

The emerge script doesn't return the position of the segfault (line 608
is just the beginning of the section).  It hides the return code STAT
(which wouldn't have been set anyway).  And it gives a wrong diagnostic
about a kernel setting.  How is one supposed to debug such a scenario?

> Dan

-- 
Alan Mackenzie (Nuremberg, Germany).


  reply	other threads:[~2021-07-07 20:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-07 18:16 [gentoo-user] glibc-2.33-r1 crashes out at the start before building Alan Mackenzie
2021-07-07 18:23 ` Dale
2021-07-07 18:52   ` Alan Mackenzie
2021-07-07 19:28 ` Daniel Frey
2021-07-07 20:42   ` Alan Mackenzie [this message]
2021-07-08  8:00 ` Sergei Trofimovich
2021-07-13 20:33   ` Alan Mackenzie

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=YOYRtuQDWIa/rjpf@ACM \
    --to=acm@muc.de \
    --cc=gentoo-user@lists.gentoo.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