From:	Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Another cross-compiler problem!
Date:	11 Oct 2001 11:34:36 GMT
Organization:	Aachen University of Technology (RWTH)
Lines:	31
Message-ID:	<9q404c$kc1$1@nets3.rz.RWTH-Aachen.DE>
References:	<20011011060443 DOT 2623 DOT qmail AT web9103 DOT mail DOT yahoo DOT com>
NNTP-Posting-Host:	acp3bf.physik.rwth-aachen.de
X-Trace:	nets3.rz.RWTH-Aachen.DE 1002800076 20865 137.226.32.75 (11 Oct 2001 11:34:36 GMT)
X-Complaints-To:	abuse AT rwth-aachen DOT de
NNTP-Posting-Date:	11 Oct 2001 11:34:36 GMT
Originator:	broeker@
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

ROLAND <roland_asmann AT yahoo DOT com> wrote:

> Well, I'm still working to find out where the problem with <time.h>
> is, but the problem with <signal.h> is in the fact that my sparc
> <signal.h> has a SIGBUS variable, which I use in my program to
> capture BUS-Errors. On my PC <signal.h> does not contain
> SIGBUS. 

Of course it doesn't --- Intel CPU's don't generate bus errors

But that's really very simple to get around, since all SIGSOMETHINGS's
are #defines. I.e. you can just enclose the relevant parts of your
program in

	#ifdef SIGBUS
	    /* code dealing with SIGBUS here */
	#endif

and that's that.

> You mantioned <inttypes.h> to be a standard from GCC, 

No. It said it's a C99'ism, which means it is a concept standardized
only rather recently. GCC (and especially the official version used
with DJGPP, which is still 2.95.3 IIRC) hasn't caught up to it, yet,
so it *will* be provided by GCC, sometime in the near future,
probably.  But not yet.

-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -