Bug 34053 – Using ebuild ... install forces a new configure and make run

• Product: Portage Development
• Status: RESOLVED INVALID

[Description Svein Erik Brostigen 2003-11-21 12:42:17 UTC]

Sometimes an ebuild may be flawed or the source will not build without errors.
After fixing the errors and finishing the make session successfully, the build
needs to be installed.

When running 'ebuild .... install qmerge' manually often results in a new round
with configure and make, reintroducing the problem fixed manually.

This is not the case with all ebuilds, but I have not been able to track down
exactly what causes it.

I saw the problem yesterday when I emerged 'bochs'. The emerge failed and I had
to run the configure line in the ebuild with some options removed followed by a
manual make. bochs was built without a problem, but when I ran ebuild ...
install, it re-ran configure and make and it failed again. My solution was to
edit and change the configure line in the ebuild file.

I would imagine that this is not expected behaviour (re-running configure and
make) since it does not happen in every ebuild.


Reproducible: Always
Steps to Reproduce:
1. emerge bochs 
2. Somewhere along the process, terminate it
3. Run the make manually until everything has been built
4. Run : ebuild /usr/portage/app-emualtion/bochs/bochs-2.0.2.ebuild install
5. Watch how configure and make is re-run even though it is not necssary

Actual Results:  
The errors corrected by a manual make gets reintroduce before ebuild tries to
install it.

Expected Results:  
Skipped the configure and make phase since it has already been done and gone on
to actually install the ebuild.

Portage 2.0.49-r15 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r1,2.3.2-r9,
2.6.0-test9-mm4)
=================================================================
System uname: 2.6.0-test9-mm4 i686 Intel(R) Pentium(R) 4 CPU 2.40GHz
Gentoo Base System version 1.4.3.12
distcc 2.11.2 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled]
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CFLAGS="-march=pentium4 -O3 -pipe -fomit-frame-pointer -funroll-loops -mno-sse2
-mfpmath=sse -mmmx -msse"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config
/usr/kde/3/share/config /usr/X11R6/lib/X11/xkb /usr/kde/cvs/share/config
/usr/kde/3.1/share/config /usr/share/texmf/tex/generic/config/
/usr/share/texmf/tex/platex/config/ /usr/share/texmf/dvips/config/
/usr/share/texmf/dvipdfm/config/ /usr/share/texmf/xdvi/ /opt/glftpd/etc
/usr/share/config"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
CXXFLAGS="-march=pentium4 -O3 -pipe -fomit-frame-pointer -funroll-loops
-mno-sse2 -mfpmath=sse -mmmx -msse"
DISTDIR="/usr/portage/distfiles"
FEATURES="ccache autoaddcvs sandbox notitles"
GENTOO_MIRRORS="ftp://gentoo.mirrors.pair.com/ http://www.ibiblio.org/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="x86 oss avi crypt cups encode foomaticdb gif jpeg libg++ mad mikmod mpeg
ncurses nls pdflib png quicktime spell truetype xml2 xmms zlib directfb alsa
gdbm berkdb slang readline arts tetex nas svga tcltk java guile X sdl gpm tcpd
libwww ssl perl python esd imlib oggvorbis gnome gtk qt kde motif opengl gphoto2
ldap cdr scanner acpi artswrappersuid dga fbcon ggi gstreamer gtk2 gtkhtml icc
icc-pgo xv composite innodb mbox mozilla nptl oci8 odbc sse tiff xvid -apm
-mysql -pam"

[Comment 1 Svein Erik Brostigen 2003-11-21 13:26:02 UTC]

Same thing happens with krusader.

The ebuiold fails on some docbook issues. Not a proble, I just edited the Makefile and removed 'doc' from the SUBDIR line and built it without errors. When doing ebuild ... install, it rerun configure and amke and resulting in a failuer. Not sure how to get around this one except for fixing the docbook issue.

[Comment 2 SpanKY 2003-11-21 13:27:23 UTC]

FEATURES=noauto

[Comment 3 Svein Erik Brostigen 2003-11-21 14:34:20 UTC]

Yes, that works.

But, why are some ebuilds re-running the config script when it has already been run?