| 1 |
Rupert Young (Restart) schreef: |
| 2 |
> grep: /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.1/libstdc++.la: No such |
| 3 |
> file |
| 4 |
> |
| 5 |
> or directory |
| 6 |
> |
| 7 |
> /bin/sed: can't read |
| 8 |
> |
| 9 |
> /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.1/libstdc++.la: No such file or |
| 10 |
> |
| 11 |
> directory |
| 12 |
> |
| 13 |
> libtool: link: `/usr/lib/gcc/x86_64-pc-linux-gnu/3.4.1/libstdc++.la' |
| 14 |
> is |
| 15 |
> |
| 16 |
> not a valid libtool archive |
| 17 |
> |
| 18 |
|
| 19 |
This message, no matter what emerge you encounter it in, is a known |
| 20 |
error that means |
| 21 |
|
| 22 |
run the |
| 23 |
|
| 24 |
fix_libtools_files.sh |
| 25 |
|
| 26 |
script. |
| 27 |
|
| 28 |
You should find in in /sbin (the script is installed by the emerge of |
| 29 |
gcc), so root should just be able to run it to fix the issue. Then run |
| 30 |
the emerge again. |
| 31 |
|
| 32 |
Hope this helps. |
| 33 |
Holly |
| 34 |
-- |
| 35 |
gentoo-user@g.o mailing list |
Archives