Re: llvm37 python3 problem

On 28/10/2015 5:27 AM, Brooks Davis wrote: > On Tue, Oct 27, 2015 at 11:03:07AM +, loic.b...@unix-experience.fr wrote: >> Any news for this problem ? > > Upstream does not yet support python 3 so it remain broken. I've not > yet had time to see if I can force the use of 2.7 when building.

Re: llvm37 python3 problem

Any news for this problem ? 12 octobre 2015 19:50 "Brooks Davis" a écrit: > On Fri, Oct 09, 2015 at 04:38:57PM +0200, Walter Schwarzenfeld wrote: > >> Can't test the patch in the above link, cause the port ignores python >> 3.4 and I don't want deinstall python 2.7. > >

Re: llvm37 python3 problem

On Tue, Oct 27, 2015 at 11:03:07AM +, loic.b...@unix-experience.fr wrote: > Any news for this problem ? Upstream does not yet support python 3 so it remain broken. I've not yet had time to see if I can force the use of 2.7 when building. Simple changes haven't worked. You can work around

Re: llvm37 python3 problem

On Fri, Oct 09, 2015 at 04:38:57PM +0200, Walter Schwarzenfeld wrote: > Can't test the patch in the above link, cause the port ignores python > 3.4 and I don't want deinstall python 2.7. I've figured out how to reconfigure poudriere to be able to test this. Several other files need this sort of

Re: llvm37 python3 problem

The patch you mention seems good yes, i think we should wait for LLVM 3.7.1 or maybe add this patch manually. What is the maintainer advice ? -- Best regards, Loïc BLOT, UNIX systems, security and network engineer http://www.unix-experience.fr Le vendredi 09 octobre 2015 à 15:56 +0200,

Re: llvm37 python3 problem

Hi Shane, Thanks for the information. The problem is that the Clang/LLVM 3.6 works perfect with PYTHON_VERSION=3.4, but not clang/llvm 3.7, for an update it looks like a regression, and i want to make python3.4 as a default version for my whole port tree. Else maybe it could be good to force

Re: llvm37 python3 problem

Can't test the patch in the above link, cause the port ignores python 3.4 and I don't want deinstall python 2.7. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to

Re: llvm37 python3 problem

Found this: http://freshbsd.org/commit/llvm/r249467?diff=lldb%2Ftrunk%2Fscripts%2FfinishSwigWrapperClasses.py ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to

llvm37 python3 problem

Hello @ports i recently created an issue because everybody wants to use LLVM/Clang 3.7 on FreeBSD with Python3(.4) as a default could not build it due to some python2 scripts not converted. Here is the issue: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203618 Can someone look at this issue

Re: llvm37 python3 problem

Hallo !! Look at /usr/ports/Mk/bsd.default-versions.mk. There you have: PYTHON_DEFAULT?=2.7 PYTHON2_DEFAULT?= 2.7 PYTHON3_DEFAULT?= 3.4 with this it compiles fine. ___ freebsd-ports@freebsd.org mailing list

Re: llvm37 python3 problem

I use Python 3.4 as a global default for the whole system, i need to switch from 2.7 to 3.4 in my whole ports tree :). LLVM python3.4 migration should not be difficult, some 2to3 should be added in the building process but i didn't know where 8 octobre 2015 12:15 "Walter Schwarzenfeld"

Re: llvm37 python3 problem

I think this should work: in /etc/make.conf: either DEFAULT_VERSIONS=python=2.7 python2=2.7 python3=3.4 or .if ${.CURDIR:M*/ports/devel/llvm*} USE_PYTHON=2.7 .endif should work. ___ freebsd-ports@freebsd.org mailing list

Re: llvm37 python3 problem

On 09/10/2015 02:33, Walter Schwarzenfeld wrote: I think this should work: in /etc/make.conf: either DEFAULT_VERSIONS=python=2.7 python2=2.7 python3=3.4 or .if ${.CURDIR:M*/ports/devel/llvm*} USE_PYTHON=2.7 .endif should work. We know it works with the old python2.7. The point is that it