On Tuesday 10 July 2001 03:39, Christoph Egger wrote:
> Hi!
>
> We make now a feature freeze until the _final_ release is done.
> We should freeze the build environment for libgii and libggi now as
> well.
>
> We accept bugfixes, documentation updates and compiler warning/error
> fixes until the _final_ release is done. Note, you have no chance to
> abuse bugfix-patches as a backdoor for new features!
Hi. I think somebody should look at the FreeBSD compilation. When I compile
DVIV, I get tons of warnings, some of which may be relevant to GGI. None of
them is related to my program, so they can only come from GGI or kpathsea (by
the way, 2.0b3 doesn't compile from the ports on 4.3). Here are the warnings:
**********************
/usr/lib/libc_r.so.4: WARNING! setkey(3) not present in the system!
/usr/lib/libc_r.so.4: warning: this program uses gets(), which is
unsafe.
/usr/lib/libc_r.so.4: warning: mktemp() possibly used unsafely;
consider using m
kstemp()
/usr/lib/libc_r.so.4: WARNING! des_setkey(3) not present in the
system!
/usr/lib/libc_r.so.4: WARNING! encrypt(3) not present in the system!
/usr/lib/libc_r.so.4: warning: tmpnam() possibly used unsafely;
consider using m
kstemp()
/usr/lib/libc_r.so.4: warning: this program uses f_prealloc(), which
is stupid.
/usr/lib/libc_r.so.4: WARNING! des_cipher(3) not present in the
system!
/usr/lib/libc_r.so.4: warning: tempnam() possibly used unsafely;
consider using
mkstemp()
**********************
