bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Sergei Trofimovich <slyich@gmail.com>
To: Bruno Haible <bruno@clisp.org>
Cc: bug-gnulib@gnu.org, libc-alpha@sourceware.org
Subject: Re: gnulib's obstack_* symbols in dynamic exports on glibc. Intentional?
Date: Fri, 30 Dec 2022 19:36:17 +0000	[thread overview]
Message-ID: <20221230193617.39b09d81@nz> (raw)
In-Reply-To: <10367839.0AQdONaE2F@nimes>

On Fri, 30 Dec 2022 19:26:48 +0100
Bruno Haible <bruno@clisp.org> wrote:

> Sergei Trofimovich wrote:
> > to my surprise it did have one a set of dynamically exported symbols:
> > 
> >     $ nm -D `which ls` | grep -v '^ '
> >     00000000004c0d40 T _obstack_allocated_p
> >     0000000000534808 D obstack_alloc_failed_handler
> >     00000000004c0bd0 T _obstack_begin
> >     00000000004c0bf0 T _obstack_begin_1
> >     00000000004c0d80 T _obstack_free
> >     00000000004c0e00 T _obstack_memory_used
> >     00000000004c0c10 T _obstack_newchunk  
> There's already a discussion on this topic, that started at
>   https://lists.gnu.org/archive/html/bug-gnulib/2022-12/msg00007.html

Aha, thank you!



      reply	other threads:[~2022-12-30 19:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-30 17:12 gnulib's obstack_* symbols in dynamic exports on glibc. Intentional? Sergei Trofimovich
2022-12-30 18:26 ` Bruno Haible
2022-12-30 19:36   ` Sergei Trofimovich [this message]

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:

  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=20221230193617.39b09d81@nz \
    --to=slyich@gmail.com \
    --cc=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=libc-alpha@sourceware.org \


* 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).