| 1 |
Paul de Vrieze wrote: |
| 2 |
|
| 3 |
> The "way around this" would be to change bootstrap.sh back to building a |
| 4 |
> minimal version of the current version that is then used to compile the |
| 5 |
> rest of the system, including the C library and gcc itself. Between this |
| 6 |
> however the original bootstrap compiler could be removed. |
| 7 |
|
| 8 |
> This however goes deep into bootstrapping a linux system. A complicated |
| 9 |
> matter that is not for the weak of heart. |
| 10 |
|
| 11 |
The bootstrap.sh script, with minor bugfixes and perhaps a pause after the |
| 12 |
gcc build, is a perfectly working method of bootstrapping gentoo. |
| 13 |
|
| 14 |
Another small fact has been glossed over. The stage3 method first upgrades |
| 15 |
gcc-3.3.5 to gcc-3.3.6, then gcc-3.4.4. An incredible waste of time that |
| 16 |
easily avoided by installing from a stage1 instead of a stage3. Yes, you |
| 17 |
could run bootstrap.sh on a stage3 tarball, but that is not what the |
| 18 |
documentation tells the users to do. |
| 19 |
|
| 20 |
As a process to get gentoo installed the stage3 method sucks, period. There |
| 21 |
is absolutely no advantage to it over a stage1 whatsoever. At certain |
| 22 |
times when the stage3 tarball was only released one week previous and there |
| 23 |
have been no major upgrades, you might save time. That is a very limited |
| 24 |
window of advantage. Installing from stage1 narrows down what problems can |
| 25 |
happen considerably and would be much easier to support in the long run. |
| 26 |
|
| 27 |
Tell me where I am wrong and why. |
| 28 |
|
| 29 |
Paul I apologize, this is not directed specifically at you, I just had to |
| 30 |
find a place to jump in... |
| 31 |
|
| 32 |
-- |
| 33 |
gentoo-dev@g.o mailing list |
Archives