>
>Have fun, tell me if you get into troubles Cesar.
>
A few: first, when I compile DVIV I get the following errors (actually
warnings) at linking time:
**********************
/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()
**********************
If some of them are GGI related it's something to think about.
Second, installing the ggi port (2.0b3) fails at compile time:
**********************
cc -DHAVE_CONFIG_H -I. -I. -I.. -DBUILDING_LIBGGI -I../include
-I/usr/local/incl
ude -O -pipe -I/usr/local/include -D_REENTRANT -D_THREAD_SAFE -g -Wall
-c dl.c
-fPIC -DPIC -o dl.lo
dl.c: In function `_ggiLoadDL':
dl.c:82: `GGI_ENOFUNC' undeclared (first use in this function)
dl.c:82: (Each undeclared identifier is reported only once
dl.c:82: for each function it appears in.)
dl.c: In function `_ggiAddDL':
dl.c:162: `GGI_ENOMATCH' undeclared (first use in this function)
dl.c:228: `GGI_ENOFUNC' undeclared (first use in this function)
*** Error code 1
**********************
Do you use the ports version?
--
Cesar Augusto Rorato Crusius o _ _ _
Stanford University __o /\_ _ \\o (_)\__/o (_)
e-mail:[EMAIL PROTECTED] _`\<, _>(_) (_)/<_ \_| \ _|/' \/
www.stanford.edu/~crusius (_)/(_) (_) (_) (_) (_)' _\o_
He who sacrifices functionality for ease of use
Loses both and deserves neither
