Date: Thu, 16 Nov 1995 07:55:45 +0300 (MSK) From: =?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> To: Nate Williams <nate@rocky.sri.MT.net> Cc: current@freebsd.org, nate@freebsd.org Subject: Re: Link order needs to be fixed! Message-ID: <isHHigm4pB@ache.dialup.demos.ru> In-Reply-To: <199511160416.VAA08251@rocky.sri.MT.net>; from Nate Williams at Wed, 15 Nov 1995 21:16:34 -0700 References: <OH21hgmK-7@ache.dialup.demos.ru> <199511160416.VAA08251@rocky.sri.MT.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <199511160416.VAA08251@rocky.sri.MT.net> Nate Williams
writes:
>KOI8-R writes:
>> BUT! I directly specify -lcipher (which have setkey()) into
>> linker line, i.e.:
>>
>> cc ..objs.. -lcipher
>>
>> It means that setkey() picked not from shared libcipher
>> but from shared libc instead independently of linking
>> order.
>If setkey() is in a shared libcipher, and you have a shared libc() it
>will follow link order.
both libc and libcipher shared as I say.
>It's when you mix and match shared/static libraries there is a problem.
>That has *always* worked, and was never broken. Can ou provide me a
>tar-file with the offending code?
I have per-program static libraries, i.e.:
cc ..objs.. ..program-static-libs.. -lcipher
I'll mail tar file to you shortly.
--
Andrey A. Chernov : And I rest so composedly, /Now, in my bed,
ache@astral.msk.su : That any beholder /Might fancy me dead -
http://dt.demos.su/~ache : Might start at beholding me, /Thinking me dead.
RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?isHHigm4pB>