Date: Thu, 21 Dec 1995 11:57:18 -0700 From: Nate Williams <nate@rocky.sri.MT.net> To: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) <ache@astral.msk.su> Cc: current@freebsd.org, nate@freebsd.org Subject: Re: LD hits again :-( Message-ID: <199512211857.LAA03453@rocky.sri.MT.net> In-Reply-To: <MHL6QsmaU9@deep-thought.demos.su> References: <MHL6QsmaU9@deep-thought.demos.su>
next in thread | previous in thread | raw e-mail | index | archive | help
> cc -O2 -m486 -fno-strength-reduce -L/usr/src/secure/usr.bin/bdes/../../lib/libcipher/obj -o bdes bdes.o -lcipher > bdes.o: WARNING! des_setkey(3) not present in the system! > bdes.o: WARNING! des_cipher(3) not present in the system! > > Note: shared libchipher exists in given -Lpath. This one has me baffled. I'm not even sure if it's something to do with the warning code being incorrectly called, or if indeed it's not linking in the correct libraries. I'm pretty sure it's the linker stating that warning (whether it needs to or not) and not an actual link bug. I verified this by adding warning symbols to the crypt.c in libcipher, and the linker now says. /usr/bin/ld -e start -dc -dp -o bdes /usr/lib/crt0.o -L../../lib/libcipher bdes.o -lcipher /usr/lib/libgcc.a -lc /usr/lib/libgcc.a ld: /usr/lib/libc.so.2.2: multiple definitions for warning symbol `_des_setkey' ld: /usr/lib/libc.so.2.2: multiple definitions for warning symbol `_des_cipher' bdes.o: WARNING! new des_setkey(3) is present in the system! bdes.o: WARNING! new des_cipher(3) is present in the system! For now, I'm going to ignore it. Although it is still a bug, I don't consider it a critical bug. Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199512211857.LAA03453>