From: Andreas Jaeger <aj@suse.de>
To: drepper@cygnus.com (Ulrich Drepper)
Cc: libc-hacker@sourceware.cygnus.com
Subject: Re: ldconfig Patch
Date: Sat, 04 Dec 1999 02:04:00 -0000 [thread overview]
Message-ID: <u8hfhzuio1.fsf@gromit.rhein-neckar.de> (raw)
In-Reply-To: <m366yfp29w.fsf@localhost.localnet>
>>>>> Ulrich Drepper writes:
Uli> Andreas Jaeger <aj@suse.de> writes:
>> I've renamed the variable has-ldconfig to use-ldconfig and set it to
>> yes for Linux only. I've also followed Jakub's suggestion to use the
>> 32/64 bit version for both Linux Sparc versions.
Uli> Thanks, I've applied the patch. One problem though:
Thanks.
>> * sysdeps/unix/sysv/linux/configure.in: Remove check for ldconfig,
>> set always use_ldconfig instead.
Uli> This change wasn't included.
Sorry, I'm appending it now.
Andreas
============================================================
Index: sysdeps/unix/sysv/linux/configure.in
--- sysdeps/unix/sysv/linux/configure.in 1999/07/14 15:20:41 1.24
+++ sysdeps/unix/sysv/linux/configure.in 1999/12/04 09:57:50
@@ -114,11 +114,8 @@
fi
fi
-# Check whether `ldconfig' sources are available. This will go away as soon
-# as ldconfig is available in GNU libc.
-if test -f $srcdir/elf/ldconfig.c; then
- has_ldconfig=yes
-fi
+# On Linux we use ldconfig
+use_ldconfig=yes
# We need some extensions to the `ldd' script.
changequote(,)
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.rhein-neckar.de
next prev parent reply other threads:[~1999-12-04 2:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-30 6:09 Andreas Jaeger
1999-11-30 6:43 ` Mark Kettenis
1999-11-30 7:13 ` Andreas Jaeger
1999-11-30 6:48 ` Andreas Jaeger
1999-11-30 6:52 ` Jakub Jelinek
1999-11-30 6:56 ` Mark Kettenis
1999-11-30 8:28 ` Andreas Jaeger
1999-12-03 23:59 ` Ulrich Drepper
1999-12-04 2:04 ` Andreas Jaeger [this message]
1999-11-30 7:58 ` Andreas Jaeger
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=u8hfhzuio1.fsf@gromit.rhein-neckar.de \
--to=aj@suse.de \
--cc=drepper@cygnus.com \
--cc=libc-hacker@sourceware.cygnus.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).