Summary: | app-pda/libplist-1.11: Could not link test program to Python | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Craig Andrews <candrews> |
Component: | Current packages | Assignee: | Gentoo PDA project <pda> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | candrews, luisav.ferreira, mail, nikarul, raistlin, randy-andy-, rose, toralf, zeekec |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 567924 | ||
Attachments: |
build.log
config.log |
Description
Craig Andrews
2015-12-02 20:01:04 UTC
Created attachment 418396 [details]
build.log
/var/tmp/portage/app-pda/libplist-1.11/temp/build.log
Created attachment 418398 [details]
config.log
/var/tmp/portage/app-pda/libplist-1.11/work/libplist-1.11-python3_4/config.log
same here at the tinderbox image amd64-plasma-unstable_20151204-112628 I've committed 1.11-r1 with some Python fixes, and disabled Python 3 support. Someone should really report this upstream, cause it uses outdated (2006) ac_python_devel.m4 that breaks with upstream Python 3 install. Now libplist-1.11-r2 fails to configure the same error. Is there not any patch, which we can use? (In reply to Juergen Rose from comment #5) > Now libplist-1.11-r2 fails to configure the same error. Is there not any > patch, which we can use? Just disable python3* targets for libplist in package.use: app-pda/libplist python_targets_python2_7 -python_targets_python3_3 -python_targets_python3_4 -python_targets_python3_5 (In reply to Denis Sokolovsky from comment #6) > (In reply to Juergen Rose from comment #5) > > Now libplist-1.11-r2 fails to configure the same error. Is there not any > > patch, which we can use? > > Just disable python3* targets for libplist in package.use: > app-pda/libplist python_targets_python2_7 -python_targets_python3_3 > -python_targets_python3_4 -python_targets_python3_5 Thanks Denis, worked. *** Bug 570106 has been marked as a duplicate of this bug. *** *** Bug 569050 has been marked as a duplicate of this bug. *** The disable-python-target workaround is not really a workaround if people are actually using libimobiledevice as python3 is required by other packages that depend on the whole stack (eg, gnome-gvfs). The problem is "simple" but the solution isn't quite as straightforward, as the current the autoconf m4 macro (ac_python_devel) gets one thing right and one thing wrong: checking for Python include path... -I/usr/include/python3.4m <= right checking for Python library path... -L/usr/lib64/python3.4 -lpython3.4 <= wrong If someone has a clean way of changing the latter lib argument to -lpython3.4m it builds/links fine. I looked at it yesterday, but I didn't find a good eclass fix or sed hack (but I will say the current ebuild could be cleaner, as it seems to run configure several more times than it needs to...) Maybe an eclass enhancement to stave off future bugs? Slight variation on something i tried yesterday pointed out in the Arch build setup works here, pushed the fix into last 2 versions (1.11-r2 and 1.12). Give it a shot... ydep, fixed After that change, we get this: /tmp/portage/app-pda/libplist-1.12/work/libplist-1.12/configure: line 17140: AX_PYTHON_DEVEL: command not found commit 0f0051b915b593a44b9150be6d1744a7ea1215d0 Author: Mike Gilbert <floppym@gentoo.org> Date: Sun Jan 24 21:14:31 2016 -0500 app-pda/libplist: Override PYTHON_LDFLAGS in src_configure Works around broken build system. Bug: https://bugs.gentoo.org/567370 Package-Manager: portage-2.2.27_p49 app-pda/libplist/libplist-1.11-r2.ebuild | 13 ++++++------- app-pda/libplist/libplist-1.12.ebuild | 13 ++++++------- 2 files changed, 12 insertions(+), 14 deletions(-) Shouldn't 1.11-r2 be stabilized for amd64? because at the moment this is broken for anybody on stable amd64 after the last changes in the tree. *** Bug 601970 has been marked as a duplicate of this bug. *** |