1 |
After fixinf fs errors with fsck emerge stopped working so i fixed |
2 |
with http://www.gentoo.org/proj/en/portage/doc/manually-fixing-portage.xml |
3 |
Then downloaded a stage3, chrooted, compiled gcc, created a binpkg and |
4 |
emerged it on the broken system with emerge -K |
5 |
Now i'm rebuilding the whole system. |
6 |
Thanks for all :) |
7 |
|
8 |
2010/11/8 Mick <michaelkintzios@×××××.com>: |
9 |
> On Monday 08 November 2010 18:28:58 Pau Peris wrote: |
10 |
>> Please, is there any developer/geek who can help to solve the |
11 |
>> situation? Why do i get : |
12 |
>> [code]/usr/bin/x86_64-pc-linux-gnu-gcc: Exec format error [/code] |
13 |
>> I did nothing than updating the system, also /etc/make.conf (which i |
14 |
>> took a look before getting errors) seems ok. |
15 |
> |
16 |
> I can't say why you *suddenly* started getting problems, but it may indicate |
17 |
> that there is some hardware problem which caused a fs corruption. So, check |
18 |
> the obvious for errors like hard drive (smartmontools) and memory |
19 |
> (memtest86+). |
20 |
> |
21 |
> If I were you I would follow the instructions in the previous link I sent you, |
22 |
> and use that to rebuild portage and tool chain before you finish off |
23 |
> rebuilding the packages that were giving you errors. |
24 |
> -- |
25 |
> Regards, |
26 |
> Mick |
27 |
> |