X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-bounces using -f
From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Conflicting types-warning
Date: 18 Mar 2002 10:58:01 GMT
Organization: Aachen University of Technology (RWTH)
Lines: 31
Message-ID: <a74h7p$hqk$1@nets3.rz.RWTH-Aachen.DE>
References: <cd0304ab DOT 0203171037 DOT 62442d9d AT posting DOT google DOT com>
NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de
X-Trace: nets3.rz.RWTH-Aachen.DE 1016449081 18260 137.226.32.75 (18 Mar 2002 10:58:01 GMT)
X-Complaints-To: abuse AT rwth-aachen DOT de
NNTP-Posting-Date: 18 Mar 2002 10:58:01 GMT
Originator: broeker@
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

dshnv <dshnv AT www DOT com> wrote:

> I use my own LIBC instead of djgpp's so I understand why I get these
> warnings, but is there some way to turn these
> built-in-conflict-warnings off? 

You should probably start by making your own LIBC use correct,
standard-compliant argument and return types for standardized
functions.  I.e. if your memcpy has any other signature than

	void *memcpy(void *dest, const void *src, size_t n);

then that is a serious bug in your libc.  A function that doesn't
fulfill the definition of the ANSI C Standard about memcpy has no
right to call itself memcpy.

> Maybe some sort of `--no-builtin' option?

Quoting the GCC docs, node "C Dialect Options":

`-fno-builtin'
     Don't recognize builtin functions that do not begin with two
     leading underscores.  Currently, the functions affected include
     `abort', `abs', `alloca', `cos', `exit', `fabs', `ffs', `labs',
     `memcmp', `memcpy', `sin', `sqrt', `strcmp', `strcpy', and
     `strlen'.

But you really shouldn't have to use this flag.
-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.