From owner-freebsd-current  Wed Nov 15 20:16:50 1995
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id UAA15361
          for current-outgoing; Wed, 15 Nov 1995 20:16:50 -0800
Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id UAA15353
          ; Wed, 15 Nov 1995 20:16:43 -0800
Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id VAA08251; Wed, 15 Nov 1995 21:16:34 -0700
Date: Wed, 15 Nov 1995 21:16:34 -0700
From: Nate Williams <nate@rocky.sri.MT.net>
Message-Id: <199511160416.VAA08251@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: Link order needs to be fixed!
In-Reply-To: <OH21hgmK-7@ache.dialup.demos.ru>
References: <OH21hgmK-7@ache.dialup.demos.ru>
Sender: owner-current@freebsd.org
Precedence: bulk

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.

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?



Nate