[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-wget] python3
From: |
Ángel González |
Subject: |
Re: [Bug-wget] python3 |
Date: |
Thu, 18 Dec 2014 21:38:11 +0100 |
User-agent: |
Thunderbird |
On 18/12/14 09:16, Jérémie Courrèges-Anglas wrote:
wget-1.16.1 introduced a change wrt. python. Just upgrading the port
lead to the following failure:
checking whether /usr/local/bin/python3.4 version is>= 3.0... no
configure: error: Python interpreter is too old
*** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2725
'/usr/ports/pobj/wget-1.16.1/.configure_done': @for d in /usr/ports/pobj/wge...)
*** Error 1 in /usr/ports/net/wget
(/usr/ports/infrastructure/mk/bsd.port.mk:2473 'all')
This is because when python 3 support is requested in our ports
framework, the following values are set in the ./configure script
environment:
PYTHON="/usr/local/bin/python3.4"
ac_cv_prog_PYTHON="/usr/local/bin/python3.4"
ac_cv_path_PYTHON="/usr/local/bin/python3.4"
No. That's not your ports fault (well, unless you are naming python 2.7
"python3.4" ;) )
I "fixed" this by:
1. forcing PYTHON to the empty string, to avoid the error message
2. setting am_cv_pathless_PYTHON so that tests can still pass (after
installation of python3 of course)
http://cvsweb.openbsd.org/cgi-bin/cvsweb/ports/net/wget/Makefile.diff?r1=1.65&r2=1.66
I thought I'd let you know about this, even though I'm not sure if there
is a reasonable way to "solve" this issue. I feel that AM_PATH_PYTHON is
doing the right thing.
I don't know which check is used there by wget, but it's broken.
BTW, python3.4 could be added to _AM_PYTHON_INTERPRETER_LIST.
- [Bug-wget] python3, Jérémie Courrèges-Anglas, 2014/12/18
- Re: [Bug-wget] python3,
Ángel González <=