From:	Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Bug in gcc or in my install ?
Date:	8 May 2001 13:13:53 GMT
Organization:	Aachen University of Technology (RWTH)
Lines:	18
Message-ID:	<9d8reh$pes$1@nets3.rz.RWTH-Aachen.DE>
References:	<20010508123935 DOT 685 DOT qmail AT web6304 DOT mail DOT yahoo DOT com>
NNTP-Posting-Host:	acp3bf.physik.rwth-aachen.de
X-Trace:	nets3.rz.RWTH-Aachen.DE 989327633 26076 137.226.32.75 (8 May 2001 13:13:53 GMT)
X-Complaints-To:	abuse AT rwth-aachen DOT de
NNTP-Posting-Date:	8 May 2001 13:13:53 GMT
Originator:	broeker@
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Florent Georges <darkman_spam AT yahoo DOT fr> wrote:

> In a first time, I prefer to think that it's a bug in my install,
> instead in gcc, but it's quite strange.

Neither of these. It's a usage error. 

The function you're using, nextafterf(), is not in the ANSI
standardized subset of library functions, and thus its declaration is
turned invisible in gcc -ansi mode. Adding -O2 -Wall flags to your
compile line would have given you a hint in that direction, warning
about an "implicit declaration of function `nextafterf'".

I.e.: this program of yours cannot be compiled by a strict ANSI C 
compiler like 'gcc -ansi'.
-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -