From: hjl@lucon.org (H.J. Lu)
To: vonbrand@sleipnir.valparaiso.cl (Horst von Brand)
Cc: drepper@gnu.ai.mit.edu (Ulrich Drepper),
libc-linux@gnu.ai.mit.edu (GNU C Library),
egcs@cygnus.com, linux-gcc@vger.rutgers.edu (linuxgcc),
linux-kernel@vger.rutgers.edu (linux kernel)
Subject: linux 2.1.71 and libc
Date: Sat, 06 Dec 1997 14:32:00 -0000 [thread overview]
Message-ID: <m0xeSly-0004ecC@ocean.lucon.org> (raw)
In-Reply-To: <199712051010.HAA08944@sleipnir.valparaiso.cl>
>
> linux-2.1.71, libc-5.4.41, binutils-2.8.1.0.17;
There is a problem with linux-2.1.71 and libc 5.4.41. I haven't
found a good solution for it yet.
sigset_t is changed in linux-2.1.71 to 64 bits. That breaks libc 5.4.x.
Also many older binaries using 32 bit sigset_t may not work properly
under linux-2.1.71.
It happens to glibc 2 also. The latest glibc 2.1 also has 64-bit
sigset_t. As the result, old binaries won't work very well. It may
be easier to deal with in glibc 2 using ELF versioning. But it is
not so for libc 5.4.x. For libc 5.4.x, I may do
extern xxxx _new_sigxxxx (xxx);
#define sigxxxx _new_sigxxxx
Ulrich, could you please fix it for glibc 2.1?
BTW, we have to translate between old and new kernel/sigset_t at
the run time. It is a very tricky one.
Linus, I think we shoud provide a new system call for each old system
call which uses sigset_t. Otherwise, we may run into many trouble
with old binaries.
Thanks.
H.J.
next prev parent reply other threads:[~1997-12-06 14:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-06 13:19 egcs-1.0 test results on i586-pc-linux-gnulibc1 Horst von Brand
1997-12-06 14:32 ` H.J. Lu [this message]
1997-12-06 15:11 ` linux 2.1.71 and libc Ulrich Drepper
1997-12-07 9:49 ` Horst von Brand
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=m0xeSly-0004ecC@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=drepper@gnu.ai.mit.edu \
--cc=egcs@cygnus.com \
--cc=libc-linux@gnu.ai.mit.edu \
--cc=linux-gcc@vger.rutgers.edu \
--cc=linux-kernel@vger.rutgers.edu \
--cc=vonbrand@sleipnir.valparaiso.cl \
/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).