Date: Sat, 30 May 2009 19:50:15 -0700 From: Tim Kientzle <kientzle@freebsd.org> To: Mel Flynn <mel.flynn+fbsd.current@mailing.thruhere.net> Cc: Ed Schouten <ed@80386.nl>, freebsd-current@freebsd.org Subject: Re: Linking with libarchive fails (Was: Re: buildworld fails.) Message-ID: <4A21F067.6000202@freebsd.org> In-Reply-To: <200905301224.40156.mel.flynn%2Bfbsd.current@mailing.thruhere.net> References: <57200BF94E69E54880C9BB1AF714BBCB5DE72E@w2003s01.double-l.local> <4A20D97B.1030609@freebsd.org> <20090530070306.GQ48776@hoeg.nl> <200905301224.40156.mel.flynn%2Bfbsd.current@mailing.thruhere.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Mel Flynn wrote: > On Saturday 30 May 2009 09:03:06 Ed Schouten wrote: >> * Tim Kientzle <kientzle@freebsd.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A21F067.6000202>