www.delorie.com/archives/browse.cgi | search |
X-Authentication-Warning: | acp3bf.physik.rwth-aachen.de: broeker owned process doing -bs |
Date: | Fri, 5 May 2000 11:39:26 +0200 (MET DST) |
From: | Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de> |
X-Sender: | broeker AT acp3bf |
To: | DJGPP Workers <djgpp-workers AT delorie DOT com> |
Subject: | Re: SIGIOT for DJGPP? |
In-Reply-To: | <3911BF98.EB8FA972@softhome.net> |
Message-ID: | <Pine.LNX.4.10.10005051136460.597-100000@acp3bf> |
MIME-Version: | 1.0 |
Reply-To: | djgpp-workers AT delorie DOT com |
Errors-To: | nobody AT delorie DOT com |
X-Mailing-List: | djgpp-workers AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
On Thu, 4 May 2000, Laurynas Biveinis wrote: > Current CVS GCC sources use SIGIOT signal, which is undefined in DJGPP. Not only in DJGPP. Not even the Digital Unix driven Alpha machine I just checked this against has that. So there's no need to hurry changing DJGPP: this is clearly a problem with the current GCC sources. They shouldn't be using SIGIOT without testing for its existence on the host compiler. We shouldn't try to make DJGPP a combination of all possible Unix flavours that ever existed, so we don't need SIGIOT, I think. Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de) Even if all the snow were burnt, ashes would remain.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |