From: Ulrich Drepper <drepper@ipd.info.uni-karlsruhe.de>
To: hjl@lucon.org (H.J. Lu)
Cc: vonbrand@sleipnir.valparaiso.cl (Horst von Brand),
libc-linux@gnu.org (GNU C Library),
egcs@cygnus.com, linux-gcc@vger.rutgers.edu (linuxgcc),
linux-kernel@vger.rutgers.edu (linux kernel)
Subject: Re: linux 2.1.71 and libc
Date: Sat, 06 Dec 1997 15:11:00 -0000 [thread overview]
Message-ID: <x74t4mdq6i.fsf@myware.rz.uni-karlsruhe.de> (raw)
In-Reply-To: <m0xeSly-0004ecC@ocean.lucon.org>
hjl@lucon.org (H.J. Lu) writes:
> It happens to glibc 2 also. The latest glibc 2.1 also has 64-bit
> sigset_t.
No. We had and have a 1024 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.
What do you tell? There is not problem like this since at user-level
we use a completely different type.
-- Uli
---------------. drepper at gnu.org ,-. Rubensstrasse 5
Ulrich Drepper \ ,-------------------' \ 76149 Karlsruhe/Germany
Cygnus Solutions `--' drepper at cygnus.com `------------------------
next prev parent reply other threads:[~1997-12-06 15:11 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 ` linux 2.1.71 and libc H.J. Lu
1997-12-06 15:11 ` Ulrich Drepper [this message]
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=x74t4mdq6i.fsf@myware.rz.uni-karlsruhe.de \
--to=drepper@ipd.info.uni-karlsruhe.de \
--cc=egcs@cygnus.com \
--cc=hjl@lucon.org \
--cc=libc-linux@gnu.org \
--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).