Sunpoet Hsieh wrote on 22.06.2012 05:20:
On Fri, Jun 22, 2012 at 4:45 AM, Marcus von Appen <m...@freebsd.org> wrote:
On, Thu Jun 21, 2012, Ruslan Mahmatkhanov wrote:
Marcus von Appen wrote on 21.06.2012 23:47:
Hi Ruslan,
On, Thu Jun 21, 2012, Ruslan Mahmatkhanov wrote:
Ok, revision 1.187 is the culprit. Reverting to 1.186 fixed things for me.
[...]
Does the latest one (1.188) work for you? I can't reproduce the issue
with my tinderboxes. How are the ports and dependencies configured on
yours?
Cheers
Marcus
No, it is not. I consequently revert 1.188 (with no success), then 1.187
(the same) and now it builds fine when I'm on 1.186.
All ports options are default. Tinderbox is i386. The only difference -
python32 is system-wide default:
nx7400> cat scripts/etc/env/build.9.0-FreeBSD-py3
USE_PYTHON=3.2
PYTHON_VERSION=python3.2
PYTHON_DEFAULT_VERSION=3.2
The issue is that USE_PYTHON=xx will introduce python as dependency for
_every_ port. Do not set it, since it is for usage in port Makefiles,
not for the environmental flags.
The reason for your problem is the circular dependency introduced by
that.
Cheers
Marcus
Hi,
In tinderbox env, I'm sure that PYTHON_DEFAULT_VERSION=python3.2 is
enough for specify the python port.
HTH
Regards,
Hi,
Yes, it's true. By the way, missing PYTHON_DEFAULT_VERSION was the
reason of py-distribute packaging break, that I asked you about a week ago.
--
Regards,
Ruslan
Tinderboxing kills... the drives.
_______________________________________________
freebsd-python@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
