Created attachment 412370 [details] build.log There is no "config-3.3" directory. Only "config-3.3m". grep config-3.3 /var/tmp/portage/dev-lang/python-3.3.5-r2/temp/build.log Creating directory /usr/lib64/python3.3/config-3.3m /usr/lib/portage/python3.4/ebuild-helpers/xattr/install -c -m 644 Modules/config.c /var/tmp/portage/dev-lang/python-3.3.5-r2/image//usr/lib64/python3.3/config-3.3m/config.c /usr/lib/portage/python3.4/ebuild-helpers/xattr/install -c -m 644 Modules/python.o /var/tmp/portage/dev-lang/python-3.3.5-r2/image//usr/lib64/python3.3/config-3.3m/python.o /usr/lib/portage/python3.4/ebuild-helpers/xattr/install -c -m 644 /var/tmp/portage/dev-lang/python-3.3.5-r2/work/Python-3.3.5/Modules/config.c.in /var/tmp/portage/dev-lang/python-3.3.5-r2/image//usr/lib64/python3.3/config-3.3m/config.c.in /usr/lib/portage/python3.4/ebuild-helpers/xattr/install -c -m 644 Makefile /var/tmp/portage/dev-lang/python-3.3.5-r2/image//usr/lib64/python3.3/config-3.3m/Makefile /usr/lib/portage/python3.4/ebuild-helpers/xattr/install -c -m 644 Modules/Setup /var/tmp/portage/dev-lang/python-3.3.5-r2/image//usr/lib64/python3.3/config-3.3m/Setup /usr/lib/portage/python3.4/ebuild-helpers/xattr/install -c -m 644 Modules/Setup.local /var/tmp/portage/dev-lang/python-3.3.5-r2/image//usr/lib64/python3.3/config-3.3m/Setup.local /usr/lib/portage/python3.4/ebuild-helpers/xattr/install -c -m 644 Modules/Setup.config /var/tmp/portage/dev-lang/python-3.3.5-r2/image//usr/lib64/python3.3/config-3.3m/Setup.config /usr/lib/portage/python3.4/ebuild-helpers/xattr/install -c /var/tmp/portage/dev-lang/python-3.3.5-r2/work/Python-3.3.5/Modules/makesetup /var/tmp/portage/dev-lang/python-3.3.5-r2/image//usr/lib64/python3.3/config-3.3m/makesetup /usr/lib/portage/python3.4/ebuild-helpers/xattr/install -c /var/tmp/portage/dev-lang/python-3.3.5-r2/work/Python-3.3.5/install-sh /var/tmp/portage/dev-lang/python-3.3.5-r2/image//usr/lib64/python3.3/config-3.3m/install-sh Listing '/var/tmp/portage/dev-lang/python-3.3.5-r2/image//usr/lib64/python3.3/config-3.3m'... Listing '/var/tmp/portage/dev-lang/python-3.3.5-r2/image//usr/lib64/python3.3/config-3.3m'... sed: can't read /var/tmp/portage/dev-lang/python-3.3.5-r2/image//usr/lib64/python3.3/config-3.3/Makefile: No such file or directory ls -d /var/tmp/portage/dev-lang/python-3.3.5-r2/image/usr/lib64/python3.3/config-* /var/tmp/portage/dev-lang/python-3.3.5-r2/image/usr/lib64/python3.3/config-3.3m ls /var/tmp/portage/dev-lang/python-3.3.5-r2/image/usr/lib64/python3.3/config-3.3m/ Makefile Setup Setup.config Setup.local config.c config.c.in install-sh makesetup python.o
Same here, but it's not reproducible (which I found out about *after* another build overwrote the logs). I'm running a few more builds, hoping I'll hit it again so I can more easily debug it.
Ok, reproduced. The new python-3.3-libressl.patch patches both configure and configure.ac. In a failed build tree, configure has only the hunk from that patch applied, it hasn't been rebuilt by autoconf. We need it to be rebuilt by autoconf to pick up this call in the ebuild: # Disable ABI flags. sed -e "s/ABIFLAGS=\"\${ABIFLAGS}.*\"/:/" -i configure.ac || die "sed failed" What puzzles me is that configure.ac is actually newer than configure: % pwd /var/tmp/portage/dev-lang/python-3.3.5-r2-borked/work/Python-3.3.5 % test configure.ac -nt configure && echo newer newer and copying the entire tree (with -a to preserve timestamps) and running "autoconf" (without --force) correctly regenerates configure. That directory was created by mv-ing a failed tree, so the timestamps should be broken now if they were at build time. Normally I'd just say "add --force to the eautoconf call" but there might be something more subtle going on I haven't figured out yet. My build directory is on tmpfs, and the kernel is gentoo-sources-4.1.7, in case it matters. I'll go run a few more builds and see if I can work out what's special about the failing ones.
Ok, reproduced again, and now I'm seeing the stat output I was expecting to see: File: ‘configure.ac’ Size: 136604 Blocks: 272 IO Block: 4096 regular file Device: 22h/34d Inode: 787859 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 1000/ marienz) Gid: ( 1000/ marienz) Access: 2015-09-21 21:40:44.518852995 +1000 Modify: 2015-09-21 21:40:44.433852308 +1000 Change: 2015-09-21 21:40:44.433852308 +1000 Birth: - File: ‘configure’ Size: 442846 Blocks: 872 IO Block: 4096 regular file Device: 22h/34d Inode: 787858 Links: 1 Access: (0755/-rwxr-xr-x) Uid: ( 1000/ marienz) Gid: ( 1000/ marienz) Access: 2015-09-21 21:40:45.714862665 +1000 Modify: 2015-09-21 21:40:44.433852308 +1000 Change: 2015-09-21 21:40:44.433852308 +1000 Birth: - Note the mtimes match. So yeah, the fix is probably just to eautoconf --force.
I suggest to drop 'configure' part of python-3.3-libressl.patch.
(In reply to Marien Zwart from comment #1) Please assign the bug to the python team in the future instead of leaving it assigned to bug-wranglers.
And 'pyconfig.h.in' part probably also is not needed.
Should be fixed now.
