Date: Tue, 28 Mar 2000 14:53:45 -0500 From: Bush Doctor <dervish@goku.cl.msu.edu> To: freebsd-current@freebsd.org Subject: Warnings when linking against libc_r Message-ID: <20000328145345.B41117@goku.cl.msu.edu>
next in thread | raw e-mail | index | archive | help
I'm seeing the following diagnostics with applications linked against libc_r cc -O -pipe -I/usr/local/include -D_REENTRANT -D_THREAD_SAFE -g -Wall -o .libs/structs structs.o -L/usr/local/lib ../../ggi/.libs/libggi.so -lc_r /usr/local/lib/libgg.so /usr/local/lib/libgii.so -Wl,--rpath -Wl,/usr/local/lib /usr/lib/libc.so: warning: tmpnam() possibly used unsafely; consider using mkstemp() /usr/lib/libc.so: warning: tempnam() possibly used unsafely; consider using mkstemp() /usr/lib/libc.so: warning: this program uses gets(), which is unsafe. /usr/lib/libc.so: WARNING! setkey(3) not present in the system! /usr/lib/libc.so: WARNING! des_setkey(3) not present in the system! /usr/lib/libc.so: WARNING! encrypt(3) not present in the system! /usr/lib/libc.so: WARNING! des_cipher(3) not present in the system! /usr/lib/libc.so: warning: mktemp() possibly used unsafely; consider using mkstemp() /usr/lib/libc.so: warning: this program uses f_prealloc(), which is stupid. Can these be ignored? From what I gathered from the mailing list archives this issue has reared its head before. goku.cl.msu.edu:dervish> uname -a FreeBSD goku.cl.msu.edu 5.0-CURRENT FreeBSD 5.0-CURRENT #33: Tue Mar 14 11:25:48 EST 2000 root@goku.cl.msu.edu:/usr/src/sys/compile/GOKU i386 #;^) -- f u cn rd ths, u cn gt a gd jb n cmptr prgrmmng. bush doctor <dervish@goku.cl.msu.edu> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000328145345.B41117>