From: John Campbell <jdc.rpv@cox.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Heads Up - glibc-2.27 breaks my system
Date: Fri, 2 Feb 2018 21:42:06 -0800 [thread overview]
Message-ID: <d4659946-7bb0-25fe-765c-9486c66e5ba4@cox.net> (raw)
In-Reply-To: <5x7d1x01i1kktTk01x7eRl>
On 02/02/2018 01:07 PM, Floyd Anderson wrote:
> Hi Helmut,
>
> On Fri, 02 Feb 2018 18:34:23 +0100
> Helmut Jarausch <jarausch@skynet.be> wrote:
>> With glibc-2.27 installed I cannot compile anything, since most
>> packages try to include <gnu/stubs-32.h>
>> which doesn't exit any more.
>> And downgrading glibc using a binary package doesn't work.
>>
>> It looks like I have to restore my system from a recent backup,
>> very annoying!
>
> Restoring your backup is probably faster but I want to point out the
> possibility of an intermediate build chroot [1] to get back a working
> toolchain. This helped me in the past to solve troubles with glibc and
> when I didn’t knew about buildpkg/buildsyspkg for FEATURES variable.
It's been fixed now. glibc-2.27-r1 is in the tree and re-instates the
x32 libs and headers.
I just emerged the new lib and everything is find. I have
FEATURES=preserve-libs set so I'm not sure how the missing x32 libs
might effect your compile but I had no issues.
next prev parent reply other threads:[~2018-02-03 5:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-02 17:34 [gentoo-user] Heads Up - glibc-2.27 breaks my system Helmut Jarausch
2018-02-02 21:07 ` Floyd Anderson
[not found] ` <5x7d1x01i1kktTk01x7eRl>
2018-02-03 5:42 ` John Campbell [this message]
2018-02-03 5:54 ` Dale
2018-02-03 8:23 ` [gentoo-user] " Nikos Chantziaras
2018-02-03 14:08 ` Dale
2018-02-04 18:01 ` Nikos Chantziaras
2018-02-04 18:23 ` Dale
2018-02-03 9:50 ` [gentoo-user] " Helmut Jarausch
2018-02-03 15:11 ` Marc Joliet
2018-02-03 17:34 ` Helmut Jarausch
2018-02-03 17:56 ` Marc Joliet
2018-02-03 23:21 ` Bill Kenworthy
2018-02-04 11:52 ` Helmut Jarausch
2018-02-04 8:39 ` Neil Bothwick
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=d4659946-7bb0-25fe-765c-9486c66e5ba4@cox.net \
--to=jdc.rpv@cox.net \
--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