Bug 208387

Summary:	graphics/libGL: r411841 pulls LLVM 3.7 (instead of 3.6) which is marked as broken with Python 3
Product:	Ports & Packages	Reporter:	Sylvain Garrigues <sylvain>
Component:	Individual Port(s)	Assignee:	freebsd-x11 (Nobody) <x11>
Status:	Closed Overcome By Events
Severity:	Affects Only Me	CC:	brooks, emaste, rezny, w.schwarzenfeld, zeising
Priority:	---	Flags:	rezny: maintainer-feedback+
Version:	Latest
Hardware:	Any
OS:	Any

Description Sylvain Garrigues 2016-03-29 20:52:54 UTC

devel/llvm37 is marked as broken: "LLDB does not build with Python 3"

So now I cannot use both Python 3 and all the programs which depend on libGL.

Can we revert back to llvm36 until llvm37 becomes compatible with Python 3?

Comment 1 Ed Maste freebsd_committer

2016-03-30 13:52:39 UTC

llvm37 won't be compatible with Python 3, but I think it should be possible to make it explicitly use Python 2 when 3 is set as the default.

Note that lldb upstream has been updated to work with Python 2 and 3, and future llvm packages should be able to drop the BROKEN= setting.

Comment 2 Jan Beich freebsd_committer

2017-04-10 20:38:22 UTC

Can you still reproduce (up to bug 218551)? 2017Q2 as of ports r433862 uses LLVM 3.9 while /head (future 2017Q3) as of ports r438198 uses LLVM 4.0.

devel/llvm37 is gone since ports r437427. devel/llvm36 will follow after divorcing from USES=compiler. Mesa 17.1 upstream will require LLVM 3.9 or later but downstream maintainer adjusted deps in advance to reduce QA cost.

(In reply to Ed Maste from comment #1)
> Note that lldb upstream has been updated to work with Python 2 and
> 3, and future llvm packages should be able to drop the BROKEN=
> setting.

Looking at devel/llvm*/Makefile I suspect that future never came or the maintainer didn't notice.

Comment 3 Ed Maste freebsd_committer

2017-04-10 20:51:57 UTC

> Looking at devel/llvm*/Makefile I suspect that future never came or the
> maintainer didn't notice.

Hrm. I haven't tried it myself, and when I search now I see reports it still fails with Python 3 on *nix, although LLDB is using Python 3 on Windows as far as I can tell.

Comment 4 Matthew Rezny freebsd_committer

2017-04-26 11:20:28 UTC

llvm37 is no more and libGL now depends on llvm39/40. Reverting to llvm36 is a non-solution. The "new" conflict with Python3 in llvm37 only pertains to LLDB, which was previously a separate port. You may still build llvm40, which also includes Clang, without the LLDB option in order to use both Python 3 and things that depend on libGL together.

Comment 5 Niclas Zeising freebsd_committer

2017-12-16 20:44:42 UTC

Hi!
Is this still an issue?

Comment 6 Walter Schwarzenfeld 2018-02-01 14:25:31 UTC

 It is shurely overcome by events and so I close here.