public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Stafford Horne <shorne@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] login: Add back libutil as an empty library
Date: Thu, 28 Oct 2021 21:19:43 +0000 (GMT)	[thread overview]
Message-ID: <20211028211943.440A33858416@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=b3cf94ef15f0bb6ff336907e31ab0064a0381916

commit b3cf94ef15f0bb6ff336907e31ab0064a0381916
Author: Stafford Horne <shorne@gmail.com>
Date:   Wed Oct 13 21:43:50 2021 +0900

    login: Add back libutil as an empty library
    
    There are several packages like sysvinit and buildroot that expect
    -lutil to work.  Rather than impacting them with having to change
    the linker flags provide an empty libutil.a.

Diff:
---
 login/Makefile | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/login/Makefile b/login/Makefile
index 4e6b97734d..e2bdcb1b0d 100644
--- a/login/Makefile
+++ b/login/Makefile
@@ -46,10 +46,10 @@ vpath %.c programs
 tests := tst-utmp tst-utmpx tst-grantpt tst-ptsname tst-getlogin tst-updwtmpx \
   tst-pututxline-lockfail tst-pututxline-cache
 
-ifeq ($(have-GLIBC_2.33),yes)
 # Empty compatibility library for old binaries.
 extra-libs      := libutil
 extra-libs-others := $(extra-libs)
+ifeq ($(have-GLIBC_2.33),yes)
 libutil-routines := libutil-compat
 libutil-shared-only-routines := libutil-compat
 
@@ -57,6 +57,8 @@ libutil-shared-only-routines := libutil-compat
 # link is not installed.
 install-lib-ldscripts = libutil.so
 $(inst_libdir)/libutil.so:
+else  # not $(have-GLIBC_2.33)
+libutil-inhibit-o = $(filter-out .o,$(object-suffixes))
 endif # $(have-GLIBC_2.33)
 
 include ../Rules


                 reply	other threads:[~2021-10-28 21:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20211028211943.440A33858416@sourceware.org \
    --to=shorne@sourceware.org \
    --cc=glibc-cvs@sourceware.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).