On 10 Jul 2001, Thayne Harbaugh wrote:
> GII compiles fine without warning (except the known LIBTOOL problem with
> autoconf).
>
> GGI does this:
> color.c: In function `GGI_aa_setpalvec':
> color.c:45: warning: implicit declaration of function `memcpy'
> mode.c: In function `GGI_xf86dga_checkmode':
> mode.c:372: warning: unused variable `ysize'
> mode.c:372: warning: unused variable `xsize'
> visual.c: In function `GGIopen':
> visual.c:176: warning: implicit declaration of function `memcpy'
> cube3d.c: In function `spawn_bg':
> cube3d.c:507: warning: control reaches end of non-void function
> wrap.o: In function `init_client':
> /home/tharbaug/rpm/BUILD/libggi-cvs/programs/demos/wrap.c:68: the use of
> `tmpnam' is dangerous, better use `mkstemp'
> slimy.c: In function `main':
> slimy.c:281: warning: control reaches end of non-void function
> Makefile:386: warning: overriding commands for target `monitest'
> Makefile:222: warning: ignoring old commands for target `monitest'
> checkmode.c:497:73: warning: trigraph ??) ignored
Fixed and committed, execept the 'mkstemp'-one (don't know, how to do
it right without breaking the code/algorithm). The memcpy() and
memset() warnings can be fixed by adding #include <string.h>
> These all look very fixable - even the problems in the demos.
>
> GALLOC - well, is it part of the 2.0 release?
No. libGAlloc isn't ready for that (it hasn't even reached the
beta-state). Maybe that libgalloc will be released together with GGI
2.1 or 2.2...
> If it is then there's a bit to do with it:
... but thanks. I've fixed the warnings, nonetheless.
CU,
Christoph Egger
E-Mail: [EMAIL PROTECTED]
