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. Simple > changes haven't worked. You can work around this by disabling the LLDB > option when building. > > -- Brooks > >> 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. >>> >>> I've figured out how to reconfigure poudriere to be able to test this. >>> Several other files need this sort of fix. I've managed to fix some >>> with patches from upstream, but it appears that lldb is incompatible >>> with python 3. The C code is using obsolete interfaces and doesn't >>> compile. >>> >>> -- Brooks >> Can a conditional BROKEN= block be added as a temporary measure? if PYTHON_REL > && PORTOPTIONS:MLLDB ? ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
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 this by disabling the LLDB option when building. -- Brooks > 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. > > > > I've figured out how to reconfigure poudriere to be able to test this. > > Several other files need this sort of fix. I've managed to fix some > > with patches from upstream, but it appears that lldb is incompatible > > with python 3. The C code is using obsolete interfaces and doesn't > > compile. > > > > -- Brooks > signature.asc Description: PGP signature
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. > > I've figured out how to reconfigure poudriere to be able to test this. > Several other files need this sort of fix. I've managed to fix some > with patches from upstream, but it appears that lldb is incompatible > with python 3. The C code is using obsolete interfaces and doesn't > compile. > > -- Brooks ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
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 fix. I've managed to fix some with patches from upstream, but it appears that lldb is incompatible with python 3. The C code is using obsolete interfaces and doesn't compile. -- Brooks signature.asc Description: PGP signature
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, Walter Schwarzenfeld a écrit : > Found this: > > http://freshbsd.org/commit/llvm/r249467?diff=lldb%2Ftrunk%2Fscripts%2 > FfinishSwigWrapperClasses.py > > ___ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.o > rg" ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
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 "freebsd-ports-unsubscr...@freebsd.org"
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 "freebsd-ports-unsubscr...@freebsd.org"
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 python2 in LLVM3.7 port
Thanks !
9 octobre 2015 07:45 "Shane Ambler" a écrit:
> 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 fails if
> you only want to use something recent like python3.4
>
> python 2.7 was released 5 years ago. Even python3.4 was release over a
> years and a half ago. If I had trouble with FreeBSD 7.3 you would tell
> me to upgrade, so why do we have to keep using such an old version of
> python? Not everyone wants to keep using old software.
>
> The point of original the email was to get llvm/clang 3.7 working on a
> machine that has python 3.4 installed as default and not 2.7
>
> Which leads to wanting to place in make.conf -
> DEFAULT_VERSIONS=python=3.4 python2=2.7 python3=3.4
>
> And Loic - just so you know, while python 2.7 was going to be supported
> until 2015, it was extended again for yet another 5 years - see
>
> http://legacy.python.org/dev/peps/pep-0373
>
> -- FreeBSD - the place to B...Software Developing
>
> Shane Ambler
>
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
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 fails if
you only want to use something recent like python3.4
python 2.7 was released 5 years ago. Even python3.4 was release over a
years and a half ago. If I had trouble with FreeBSD 7.3 you would tell
me to upgrade, so why do we have to keep using such an old version of
python? Not everyone wants to keep using old software.
The point of original the email was to get llvm/clang 3.7 working on a
machine that has python 3.4 installed as default and not 2.7
Which leads to wanting to place in make.conf -
DEFAULT_VERSIONS=python=3.4 python2=2.7 python3=3.4
And Loic - just so you know, while python 2.7 was going to be supported
until 2015, it was extended again for yet another 5 years - see
http://legacy.python.org/dev/peps/pep-0373/
--
FreeBSD - the place to B...Software Developing
Shane Ambler
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
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
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
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" a écrit: > 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 > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
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 https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
