localcharset.c: In function `get_charset_aliases':

Gansser, Martin MGansser@rand.de
Thu, 15 Aug 2002 14:47:28 +0200


> Gansser, Martin wrote:
>=20
> > removing CFLAGS=3D"${CFLAGS}=20
> -Werror-implicit-function-declaration" in configure
> > solves this Problem.
>=20
>=20
> Err... are you sure this is a real solution? Now you have an implicit=20
> function declaration during your compile (which doesn't give an error=20
> anymore once you removed that compile option). IMHO implictly=20
> declared functions are highly likely to be a BAD THING (tm), and solving =
this=20
> problem rather means finding the right header file where that=20
> function is declared.
>=20
> How about a 'grep getc_unlocked /usr/include/*.h' or the=20
> other favorite locations for header-files?

here the output:

# grep getc_unlocked /usr/include/*.h

/usr/include/stdio.h:       extern int getc_unlocked(__FILE *);
/usr/include/stdio.h:       extern int getc_unlocked();
/usr/include/stdio.h:#     define getc_unlocked(__p)            (--(__p)->_=
_cnt >=3D 0 ? \
/usr/include/stdio.h:#     define getchar_unlocked()            getc_unlock=
ed(stdin)
/usr/include/stdio.h:#       define getc(__p)           getc_unlocked(__p)
/usr/include/stdio.h:     extern int ungetc_unlocked(int, __FILE *);
/usr/include/stdio.h:     extern int ungetc_unlocked();

now what should I do .. include ...



> Also, I'm not quite sure whether the source files in the intl/=20
> subdirectory actually are written by us. Maybe they have just been=20
> copied by some other i18n tool... anybody has more info here?


Martin