public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Horst von Brand <vonbrand@sleipnir.valparaiso.cl>
To: hjl@lucon.org (H.J. Lu)
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: Re: linux 2.1.71 and libc
Date: Sun, 07 Dec 1997 09:49:00 -0000	[thread overview]
Message-ID: <199712071300.KAA05522@sleipnir.valparaiso.cl> (raw)
In-Reply-To: <m0xeSly-0004ecC@ocean.lucon.org>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1193 bytes --]

hjl@lucon.org (H.J. Lu) said:
> "Horst von Brand" at Dec 5, 97 07:10:52 am said:
> > 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.

Hum.... I had to take a look at this (I needed to compile modutils-2.1.55,
but the compilation blew up due to incorrect types). The fix for this is
simple: In /usr/include/signal.h there are several #defines for the sigset
manipulation functions that assume 32 bits (or an unsigned long, at least),
they are at the start of an #ifdef __OPTIMIZE__ Just move the #ifdef 0 a
couple of lines lower up, and they aren't included. This will need a closer
look...

OTOH, I took a look at the whole stuff in 2.1.71, and I can't see anything
that might break 32-signal applications in there. If it did, my system
wouldn't work, I guess...
-- 
Horst von Brand                             vonbrand@sleipnir.valparaiso.cl
Casilla 9G, Viña del Mar, Chile                               +56 32 672616

      parent reply	other threads:[~1997-12-07  9:49 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
1997-12-07  9:49   ` Horst von Brand [this message]

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=199712071300.KAA05522@sleipnir.valparaiso.cl \
    --to=vonbrand@sleipnir.valparaiso.cl \
    --cc=drepper@gnu.ai.mit.edu \
    --cc=egcs@cygnus.com \
    --cc=hjl@lucon.org \
    --cc=libc-linux@gnu.ai.mit.edu \
    --cc=linux-gcc@vger.rutgers.edu \
    --cc=linux-kernel@vger.rutgers.edu \
    /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).