This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: signals on latest linux kernels
- To: law at cygnus dot com
- Subject: Re: signals on latest linux kernels
- From: Jauder Ho <jauderho at transmeta dot com>
- Date: Thu, 4 Dec 1997 00:41:37 -0800 (PST)
- cc: egcs-bugs at cygnus dot com
well.. we can use the linux method of generating version codes.
the version code is defined..
Makefile: @echo \#define LINUX_VERSION_CODE `expr $(VERSION) \\*
65536 + $(PATCHLEVEL) \\* 256 + $(SUBLEVEL)` >> .ver
then have a
#if LINUX_VERSION_CODE >= 0x20119
then do something... i.e. do _NSIG instead of NSIG...
--Jauder
On Thu, 4 Dec 1997, Jeffrey A Law wrote:
>
> In message <Pine.LNX.3.96.971203233738.29782A-100000@turtle.transmeta.com>you
> write:
> >
> > linus changed the way signals are handled in the latest kernels..
> > compiling egcs will fail at libiberty/strsignal.c
> >
> > at line 246...
> >
> > the NSIG should be changed to a _NSIG and that should cause gcc to
> > compile fine then..
> This is not a change we can make since it would break all the existing
> systems that use that code -- including all versions of linux that
> don't have Linus's recent change.
>
> We will need to find some other way to handle this problem that doesn't
> break other targets.
>
> Suggestions anyone?
>
> jeff
>
IMPORTANT NOTICE TO RECIPIENTS: The Entire Physical Universe, Including
This Product, May One Day Collapse Back Into an Infinitesimally Small
Space. Should Another Universe Subsequently and Spontaneously Re-Emerge,
the Existence of This Message in That Universe Cannot be Guaranteed.