After dev-lang/python-2.7 package was compiled with clang, compilation of app-emulation/xen-tools with gcc failed in configuration phase with msg: configure: error: Unable to find Python development headers configure: error: ./configure failed for tools Reproducible: Always Steps to Reproduce: 1. compile dev-lang/python-2.7 with clang 2. compile app-emulation/xen-tools with gcc Actual Results: configure within .../portage/app-emulation/xen-tools-4.7.0-r2/work/xen-4.7.0/tools directory failed with: checking for PyArg_ParseTuple in -lpython... no configure: error: Unable to find a suitable python development library Expected Results: xen-tools compiled without problem default compiler: gcc .../env/compiler-clang.conf:CC="clang" .../package.env/use-clang:dev-lang/python compiler-clang.conf Solution: Comment python-2.7.10-cross-compile-warn-test.patch in ebuild!
Created attachment 449782 [details, diff] GCC is failing with -OPT:Olimit=0 argument, clang just ignore it Actually I needed just another patch for python-2.7. More in https://forums.gentoo.org/viewtopic-t-984804-start-0.html It's looking like different manifestation of the same cause. Clang just ignore '-OPT:Olimit=0' argument, so if python is compiled with clang everything is OK. But this argument is then used when xen-tools package is compiled and if gcc is used, then error is throwned out because gcc is not ignoring '-OPT:Olimit=0'! :-(
well, if you are using xen, please stick to gcc I don't think Xen upstream support clang (even build python with clang).
Guys, A similar issue has been reported to us: https://github.com/pentoo/pentoo-overlay/issues/222 FYI, to highlight the fact that other packages might be affected. It might be an upstream python bug but users need a workaround (like a freebsd? https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=182952)
Well, it's actually quite a curious bug. Normally, clang reports this as an erroneous option: $ clang-8 -OPT:Olimit=0 -x c -; echo $? error: invalid integral value 'PT:Olimit=0' in '-OPT:Olimit=0' error: invalid integral value 'PT:Olimit=0' in '-OPT:Olimit=0' 1 However, if you pass -O2 following it, it ignores the previous value. However, that is not the only bug in question here. The more important issue is xen-tools configure script taking 'python-config --cflags' which is plain wrong. It should be using 'python-config --includes' instead.
FWICS upstream removed the use of this flag in py3.2a4, so nothing to report upstream. I'll patch it out in our Python ebuild. I'll leave the bug open for xen-tools maintainers to replace wrong use of 'python-config --cflags'.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e1d806dae10cf0fb34aa2778eabed2869b8eece8 commit e1d806dae10cf0fb34aa2778eabed2869b8eece8 Author: Michał Górny <mgorny@gentoo.org> AuthorDate: 2019-05-09 13:29:10 +0000 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: 2019-05-10 14:35:55 +0000 dev-lang/python: Force-off -OPT:Olimit=0 in 2.7 to unbreak clang+gcc Bug: https://bugs.gentoo.org/596798 Signed-off-by: Michał Górny <mgorny@gentoo.org> dev-lang/python/python-2.7.16.ebuild | 5 +++++ 1 file changed, 5 insertions(+)
I believe this is long-fixed because we changed to *FLAGS_NODIST.
