Summary: | dev-python/pygobject: incorrect dep on python (needs USE=threads) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jeremy Olexa (darkside) (RETIRED) <darkside> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | python, StormByte, tobias.pal |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://bugzilla.gnome.org/show_bug.cgi?id=640748 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Fix threads USE depency |
Description
Jeremy Olexa (darkside) (RETIRED)
2009-09-20 16:38:05 UTC
I vaguely recall pygobject having support for threadless python, it would need a recompile of pygobject though to match python... Can you try? (In reply to comment #1) > I vaguely recall pygobject having support for threadless python, it would need > a recompile of pygobject though to match python... Can you try? > I recompiled pygobject a couple times trying to figure out what was wrong. So, nope, it doesn't work. I just can confirm by using wicd-client. Same issue. Running revdep-rebuild does not detect this symbol missing though, and manually recompiling either. This is because I tried to use python with -threads. It worked well when I had python[+threads]. My symptoms: $ meld /usr/lib/libpyglib-2.0-python.so.0: undefined symbol: PyGILState_Release Meld requires pygtk 2.8.0 or higher. And after this command the error is gone and meld runs without problems: USE="threads" emerge -1 python:2.6 (In reply to comment #3) > I just can confirm by using wicd-client. Same issue. > Running revdep-rebuild does not detect this symbol missing though, and manually > recompiling either. > This is because I tried to use python with -threads. It worked well when I had > python[+threads]. I strongly doubt revdep-rebuild knows enough about dlopen targets to handle this one anyways... + 27 Jan 2011; Pacho Ramos <pacho@gentoo.org> pygobject-2.26.0-r1.ebuild: + dev-python/pygobject always needs python with threads support as reported by + Jeremy Olexa (bug #285722) and confirmed by me until upstream fixes its bug + #640748. + Just solved by upstream, and patch works fine Now, I need to know how to mimic: foo[bar=] EAPI2 behavior with python.eclass :-( http://devmanual.gentoo.org/ebuild-writing/eapi/index.html Could anybody from python team help me? Thanks (In reply to comment #7) > Now, I need to know how to mimic: > foo[bar=] EAPI2 behavior with python.eclass :-( The following syntax accidentally works: PYTHON_USE_WITH="threads=" (Some more complicated cases will be handled by PYTHON_DEPEND in EAPI >=4.) + 28 Jan 2011; Pacho Ramos <pacho@gentoo.org> pygobject-2.26.0-r1.ebuild, + +files/pygobject-2.26.0-disabled-threads.patch: + Fix building without threads and dependency on python (thanks a lot to + Arfrever Frehtes Taifersar Arahesis for his help). + (In reply to comment #9) revision 1.6 date: 2011-01-28 20:45:20 +0100; author: arfrever; state: Exp; lines: +2 -2; commitid: 28c44d431cd04567; Use +threads since dev-lang/python also has +threads. Created attachment 261077 [details, diff]
Fix threads USE depency
Remove "=" from PYTHON_USE_WITH.
-PYTHON_USE_WITH="threads="
+PYTHON_USE_WITH="threads"
Why? pygobject can work if both (python and pygobject) are compiled without threads support |