From: Jakub Jelinek <jakub@redhat.com>
To: Andreas Jaeger <aj@suse.de>
Cc: GNU libc hacker <libc-hacker@sourceware.cygnus.com>
Subject: Re: New ldconfig
Date: Tue, 23 Nov 1999 04:07:00 -0000 [thread overview]
Message-ID: <19991123130904.J515@mff.cuni.cz> (raw)
In-Reply-To: <u8u2mde8vg.fsf@gromit.rhein-neckar.de>
On Tue, Nov 23, 1999 at 12:37:55PM +0100, Andreas Jaeger wrote:
>
> I've written a new ldconfig which I'll place under the GPL and like to
> get added to glibc. ldconfig should be compatible with the current
> ldconfig, but is missing some (IMHO not needed) options. It has been
> successfully tested on ix86, powerpc and alpha.
>
> The program parses libraries of the same endianness and wordsize as
> it's compiled for. It currently can not handle 32 and 64 bit
> libraries simultaneously (if compiled on a 64 bit platform, it parses
> only 64bit libraries). Is this needed anywhere?
Yes. On sparc and I assume on ia64 as well.
>
> I've placed the file ldconfig-19991123.tar.gz on
> ftp.suse.com/pub/people/aj/ The files come with a make file for
> building. You need glibc 2.1 or newer for compilation.
>
> I would appreciate to get your comments. Is there anything missing
> for integration into glibc?
BTW: What was the reason not to integrate H.J.'s latest ldconfig, which
already does a few things this ldconfig does not (in addition to 32/64
handling it e.g. removes duplicates etc.)?
Cheers,
Jakub
___________________________________________________________________
Jakub Jelinek | jakub@redhat.com | http://sunsite.mff.cuni.cz/~jj
Linux version 2.3.18 on a sparc64 machine (1343.49 BogoMips)
___________________________________________________________________
next prev parent reply other threads:[~1999-11-23 4:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-23 3:45 Andreas Jaeger
1999-11-23 4:07 ` Jakub Jelinek [this message]
1999-11-23 4:24 ` Andreas Jaeger
1999-11-23 4:31 ` Jakub Jelinek
1999-11-25 5:30 ` 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=19991123130904.J515@mff.cuni.cz \
--to=jakub@redhat.com \
--cc=aj@suse.de \
--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).