unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: Stafford Horne <shorne@gmail.com>
Cc: Stafford Horne via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH] NEWS: Mention libpthread, libdl, libutil, libanl integration
Date: Sun, 10 Oct 2021 15:34:39 +0200	[thread overview]
Message-ID: <87fst90zrk.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <YWI3q1OkK5gA9Pv3@antec> (Stafford Horne's message of "Sun, 10 Oct 2021 09:45:31 +0900")

* Stafford Horne:

>> I think we should change the makefiles so that we still keep building
>> libutil.a, but not the shared object, so that it's not necessary to
>> change build systems too much.  Similar for the other shared objects
>> that are now empty.  I'm open to other suggestions, though.
>
> That seems to make sense, it would be nice if there was a way to have a
> deprecated warning when an app tries to link in libutil etc.  This would
> allow for project to clean up their makefiles to avoid unneeded linking.

We can eventually add such a warning, but I think it's premature.  The
empty .a file does not leave any trace at all at run time. And we have
to keep some of these libraries indefinitely anyway because POSIX
requires that certain -l options work.  Empty .a files are the easiest
way to achieve that.

      reply	other threads:[~2021-10-10 13:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-21 12:08 [PATCH] NEWS: Mention libpthread, libdl, libutil, libanl integration Florian Weimer via Libc-alpha
2021-07-29  2:19 ` Carlos O'Donell via Libc-alpha
2021-07-29  7:56 ` Alexander Monakov via Libc-alpha
2021-10-08 22:09 ` Stafford Horne via Libc-alpha
2021-10-09 12:18   ` Florian Weimer
2021-10-10  0:45     ` Stafford Horne via Libc-alpha
2021-10-10 13:34       ` Florian Weimer [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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fst90zrk.fsf@mid.deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    --cc=libc-alpha@sourceware.org \
    --cc=shorne@gmail.com \
    /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).