From owner-freebsd-current@FreeBSD.ORG Sun May 31 02:50:38 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 3B267106564A for ; Sun, 31 May 2009 02:50:38 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from kientzle.com (kientzle.com [66.166.149.50]) by mx1.freebsd.org (Postfix) with ESMTP id F2EF38FC18 for ; Sun, 31 May 2009 02:50:37 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: (from root@localhost) by kientzle.com (8.14.3/8.14.3) id n4V2oF5c073447; Sat, 30 May 2009 19:50:16 -0700 (PDT) (envelope-from kientzle@freebsd.org) Received: from dark.x.kientzle.com (fw2.kientzle.com [10.123.1.2]) by kientzle.com with SMTP id 8x8y68en4cw8r2k6yuiw9eb3tn; Sat, 30 May 2009 19:50:15 -0700 (PDT) (envelope-from kientzle@freebsd.org) Message-ID: <4A21F067.6000202@freebsd.org> Date: Sat, 30 May 2009 19:50:15 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.21) Gecko/20090409 SeaMonkey/1.1.15 MIME-Version: 1.0 To: Mel Flynn References: <57200BF94E69E54880C9BB1AF714BBCB5DE72E@w2003s01.double-l.local> <4A20D97B.1030609@freebsd.org> <20090530070306.GQ48776@hoeg.nl> <200905301224.40156.mel.flynn+fbsd.current@mailing.thruhere.net> In-Reply-To: <200905301224.40156.mel.flynn+fbsd.current@mailing.thruhere.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Ed Schouten , freebsd-current@freebsd.org 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: Sun, 31 May 2009 02:50:38 -0000 Mel Flynn wrote: > 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? Don't know. Looks like OpenBSD has SHA384 and SHA512 in their standard libraries, so we should be able to crib from there. I don't know the legal issues, though. Tim