From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <fw@deneb.enyo.de>
Received: from albireo.enyo.de (albireo.enyo.de [37.24.231.21])
	by sourceware.org (Postfix) with ESMTPS id 1C5953858CDA
	for <libc-help@sourceware.org>; Mon, 26 Sep 2022 11:35:49 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 1C5953858CDA
Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=deneb.enyo.de
Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=deneb.enyo.de
Received: from [172.17.203.2] (port=41075 helo=deneb.enyo.de)
	by albireo.enyo.de ([172.17.140.2]) with esmtps (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
	id 1ocmOp-003k3O-3l; Mon, 26 Sep 2022 11:35:47 +0000
Received: from fw by deneb.enyo.de with local (Exim 4.94.2)
	(envelope-from <fw@deneb.enyo.de>)
	id 1ocmOo-000Cr5-MV; Mon, 26 Sep 2022 13:35:46 +0200
From: Florian Weimer <fw@deneb.enyo.de>
To: Patrick Rother <krd@gulu.net>
Cc: libc-help@sourceware.org
Subject: Re: installation of glibc crashes because of ABI sonames
References: <YzE/tNWQC2bhA6jH@vdr.gulu.net>
Date: Mon, 26 Sep 2022 13:35:46 +0200
In-Reply-To: <YzE/tNWQC2bhA6jH@vdr.gulu.net> (Patrick Rother's message of
	"Mon, 26 Sep 2022 07:59:16 +0200")
Message-ID: <87edvyid0t.fsf@mid.deneb.enyo.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Status: No, score=-5.9 required=5.0 tests=BAYES_00,KAM_DMARC_STATUS,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=ham autolearn_force=no version=3.4.6
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org
List-Id: <libc-help.sourceware.org>

* Patrick Rother:

> So, before the quoted change is was possible to upgrade glibc from
> source on a running system, but as of 2.34 this is no longer
> possible.

In my experience, it has always been required to use =E2=80=9Cmake install
DESTDIR=3D=E2=80=A6=E2=80=9D to update a running system, and then move the =
resulting
temporary tree into place with a single command.  (The elimination of
symbolic links actually makes this step more reliable because there
are no older glibc .so files left behind.)  It never occurred to me
that we regressed this functionality because it didn't actually work
before for me.