Summary: | sys-libs/tdb-1.2.9 fails on portage-multilib because of waflib module's python support | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Nathan Phillip Brink (binki) (RETIRED) <binki> |
Component: | [OLD] Library | Assignee: | Patrick Lauer <patrick> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | esigra, ewoud+gentoo, samba |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://code.google.com/p/waf/issues/detail?id=951 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 367291 | ||
Bug Blocks: | 306835, 379001, 379003 | ||
Attachments: |
tdb-1.2.9-build.log
emerge--info.txt talloc-2.0.5-waf-multilib.patch tdb-1.2.9.ebuild-waflib-python.patch |
Created attachment 278415 [details]
emerge--info.txt
Created attachment 278417 [details, diff]
talloc-2.0.5-waf-multilib.patch
Patch against the bundled waflib (exactly the same patch as fixes the same (yet unfiled) bug with talloc-2.0.5's waflib.
Created attachment 278419 [details, diff] tdb-1.2.9.ebuild-waflib-python.patch This patch requires bug #367291 to be fixed before it is valid, but it fixes this particular compilation issue on portage-multilib. Nice, but I would say more systematic solution in waf eclass would be better, some non fatal sed if it gets ever fixed upstream or so. On my system /usr/bin/python-config is also a bash script (I guess this is because of the new python-r1.eclass and distutils-r1.eclass) but tdb still compiles fine. Is this still a problem on portage-multilib? This is fixed in tdb-1.3.8 |
Created attachment 278413 [details] tdb-1.2.9-build.log many packages' waflibs don't support /usr/bin/python-config being written in non-python. On portage-multilib, python-config is written in POSIX shell as a wrapper trying to pass off execution to python-config-${ABI} as appropriate. See tdb-1.2.9-build.log.