Exim fails due to race conditions in the makefile that creates links for the build when making with '-j' option enabled. The ebuild should probably strip out any -j flags from MAKEFLAGS before running. Reproducible: Always Steps to Reproduce: 1. Set MAKEFLAGS to '-j 3' 2. emerge exim Actual Results: !!! ERROR: mail-mta/exim-4.43-r2 failed. !!! Function src_compile, Line 184, Exitcode 2 !!! make failed !!! If you need support, post the topmost build error, NOT this status message. >>> Unpacking source... >>> Unpacking exim-4.43.tar.bz2 to /var/tmp/portage/exim-4.43-r2/work * Applying exim-4.14-tail.patch ... [ ok ] * Applying exim-4.43-r2-host_aton-buff.patch ... [ ok ] * Applying exim-4.43-r2-localscan_dlopen.patch ... [ ok ] * Applying exim-4.30-conf.patch ... [ ok ] >>> Source unpacked. /bin/sh: line 1: cd: build-exim-gentoo: No such file or directory make[1]: Entering directory `/var/tmp/portage/exim-4.43-r2/work/exim-4.43' >>> Creating links to source files... mkdir: cannot create directory `build-exim-gentoo': File exists *** It appears that ../scripts/MakeLinks was previously interrupted. *** You need to remove the build directory, and then run 'make' again. make[1]: *** [build-directory] Error 1 make[1]: Leaving directory `/var/tmp/portage/exim-4.43-r2/work/exim-4.43' make: *** [go] Error 2 make: *** Waiting for unfinished jobs.... !!! ERROR: mail-mta/exim-4.43-r2 failed. !!! Function src_compile, Line 184, Exitcode 2 !!! make failed !!! If you need support, post the topmost build error, NOT this status message. Expected Results: Normal ebuild process.
this doesn't look like it's a make issue, I regularly build with MAKEOPTS="-j12" during testing. would you mind making sure /var/tmp/portage/exim-4.43-r2 doesn't exist before trying the build. The output of `emerge info` would also come in handy. Cheers, Colin
Yes, I've checked that /var/tmp/portage/ is empty before running it. The bug does leave its build area untidy, which causes a diferent error when re-emerging. (Complains about lots of files being already present when trying to link them) Portage 2.0.51.19 (default-linux/x86/2005.0, gcc-3.3.5, glibc-2.3.4.20040808-r1, 2.6.10-gentoo-r6 i686) ================================================================= System uname: 2.6.10-gentoo-r6 i686 AMD Duron(tm) Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.4-r1 [2.3.4 (#1, Feb 24 2005, 02:43:16)] dev-lang/python: 2.3.4-r1 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.5, 1.4_p6, 1.8.5-r3, 1.9.4, 1.6.3, 1.7.9-r1 sys-devel/binutils: 2.15.92.0.2-r1 sys-devel/libtool: 1.5.10-r4 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=athlon-xp -O3 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon-xp -O3 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms" GENTOO_MIRRORS="http://ftp.easynet.nl/mirror/gentoo/ ftp://ftp.easynet.nl/mirror/gentoo/ ftp://linux.rz.ruhr-uni-bochum.de/gentoo-mirror/ http://gentoo.inode.at/ http://www.gigaload.org/gentoo.org/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 clearpasswd nptl nptlonly userlocales" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, PORTDIR_OVERLAY
I can't reproduce it here, could you check a couple of other stable releases of exim, and with other numbers of MAKEOPTS (-j2,-j4,j12 etc). but first, could you do `emerge --debug exim` for me. Cheers.
just to verify, are you setting MAKEFLAGS or MAKEOPTS? and where abouts are you setting it?
Created attachment 53032 [details] emerge --debug exim
D'oh. Typo in make.conf apears to have been causing this. Closed.
*** Bug 161616 has been marked as a duplicate of this bug. ***
