| 1 |
> When I returned home from work I found in the logs, that ``emerge |
| 2 |
> --emptytree system'' failed at package 28 of 186 |
| 3 |
> |
| 4 |
> python-fcksum-1.7.1 |
| 5 |
> i386-pc-linux-gnu-gcc ....bla...bla |
| 6 |
> ^ |
| 7 |
> | |
| 8 |
> +- !!!!!!!!!!!!!!!!!!!!! |
| 9 |
> |
| 10 |
> gcc-config error: |
| 11 |
> could not run/locate "i386-pc-linux-gnu-gcc" |
| 12 |
|
| 13 |
My guess is that during the -emptytree system emergence that gcc was built |
| 14 |
to target your system. |
| 15 |
|
| 16 |
Sometimes when this happens the internal build system gets a little confused |
| 17 |
when it is time to switch over, but this is easily resolved by running the |
| 18 |
fix_libtool_files.sh script in /sbin. |
| 19 |
|
| 20 |
You would need to do this when you get errors similar to that listed above. |
| 21 |
|
| 22 |
The good news is that you'll only need to do this during the beginning when |
| 23 |
the system is being built from scratch; once you're up and running you |
| 24 |
normally won't need to do this again. |
| 25 |
> automake-1.25-r3 |
| 26 |
> autoconf-2.58 or better is required |
| 27 |
> |
| 28 |
> Why the hell do we try to install x versions of autoconf and |
| 29 |
> automake????? |
| 30 |
|
| 31 |
Because packages have individual automake/autoconf version requirements. |
| 32 |
Each automake/autoconf is slotted, they don't take up much disk, and they're |
| 33 |
good to have around for a successful emerge. |
| 34 |
|
| 35 |
> So my presumption for the time demand of a Gentoo installation looks |
| 36 |
> like this. |
| 37 |
> |
| 38 |
> A breakage will occure every 15'th package (2 breakages during the first |
| 39 |
> 30 within 2 days). |
| 40 |
|
| 41 |
That's an analysis based upon two initial emptytree emerges. I would expect |
| 42 |
that for the 200 package estimate that you're using you will probably |
| 43 |
encounter a total of 4 breaks (I think that's what I had, it was so long |
| 44 |
ago, but there was one fix_libtool_files.sh run and a couple of changes to |
| 45 |
/etc/portage/package.keywords to enable ~x86 versions of a few packages |
| 46 |
where I needed a later version). |
| 47 |
|
| 48 |
Completing an install in 4 days will not be a problem if you have the time |
| 49 |
to check on the emerge process every now and then and resolve the minor |
| 50 |
problems that crop up. |
| 51 |
|
| 52 |
> So which distribution would you suggest me to install during less than 4 |
| 53 |
> days? I'm wondering about Slackware. |
| 54 |
|
| 55 |
You can still stick with gentoo ;-) |
| 56 |
|
| 57 |
If you don't have the time to watch over the stage 1 build process, you can |
| 58 |
jump straight to a stage 3 then update packages from there. |
| 59 |
|
| 60 |
-- |
| 61 |
gentoo-user@g.o mailing list |
Archives