Summary: | x11-proto/xcb-proto: enable multiple python support | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Maxim Koltsov (RETIRED) <maksbotan> |
Component: | [OLD] Library | Assignee: | Gentoo X packagers <x11> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | Adrian.Bassett, fuzzyray, python |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 470902 | ||
Attachments: |
xcb-proto-1.8-r2.ebuild
eclass-debug.log |
Description
Maxim Koltsov (RETIRED)
2013-05-21 18:50:27 UTC
Created attachment 348844 [details]
xcb-proto-1.8-r2.ebuild
Commited per radhermit and lu_zero permission on IRC. FYI, this ebuild is broken on a MacOS prefix environment not sure if it would possibly impact other architectures. Basically the xorg-2_src_configure call is creating 'xcb-proto-1.8-default' instead of 'xcb-proto-1.8-x64-macos', so top_builddir="${WORKDIR}/${P}-${ARCH}" does not exist in the src_compile phase. I haven't found where exactly in the eclass hierarchy that this gets set, but it appears to be in the multibuild eclass. (In reply to comment #3) > FYI, this ebuild is broken on a MacOS prefix environment not sure if it > would possibly impact other architectures. > > Basically the xorg-2_src_configure call is creating 'xcb-proto-1.8-default' > instead of 'xcb-proto-1.8-x64-macos', so > top_builddir="${WORKDIR}/${P}-${ARCH}" does not exist in the src_compile > phase. > > I haven't found where exactly in the eclass hierarchy that this gets set, > but it appears to be in the multibuild eclass. Could you attach the eclass-debug.log? It could be either returned by get_all_abis or $DEFAULT_ABI fallback. The issue is likely common to all non-multilib arches. Created attachment 348993 [details]
eclass-debug.log
The eclass-debug log is attached. I'll be opening a separate bug for the issue shortly, so this is the last thing I will be putting on this bug.
Putting back to resolved / fixed since I opened bug 471079 for the issue. |