ALT Linux Team development discussions
 help / color / mirror / Atom feed
From: Gleb Fotengauer-Malinovskiy <glebfm@altlinux.org>
To: ALT Linux Team development discussions <devel@lists.altlinux.org>
Subject: Re: [devel] I: glibc 2.34
Date: Wed, 13 Oct 2021 18:08:02 +0300
Message-ID: <YWb10s8QWmduhVR2@glebfm.cloud.tilaa.com> (raw)
In-Reply-To: <CA+qzen=kpqMbWThh0Hu_N40sCSW2aNOKsSZvvRM4ZC47Ht_p9w@mail.gmail.com>

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

On Wed, Oct 13, 2021 at 04:34:32PM +0300, Alexey Tourbin wrote:
> On Wed, Oct 13, 2021 at 2:05 PM Gleb Fotengauer-Malinovskiy
> <glebfm@altlinux.org> wrote:
> > В Сизиф совсем скоро попадёт glibc 2.34.
> 
> When an application gets relinked with glibc 2.34, it will no longer
> have the dependency on libpthread.so.0, right?

Yes, DT_NEEDED structure for libpthread.so.0 is not going to be added
anymore.

> Will the application still work with glibc 2.32?

No.

All symbols previously provided by the libpthread, librt, libutil, and
libanl libraries are now supported by libc as compatibility symbols.
Shared objects linked with glibc >= 2.34 will require @GLIBC_2.34
versions of these symbols.

Furthermore, all executables linked with glibc >= 2.34 will be
incompatible with the older versions of glibc due
to linking with the __libc_start_main@@GLIBC_2.34 symbol.

-- 
glebfm

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

  parent reply	other threads:[~2021-10-13 15:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-13 11:05 Gleb Fotengauer-Malinovskiy
2021-10-13 11:16 ` Gleb Fotengauer-Malinovskiy
2021-10-13 12:34 ` Alexey Sheplyakov
2021-10-13 13:34 ` Alexey Tourbin
2021-10-13 15:01   ` Dmitry V. Levin
2021-10-13 15:08   ` Gleb Fotengauer-Malinovskiy [this message]
2021-10-14  8:26 ` Aleksei Nikiforov
2021-10-14 10:27   ` Dmitry V. Levin
2021-10-25 15:08 ` Sergey Y. Afonin

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=YWb10s8QWmduhVR2@glebfm.cloud.tilaa.com \
    --to=glebfm@altlinux.org \
    --cc=devel@lists.altlinux.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

ALT Linux Team development discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
		devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
	public-inbox-index devel

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.devel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git