From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gentoo-user+bounces-196404-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by finch.gentoo.org (Postfix) with ESMTPS id 625CF13933E
for <garchives@archives.gentoo.org>; Wed, 7 Jul 2021 20:42:39 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id EEC39E0D84;
Wed, 7 Jul 2021 20:42:33 +0000 (UTC)
Received: from mail.muc.de (colin.muc.de [193.149.48.1])
by pigeon.gentoo.org (Postfix) with SMTP id 1124DE0C94
for <gentoo-user@lists.gentoo.org>; Wed, 7 Jul 2021 20:42:32 +0000 (UTC)
Received: (qmail 71650 invoked by uid 3782); 7 Jul 2021 20:42:31 -0000
Received: from acm.muc.de (p4fe15ce4.dip0.t-ipconnect.de [79.225.92.228])
(using STARTTLS) by colin.muc.de (tmda-ofmipd) with ESMTP;
Wed, 07 Jul 2021 22:42:31 +0200
Received: (qmail 4791 invoked by uid 1000); 7 Jul 2021 20:42:30 -0000
Date: Wed, 7 Jul 2021 20:42:30 +0000
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] glibc-2.33-r1 crashes out at the start before
building.
Message-ID: <YOYRtuQDWIa/rjpf@ACM>
References: <YOXvjCqK59fOZVcU@ACM>
<2d894e7e-aa9e-92e0-08b5-153f9944db5a@gmail.com>
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <2d894e7e-aa9e-92e0-08b5-153f9944db5a@gmail.com>
X-Submission-Agent: TMDA/1.3.x (Ph3nix)
From: Alan Mackenzie <acm@muc.de>
X-Primary-Address: acm@muc.de
X-Archives-Salt: 32a3504d-f071-4df6-9811-c1dab98f52d0
X-Archives-Hash: 3b520f3490027a7b7a6599af131835ec
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).