From owner-freebsd-current@FreeBSD.ORG Sat May 30 10:25:15 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D72CA106564A; Sat, 30 May 2009 10:25:15 +0000 (UTC) (envelope-from mel.flynn+fbsd.current@mailing.thruhere.net) Received: from mailhub.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id A5BF88FC1D; Sat, 30 May 2009 10:25:15 +0000 (UTC) (envelope-from mel.flynn+fbsd.current@mailing.thruhere.net) Received: from sarevok.dnr.servegame.org (mailhub.rachie.is-a-geek.net [192.168.2.11]) by mailhub.rachie.is-a-geek.net (Postfix) with ESMTP id 45F907E837; Sat, 30 May 2009 02:25:14 -0800 (AKDT) From: Mel Flynn To: freebsd-current@freebsd.org Date: Sat, 30 May 2009 12:24:39 +0200 User-Agent: KMail/1.11.3 (FreeBSD/8.0-CURRENT; KDE/4.2.3; i386; ; ) References: <57200BF94E69E54880C9BB1AF714BBCB5DE72E@w2003s01.double-l.local> <4A20D97B.1030609@freebsd.org> <20090530070306.GQ48776@hoeg.nl> In-Reply-To: <20090530070306.GQ48776@hoeg.nl> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200905301224.40156.mel.flynn+fbsd.current@mailing.thruhere.net> Cc: Ed Schouten , Tim Kientzle Subject: Re: Linking with libarchive fails (Was: Re: buildworld fails.) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 May 2009 10:25:16 -0000 On Saturday 30 May 2009 09:03:06 Ed Schouten wrote: > * Tim Kientzle wrote: > > You need: LDADD=-larchive -lmd -lcrypto > > > > One of the formats supported by libarchive has recently > > gained support for some cryptographic extensions which > > rely on the 'md' and 'crypto' libraries. > > Can't this be solved by linking libarchive to libmd and libcrypto? That > way you don't have to link against those libraries explicitly. On a related note I find it illogical that SHA385/SHA512 is not in libmd while 256 and lower are. Is this a legal thing or infrastructure? -- Mel