X-Authentication-Warning:	delorie.com: mailnull set sender to djgpp-workers-bounces using -f
Subject:	Re: conflicting types for bzero (gcc303)
From:	Tim Van Holder <tim DOT van DOT holder AT pandora DOT be>
To:	djgpp-workers AT delorie DOT com
Cc:	ST001906 AT HRZ1 DOT HRZ DOT TU-Darmstadt DOT De
In-Reply-To:	<6048-Thu07Feb2002075445+0200-eliz@is.elta.co.il>
References:	<000201c1af4d$2d84e030$747d76d5 AT zastaixp>
	<6048-Thu07Feb2002075445+0200-eliz AT is DOT elta DOT co DOT il>
X-Mailer:	Evolution/1.0.2
Date:	07 Feb 2002 09:03:15 +0100
Message-Id:	<1013068997.9713.6.camel@bender.falconsoft.be>
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, 2002-02-07 at 06:54, Eli Zaretskii wrote:
> > From: "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
> > Date: Wed, 6 Feb 2002 21:30:54 +0100
> > 
> > Our prototypes are normally not even seen; gcc uses its own stdlib.h
> 
> The prototypes for bzero and bcopy are on string.h, not stdlib.h.  So
> using GCC's own headers will not solve that, at least not for
> programs which include string.h.
> 
OK - so I was wrong, and meant to say string.h instead of stdlib.h.
The point is that gcc only complains if you force it to use our own
headers by explicitly listing -I$DJDIR/include on the command line.
If you don't do so, I assume it uses its own private version.

- Raw text -