linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: "Carlos O'Donell" <carlos@redhat.com>,
	linux-man <linux-man@vger.kernel.org>,
	Michael Kerrisk <mtk.manpages@gmail.com>
Subject: Re: [PATCH v2] ld.so.8: Update "Hardware capabilities" section for glibc 2.31.
Date: Wed, 10 Jun 2020 08:00:00 +0200	[thread overview]
Message-ID: <CAKgNAkjB3-LvJaTQ5cHyc-cduD6Yr0_dBrSmN_bih+YOzuBCww@mail.gmail.com> (raw)
In-Reply-To: <87r1uy3sgb.fsf@oldenburg2.str.redhat.com>

Hi Carlos,

What's the status of this patch?

Thanks,

Michael


On Tue, 2 Jun 2020 at 08:14, Florian Weimer <fweimer@redhat.com> wrote:
>
> * Carlos O'Donell:
>
> > +Care should be taken when packaging such application with a package manager,
> > +particularly the scenario where an optimized library is being removed.  With
> > +certain package managers, particularly rpm, the newer version of the
>
> Twice “particularly”.
>
> > +application is installed first, which means that for a period of time during
> > +the upgrade all applications that use the library may start with a mixed set of
> > +libraries e.g.  the old library from the feature-based search path, and new
>
> Commas arount e.g.?
>
> > +libraries from the upgrade. To avoid this scenario the new library version
> > +should delete all known optimized libraries in the post-install phase.
>
> There is a different mechanism: Debian has patched glibc to disable
> hwcap subdirectors if the file /etc/ld.so.nohwcap exists.
>
> You now list the AT_PLATFORM directories (determined by the kernel on
> most architectures) along the regular hwcaps directories, although they
> are handled somewhat differently.  For example, on s390x, if you have a
> “z15” machine (as indicated by AT_PLATFORM), the “z13” subdirectory is
> not selected.  ldconfig will add it to the cache, but it will not be
> used at run time.  I'm not sure if your proposed description gives
> readers the right idea what happens.
>
> Thanks,
> Florian
>


--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

  reply	other threads:[~2020-06-10  6:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-27 20:02 [PATCH] ld.so.8: Update "Hardware capabilities" section for glibc 2.31 Carlos O'Donell
2020-05-28  9:35 ` Florian Weimer
2020-05-28 15:05   ` Carlos O'Donell
2020-06-02  3:09   ` [PATCH v2] " Carlos O'Donell
2020-06-02  6:14     ` Florian Weimer
2020-06-10  6:00       ` Michael Kerrisk (man-pages) [this message]
2020-06-11 20:53         ` Carlos O'Donell
2020-06-13 12:00           ` Florian Weimer
2020-12-04  9:12           ` Florian Weimer
2020-12-04 21:19             ` Carlos O'Donell

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=CAKgNAkjB3-LvJaTQ5cHyc-cduD6Yr0_dBrSmN_bih+YOzuBCww@mail.gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=carlos@redhat.com \
    --cc=fweimer@redhat.com \
    --cc=linux-man@vger.kernel.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 NNTP newsgroup(s).