John W. O'Brien j...@saltant.com:
On 12/1/14 4:01 AM, Marcus von Appen wrote:
Zitat von Andrew Berg aberg...@my.hennepintech.edu:
On 2014.11.30 08:23, John W. O'Brien wrote:
On 11/29/14 11:40 PM, Andrew Berg wrote:
On 2014.11.29 22:00, John W. O'Brien wrote:
Let's say that I want to
Zitat von Andrew Berg aberg...@my.hennepintech.edu:
On 2014.11.30 08:23, John W. O'Brien wrote:
On 11/29/14 11:40 PM, Andrew Berg wrote:
On 2014.11.29 22:00, John W. O'Brien wrote:
Let's say that I want to build net/py-pyzmq with
PYTHON_VERSION=python3.4.
Why this instead of using
On 12/1/14 4:01 AM, Marcus von Appen wrote:
Zitat von Andrew Berg aberg...@my.hennepintech.edu:
On 2014.11.30 08:23, John W. O'Brien wrote:
On 11/29/14 11:40 PM, Andrew Berg wrote:
On 2014.11.29 22:00, John W. O'Brien wrote:
Let's say that I want to build net/py-pyzmq with
On 11/29/14 11:40 PM, Andrew Berg wrote:
On 2014.11.29 22:00, John W. O'Brien wrote:
Let's say that I want to build net/py-pyzmq with
PYTHON_VERSION=python3.4.
Why this instead of using DEFAULT_VERSIONS?
I was following this advice:
On 2014.11.30 08:23, John W. O'Brien wrote:
On 11/29/14 11:40 PM, Andrew Berg wrote:
On 2014.11.29 22:00, John W. O'Brien wrote:
Let's say that I want to build net/py-pyzmq with
PYTHON_VERSION=python3.4.
Why this instead of using DEFAULT_VERSIONS?
I was following this advice:
Hello FreeBSD-Python (and mva),
I think there is a bug, either in Mk/Uses/python.mk or in
lang/python{2,3}, or perhaps both, and I would appreciate some review of
my analysis that follows to validate or correct it. I'm sorry if I'm
stumbling along well-trod ground here.
Let's say that I want to
On 2014.11.29 22:00, John W. O'Brien wrote:
Let's say that I want to build net/py-pyzmq with
PYTHON_VERSION=python3.4.
Why this instead of using DEFAULT_VERSIONS?
It looks like the right thing to do, short of
patching openpgm's build scripts to be py3k-friendly, is to update
