Neil Bothwick schreef: > On Sun, 11 Sep 2005 12:58:19 -0400, Mark Shields wrote: > > >> // start quote >> >> Building the System >> >> To start building the system, execute emerge --emptytree system. // >> end quote >> >> So you see, it does tell you to do an emerge --emptytree system, > > > When BUILDING THE SYSTEM. This thread was all about rebuilding the > system, which is a completely different, and usually unnecessary, > process. >
No, Neil, this thread (or the original issue, at least), is occurring during the initial install process: > Hi list, > > as I wrote yesterday I planned to complete installation after work > (started ``emerge --emptytree system'' in the morning). > ... because he's following the (old?) Handbook, which does say to use --emptytree, although we don't quite know why. But Frank also says: > I'd be glad for every hint. Waiting for fixage isn't an option. So possibly we might consider using our expertise to actually help the guy, in case anyone might happen to know why he's getting this breakage during his inital installation, rather than arguing about whether he should be using --emptytree or not, especially since-- as the system is not yet installed, it doesn't matter if it's explicitly stated or not, because he's essentially doing an emptytree-- *not* doing an emerge -e is not likely to solve/mitigate the issue, which is apparently that automake is trying to install before its dependency (autoconf), for unknown reasons. Holly -- [email protected] mailing list
