public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: Patrick Rother <krd@gulu.net>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: libc-help@sourceware.org
Subject: Re: installation of glibc crashes because of ABI sonames
Date: Mon, 26 Sep 2022 14:53:40 +0200	[thread overview]
Message-ID: <YzGg1BJuOMoEMWOg@vdr.gulu.net> (raw)
In-Reply-To: <87edvyid0t.fsf@mid.deneb.enyo.de>

[-- Attachment #1: Type: text/plain, Size: 812 bytes --]

Hello.

On Mon, Sep 26, 2022 at 01:35:46PM +0200, Florian Weimer wrote:
> > 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 “make install
> DESTDIR=…” 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.

I wasn't aware of the DESTDIR=… option, and interestingly that worked
like a charm.

Problem solved for me, thank you!


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 155 bytes --]

  reply	other threads:[~2022-09-26 12:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-26  5:59 Patrick Rother
2022-09-26 11:35 ` Florian Weimer
2022-09-26 12:53   ` Patrick Rother [this message]
2022-09-26 12:57     ` Adhemerval Zanella Netto
2022-09-26 13:02       ` Florian Weimer
2022-09-26 13:11         ` Adhemerval Zanella Netto

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=YzGg1BJuOMoEMWOg@vdr.gulu.net \
    --to=krd@gulu.net \
    --cc=fw@deneb.enyo.de \
    --cc=libc-help@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).