Re: build broken due to openssl?

[Rafal Boni <rafal%pobox.com@localhost>]

On Thu, May 15, 2008 at 02:35:05PM +0100, Patrick Welche wrote:
> On Wed, May 14, 2008 at 07:33:56PM +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.
> > 
> > I saw that yesterday on a native i386 build but not with this afternoon's 
> > cvs..
> 
> I see it now though :-/

I still saw this yesterday/the day before after not having updated my
-current tree on sparc64 for a while.  The usual medicine of removing
the pre-bump OpenSSL libs (esp. libcrypto.so.3 it seems) helped me to
get over it, but I bet the problem is still there for anyone that has
a $DESTDIR from before the bumps and does a build of post-bump sources
w/out cleaning out the $DESTDIR.  Why the libs in the $DESTDIR are 
picked up first is the mystery.

At the very least we should note it in UPDATING that you might lose on
the first (any?) post-bump build if you have old OpenSSL libs in your 
$DESTDIR.

--rafal

-- 
  Time is an illusion; lunchtime, doubly so.     |/\/\|           Rafal Boni
                   -- Ford Prefect               |\/\/|      
rafal%pobox.com@localhost