<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "http://bugs.gentoo.org/bugzilla.dtd">

<bugzilla version="2.22.7"
          urlbase="http://bugs.gentoo.org/"
          maintainer="bugzilla@gentoo.org"
>

    <bug>
          <bug_id>20314</bug_id>
          
          <creation_ts>2003-05-02 04:35 0000</creation_ts>
          <short_desc>At stage2, emerge system fails the 1st time. Autoconf-2.57-r1 fails to build because of missing m4</short_desc>
          <delta_ts>2003-05-03 04:56:31 0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>Gentoo Linux</product>
          <component>Core system</component>
          <version>unspecified</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          
          <priority>P2</priority>
          <bug_severity>critical</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          
          <everconfirmed>1</everconfirmed>
          <reporter>david@djin.com</reporter>
          <assigned_to>release@gentoo.org</assigned_to>
          

      

      
          <long_desc isprivate="0">
            <who>david@djin.com</who>
            <bug_when>2003-05-02 04:35:36 0000</bug_when>
            <thetext>I&apos;ve building 2 systems during the last 3 days. The both had the same problem.

When running &apos;emerge system&apos; for the first time it fails on autoconf-2.57-r1. 
It claims that m4 doesn&apos;t work and that&apos;s right because m4 isn&apos;t installed. On 
both systems I&apos;ve updated the portage tree with emerge sync, but I don&apos;t think 
that was necessary (just a feeling).

After that emerge system works fine and with emerge -p system I can see 
autoconf moved down the list a little and m4 will be installed before it.

Reproducible: Always
Steps to Reproduce:
1.Start from stage 1
2.emerge system in stage 2
3.

Actual Results:  
THe build of autoconf-2.57-r1 failed

Expected Results:  
Build the system

Portage 2.0.47-r10 (default-x86-1.4, gcc-3.2.2, glibc-2.3.1-r4)
=================================================================
System uname: 2.4.20-gentoo-r2 i686 AMD Athlon(tm) Processor
GENTOO_MIRRORS=&quot;http://ftp.snt.utwente.nl/pub/os/linux/gentoo 
http://gentoo.oregonstate.edu/ 
http://www.ibiblio.org/pub/Linux/distributions/gentoo&quot;
CONFIG_PROTECT=&quot;/etc /var/qmail/control /usr/share/config /usr/kde/2/share/confi
g /usr/kde/3/share/config&quot;
CONFIG_PROTECT_MASK=&quot;/etc/gconf /etc/env.d&quot;
PORTDIR=&quot;/usr/portage&quot;
DISTDIR=&quot;/usr/portage/distfiles&quot;
PKGDIR=&quot;/usr/portage/packages&quot;
PORTAGE_TMPDIR=&quot;/var/tmp&quot;
PORTDIR_OVERLAY=&quot;&quot;
USE=&quot;x86 oss 3dnow apm arts avi crypt cups encode gif gpm gtk imlib java jpeg 
kde libg++ libwww mikmod mmx motif mpeg ncurses nls oggvorbis opengl pdflib png 
qt quicktime sdl spell svga truetype X xml2 xmms xv zlib gdbm berkdb slang 
readline tcpd pam ssl perl python -gnome ldap pic&quot;
COMPILER=&quot;gcc3&quot;
CHOST=&quot;i686-pc-linux-gnu&quot;
CFLAGS=&quot;-mcpu=athlon-tbird -O3 -pipe&quot;
CXXFLAGS=&quot;-mcpu=athlon-tbird -O3 -pipe&quot;
ACCEPT_KEYWORDS=&quot;x86&quot;
MAKEOPTS=&quot;-j2&quot;
AUTOCLEAN=&quot;yes&quot;
SYNC=&quot;rsync://rsync.gentoo.org/gentoo-portage&quot;
FEATURES=&quot;sandbox ccache distcc&quot;</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>azarah@gentoo.org</who>
            <bug_when>2003-05-03 04:56:31 0000</bug_when>
            <thetext>Ok, it was the DEPEND on util-linux that was added to man.  Is fixed
for man-1.5l-r3.
</thetext>
          </long_desc>
      
    </bug>

</bugzilla>