From: "Dmitry V. Levin" <ldv@altlinux.org>
To: arnold@skeeve.com
Cc: bruno@clisp.org, bug-gnulib@gnu.org
Subject: Re: current gnulib regex breaks in gawk
Date: Sun, 18 Apr 2021 00:40:11 +0300 [thread overview]
Message-ID: <20210417214011.GA479@altlinux.org> (raw)
In-Reply-To: <202104171943.13HJhwXM016234@freefriends.org>
On Sat, Apr 17, 2021 at 01:43:58PM -0600, arnold@skeeve.com wrote:
> "Dmitry V. Levin" <ldv@altlinux.org> wrote:
>
> > I've just tried to build the latest commit gawk-5.1.0-260-gde598391 from
> > gawk-5.1-stable branch. Unfortunately, the result executable uses a
> > private glibc interface:
> > $ nm gawk |grep GLIBC_PRIVATE
> > U __libc_dynarray_resize@GLIBC_PRIVATE
> > This makes it unusable at least in GNU/Linux distributions.
>
> Can you explain how this makes it unusable? I see this on Ubuntu
> but the gawk executables run just fine.
>
> What, really, is the problem here? I don't understand.
Well, GLIBC_PRIVATE is a private glibc interface intended for use by
various parts of glibc itself, it can change (and does change from time
to time) without providing backwards compatibility, any symbol in
GLIBC_PRIVATE can disappear or change its semantics during glibc update.
Consequently, packages are not allowed to have dependencies on
GLIBC_PRIVATE.
--
ldv
next prev parent reply other threads:[~2021-04-17 21:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-07 9:57 current gnulib regex breaks in gawk arnold
2021-02-07 10:29 ` Bruno Haible
2021-02-07 12:08 ` arnold
2021-02-07 13:07 ` Bruno Haible
2021-02-08 6:11 ` arnold
2021-02-08 6:36 ` arnold
2021-04-16 22:30 ` Dmitry V. Levin
2021-04-17 19:18 ` arnold
2021-04-17 19:43 ` arnold
2021-04-17 21:40 ` Dmitry V. Levin [this message]
2021-04-18 5:53 ` arnold
2021-04-22 6:52 ` arnold
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210417214011.GA479@altlinux.org \
--to=ldv@altlinux.org \
--cc=arnold@skeeve.com \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.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).