| 1 |
On 9/10/05, Frank Schafer <frank.schafer@×××××××××.cz> wrote: |
| 2 |
> ... or which distribution to install during less than 4 days? |
| 3 |
> |
| 4 |
> Hi list, |
| 5 |
> |
| 6 |
> as I wrote yesterday I planned to complete installation after work |
| 7 |
> (started ``emerge --emptytree system'' in the morning). |
| 8 |
> |
| 9 |
> When I returned home from work I found in the logs, that ``emerge |
| 10 |
> --emptytree system'' failed at package 28 of 186 |
| 11 |
> |
| 12 |
> python-fcksum-1.7.1 |
| 13 |
> i386-pc-linux-gnu-gcc ....bla...bla |
| 14 |
> ^ |
| 15 |
> | |
| 16 |
> +- !!!!!!!!!!!!!!!!!!!!! |
| 17 |
> |
| 18 |
> gcc-config error: |
| 19 |
> could not run/locate "i386-pc-linux-gnu-gcc" |
| 20 |
> |
| 21 |
> My architecture is i686 and it seems that 27 packages before |
| 22 |
> python-fchksum found the i686(that's SIX-eight-six)-pc-linux-gnu-gcc. |
| 23 |
> |
| 24 |
> Could be my fault. I had set up ACCEPT_KEYWORDS to "~x86". |
| 25 |
|
| 26 |
That's the first problem. Unless you want to deal with explosions, |
| 27 |
don't set your entire system to be unstable. That's a recipe for |
| 28 |
problems. Leave the global setting at stable. Then, if you need an |
| 29 |
unstable version use /etc/portage/package.keywords to set ~x86 for |
| 30 |
just the package you want to install. |
| 31 |
|
| 32 |
> |
| 33 |
> Today in the morning I started up from scratch. That's about an hour of |
| 34 |
> editing files, making file systems and so on, 1,5 hours of bootstrap.sh. |
| 35 |
> |
| 36 |
> ``emerge -p --emptytree system'' showed me, that it will install |
| 37 |
> python-fchksum with the ACCEPT_KEYWORDS="x86" too. So far, so good. |
| 38 |
> Yesterday I got a portage snapshot 20050907, today I got a portage |
| 39 |
> snapshot 20050908. Maybe the bug is fixed. So I started emerge system. |
| 40 |
> At least it didn't install two versions of gcc. That saved some time. It |
| 41 |
> ran 2,5 hours and ... |
| 42 |
> |
| 43 |
> ... kabooooom ... |
| 44 |
> |
| 45 |
> Unfortunately I can't tell you if the python-fchksum failure has gone |
| 46 |
> away. I didn't reach this ebuild :( |
| 47 |
> |
| 48 |
|
| 49 |
I suggest starting from a stage3 build. I've installed many stage 3 |
| 50 |
builds and it nearly always works with no breakage. Once your minimal |
| 51 |
system up and running (always go for minimal on the initial emerge, |
| 52 |
then boot into your system, then emerge more) then you can easily do |
| 53 |
an emptytree emerge to re-build things....if you *really* want to. I'm |
| 54 |
of the mind that starting with stage3 is perfectly fine. Eventually |
| 55 |
all of those packages will be updated and recompiled, so there's |
| 56 |
really no reason to do it manually right at the beginning. |
| 57 |
|
| 58 |
One more thing. What optimization setting(s) are you using? |
| 59 |
|
| 60 |
-- |
| 61 |
Justin Patrin |
| 62 |
|
| 63 |
-- |
| 64 |
gentoo-user@g.o mailing list |
Archives