I did a stage 2 install I ran emerge --fetchonly system emerge system sat back and fell asleap. It got to autoconf and becasue I didn't already have it installed, it ran through a list of checks, and found that I needed autoconf to be installed already and exit(1). I then tired this again, and the same thing happend. Then I ran emerge autoconf, and it fixed the problem. Reproducible: Always Steps to Reproduce: 1.emerge --fetchonly system 2.emerge system 3.wait for autoconf to be compiled Actual Results: I recveaced an error that said that I needed autoconf v2.48 in my PATH in order for autoconf to install Expected Results: it should have compailed autoconf from the downloaded source code, I have never had this happen when I ignored the --fechonly. I am running an amd atholon-xp, make.conf options are set to "march-atholon-xp -03 -pipe" Western Digital 40GB HD asus motherbord I think DDR266 compatable 512MB ram cd rom nvidia geforce2 pci card
We are only reponsible for the media itself, not the bootstrap process.
what package did it fail on? /var/log/emerge.log may help.
what package failed ? autoconf failed ? you should post the error ...
See Bug 71411. It fails while emerging automake during emerge system. The above mentioned bug is marked as fixed, but it is not fixed at all, I have just experienced it with fresh 2004.3 stage 2 install. Also see Bug 73232 - it can
See Bug 71411. It fails while emerging automake during emerge system. The above mentioned bug is marked as fixed, but it is not fixed at all, I have just experienced it with fresh 2004.3 stage 2 install. Also see Bug 73232 - it can´t be fixed via emerging autoconf, the dependencies are circular. :-( Workaround: 1. emerge -a libtool (now the order of packages is correct) 2. continue with emerge system
