From owner-freebsd-current Thu Dec 21 10:55:34 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA26452 for current-outgoing; Thu, 21 Dec 1995 10:55:34 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA26445 Thu, 21 Dec 1995 10:55:30 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id LAA03453; Thu, 21 Dec 1995 11:57:18 -0700 Date: Thu, 21 Dec 1995 11:57:18 -0700 From: Nate Williams Message-Id: <199512211857.LAA03453@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) Cc: current@freebsd.org, nate@freebsd.org Subject: Re: LD hits again :-( In-Reply-To: References: Sender: owner-current@freebsd.org Precedence: bulk > 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