mailutils with python USE enabled failing to build after python-2.7.11 update. Reproducible: Always Steps to Reproduce: 1. update to python-2.7.11 2. emerge =net-mail/mailutils-2.99.98 with python USE enabled 3. notice a failure 4. downgrade to =python-2.7.10-r3 5. notice a successful build of net-mail/mailutils Actual Results: Makefile:1200: recipe for target 'mime.lo' failed make[3]: *** [mime.lo] Error 1 In file included from libmu_py.h:47:0, from url.c:18: ../../include/mailutils/python.h:21:20: fatal error: Python.h: No such file or directory #include <Python.h> ^ compilation terminated. Makefile:1200: recipe for target 'url.lo' failed make[3]: *** [url.lo] Error 1 make[3]: Leaving directory '/var/tmp/portage/net-mail/mailutils-2.99.98/work/mailutils-2.99.98/python/libmu_py' Makefile:1131: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/var/tmp/portage/net-mail/mailutils-2.99.98/work/mailutils-2.99.98/python' Makefile:1253: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/var/tmp/portage/net-mail/mailutils-2.99.98/work/mailutils-2.99.98' Makefile:1126: recipe for target 'all' failed make: *** [all] Error 2 ^[[31;01m*^[[0m ERROR: net-mail/mailutils-2.99.98::gentoo failed (compile phase): ^[[31;01m*^[[0m emake failed ^[[31;01m*^[[0m ^[[31;01m*^[[0m If you need support, post the output of `emerge --info '=net-mail/mailutils-2.99.98::gentoo'`, ^[[31;01m*^[[0m the complete build log and the output of `emerge -pqv '=net-mail/mailutils-2.99.98::gentoo'`. ^[[31;01m*^[[0m The complete build log is located at '/var/tmp/portage/net-mail/mailutils-2.99.98/temp/build.log'. ^[[31;01m*^[[0m The ebuild environment file is located at '/var/tmp/portage/net-mail/mailutils-2.99.98/temp/environment'. ^[[31;01m*^[[0m Working directory: '/var/tmp/portage/net-mail/mailutils-2.99.98/work/mailutils-2.99.98' ^[[31;01m*^[[0m S: '/var/tmp/portage/net-mail/mailutils-2.99.98/work/mailutils-2.99.98'
Created attachment 418874 [details] build.log
> checking for python-config... /usr/bin/python-config > /usr/bin/python-config: line 6: /usr/bin/python-config-2.7: No such file or directory > /usr/bin/python-config: line 6: /usr/bin/python-config-2.7: No such file or directory Looks like we need to PDEPEND on the newest eselect-python in the latest dev-lang/python ebuilds.
It rather looks like an eclass use failure to me.
I have this bug too.
after updateing to stable dev-lang/python-2.7.12 i run into the same issue: libtool: compile: x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../.. -I../.. -I../../include -I../../include -DSYSCONFDIR=\"/etc\" -march=ivybridge -fomit-frame-pointer -O2 -pipe -fno-strict-aliasing -Wall -Wdeclaration-after-statement -c nls.c -fPIC -DPIC -o .libs/nls.o In file included from libmu_py.h:47:0, from mailbox.c:18: ../../include/mailutils/python.h:21:20: fatal error: Python.h: No such file or directory #include <Python.h> ^ compilation terminated. In file included from libmu_py.h:47:0, from envelope.c:18: ../../include/mailutils/python.h:21:20: fatal error: Python.h: No such file or directory #include <Python.h> ^ compilation terminated. Makefile:1260: recipe for target 'envelope.lo' failed make[3]: *** [envelope.lo] Error 1 make[3]: *** Waiting for unfinished jobs.... Makefile:1260: recipe for target 'mailbox.lo' failed make[3]: *** [mailbox.lo] Error 1
This should have been resolved by app-eselect/eselect-python-20140125-r1, which is a dependency of dev-lang/python-2.7.12. I cannot reproduce this failure in a stable amd64 environment. What does the following command output on your system? EPYTHON=python2.7 python-config --includes
(In reply to Mike Gilbert from comment #6) > This should have been resolved by app-eselect/eselect-python-20140125-r1, > which is a dependency of dev-lang/python-2.7.12. this is installed. > I cannot reproduce this failure in a stable amd64 environment. I have a (mostly) stable environment on two servers where the bug occurs. > What does the following command output on your system? > > EPYTHON=python2.7 python-config --includes # EPYTHON=python2.7 python-config --includes /usr/bin/python-config: line 6: /usr/bin/python-config-2.7: No such file or directory
Please try running either of the following commands to regenerate the /usr/bin/python-config wrapper script: eselect python set python2.7 or eselect python set python3.4
(In reply to Thomas Beutin from comment #7) > (In reply to Mike Gilbert from comment #6) [...] > > What does the following command output on your system? > > > > EPYTHON=python2.7 python-config --includes > > # EPYTHON=python2.7 python-config --includes > /usr/bin/python-config: line 6: /usr/bin/python-config-2.7: No such file or > directory after switching the default python version from 2.7 to 3.4 and back to 2.7 (first server) or simply (re)setting the default python version from 3.4 to 3.4 (second server) the result of this is on both machines: # EPYTHON=python2.7 python-config --includes -I/usr/include/python2.7 -I/usr/include/python2.7 and net-mail/mailutils-2.99.98[python] installs w/o any problem. But should i really have done this manually? IMHO it should be done by the ebuild. (i've to admit that i didn't read any after-update-message, but just used "python-updater -eall".)
(In reply to Mike Gilbert from comment #8) > Please try running either of the following commands to regenerate the > /usr/bin/python-config wrapper script: > > eselect python set python2.7 > > or > > eselect python set python3.4 i did it in the meantime (see comment 9), but there was a mid-air-collision here in bugzilla ;)
(In reply to Thomas Beutin from comment #9) > But should > i really have done this manually? IMHO it should be done by the ebuild. I agree. I just wanted to confirm that it resolved your problem first. https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f1ace35d4ae34b0788433037a4ef5bd4859b4d52