Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 10 Aug 2023 12:13:52 +0200
From:      Matthias Apitz <guru@unixarea.de>
To:        Alastair Hogge <agh@riseup.net>
Cc:        Moin Rahman <bofh@freebsd.org>, freebsd-current@freebsd.org
Subject:   Re: port lang/python27 does not build in 14.0-CURRENT w/ poudriere
Message-ID:  <ZNS4YH3weKU7By0J@pureos>
In-Reply-To: <87c58b62df16bd5cc31952d814bbe995@riseup.net>
References:  <ZNN4vNTtQGb5Jm8v@pureos> <DB31B93E-01AE-4AF6-BDA6-1F6F980B1C5A@freebsd.org> <A7BC4F5A-9061-46A8-9659-102626EA6241@freebsd.org> <ZNOdqiNvAFfMh9a9@pureos> <414B922C-C553-41D4-B519-E3B3B239B606@freebsd.org> <ZNO4WYPzZ7B5ne5v@pureos> <9A29A1BA-F957-40D9-96C6-062471BA14AF@freebsd.org> <ZNSv%2BwEyLXD0JuK2@pureos> <87c58b62df16bd5cc31952d814bbe995@riseup.net>

next in thread | previous in thread | raw e-mail | index | archive | help
El día jueves, agosto 10, 2023 a las 09:50:31 +0000, Alastair Hogge escribió:

> On 2023-08-10 17:38, Matthias Apitz wrote:
> > El día Wednesday, August 09, 2023 a las 06:04:16PM +0200, Moin Rahman escribió:
> > 
> >> This perfectly builds on the latest HEAD without any problem as shared in my build log. I am not sure what is wrong at your end. Neither can I see any fallout on the clusters.
> >> 
> > 
> > I've cc'ed freebsd-current@
> > 
> > I did two times the building of lang/python27 within poudriere on
> > 14.0-CURRENT:
> > 
> > =>> Building lang/python27
> > build started at Tue Aug  8 04:05:20 CEST 2023
> > port directory: /usr/ports/lang/python27=>> Building lang/python27
> > 
> > =>> Building lang/python27
> > build started at Thu Aug 10 06:33:53 CEST 2023
> > port directory: /usr/ports/lang/python27
> > 
> > The first failed, the one of today went fine. The main difference in the
> > building log is:
> > 
> > failing job:
> > --MAKE_ENV--
> > OPENSSLBASE=/usr/local OPENSSLDIR=/usr/local/openssl OPENSSLINC=/usr/local/include OPENSSLLIB=/usr/local/lib OPENSSLRPATH=/usr/local/lib
> > 
> > fine job:
> > --MAKE_ENV--
> > OPENSSLBASE=/usr OPENSSLDIR=/etc/ssl OPENSSLINC=/usr/include OPENSSLLIB=/usr/lib
> > ...
> > 
> > I didn't changed anything in the poudriere config or port's options. The
> > only thing I did between was yesterday evening a 'git pull' in
> > /usr/ports.
> > 
> > What could have triggered this change of the used SSL version?
> 
> Do you have the error from the failed build? I have the following patch
> in my tree to get Python-2.7 to build, tho I have not tested recently if
> it is still required:

The log of the failing job is here:

http://www.unixarea.de/python27-2.7.18_2.log

It has exactly the issue which your patch addresses: with OpenSSL from
ports it can't build the shared object _hashlib.so.

I can live with this for now (as the package was built now). But I
wanted to understand, why and what was the change between August 8 and
10.

	matthias

-- 
Matthias Apitz, ✉ guru@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZNS4YH3weKU7By0J>