From: Mark Kettenis <kettenis@wins.uva.nl>
To: jakub@redhat.com
Cc: aj@suse.de, libc-hacker@sourceware.cygnus.com
Subject: Re: ldconfig Patch
Date: Tue, 30 Nov 1999 06:56:00 -0000 [thread overview]
Message-ID: <199911301456.PAA24045@landau.wins.uva.nl> (raw)
In-Reply-To: <19991130155608.B515@mff.cuni.cz>
Date: Tue, 30 Nov 1999 15:56:08 +0100
From: Jakub Jelinek <jakub@redhat.com>
I'd prefer if you moved readelflib.c one level higher
(linux/sparc/readelflib.c), so that even 32bit ldconfig will handle both
elf32_sparc and elf64_sparc, plus if Hurd does not want ldconfig at all,
then most or everything should go to sysdeps/unix/sysv/linux IMHO.
I don't think sysdeps/unix/sysv/linux is the right place, since
caching is implemented in sysdeps/generic/dl-cache.c.
It's just the Hurd that wants to be different :-).
Mark
next prev parent reply other threads:[~1999-11-30 6:56 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 [this message]
1999-11-30 8:28 ` Andreas Jaeger
1999-12-03 23:59 ` Ulrich Drepper
1999-12-04 2:04 ` Andreas Jaeger
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=199911301456.PAA24045@landau.wins.uva.nl \
--to=kettenis@wins.uva.nl \
--cc=aj@suse.de \
--cc=jakub@redhat.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).