On Fri, May 16, 2008 at 04:02:27PM +0100, Patrick Welche wrote:
| On Wed, May 14, 2008 at 02:18:43PM -0400, Greg Troxel wrote:
| > I am failing to build current (on macos 10.5), and the problem is that
| > various programs fail due to warnings about libcrypto including patented
| > algorithms.
|
| >
/usr/obj/gdt-current/tools/lib/gcc/i386--netbsdelf/4.1.3/../../../../i386--netbsdelf/bin/ld:
warning: libcrypto.so.3, needed by
/usr/obj/gdt-current/destdir/i386/usr/lib/libkrb5.so, may conflict with
libcrypto.so.4
|
| Odd: there is a .WAIT between libcrypto and libssl, libssl/Makefile
correctly
| has
|
| LIBDPLIBS+=crypto ${.CURDIR}/../libcrypto
|
| yet after the libraries are installed, libssl->libcrypto.so.3, and
| libcrypto.so.4 is installed, so the question is how libssl ends up
| being linked to libcrypto.so.3 even though libcrypto.so.4 should
| (according to the .WAIT) already exist in libcrypto/objdir? (Looks
| like libssl gets linked to the installed libcrypto rather than
| the one in ../libcrypto/objdir - LIBDPLIBS ignored?)
|
| Naturally, the second build.sh run works...
Try a clean build, rather than an update build.
I found that fixed various build problems I was having
after the recent OpenSSL upgrade.
Attachment:
pgpx0Nhg8TsbM.pgp
Description: PGP signature