| 1 |
Ioannis Aslanidis wrote: |
| 2 |
> I have run into a trouble when emerging for example beep-media-player |
| 3 |
> and getting the following: |
| 4 |
> |
| 5 |
> |
| 6 |
> grep: /usr/lib/gcc/i686-pc-linux-gnu/3.4.2.2.2.2/libstdc++.la: No such |
| 7 |
> file or directory |
| 8 |
> /bin/sed: can't read |
| 9 |
> /usr/lib/gcc/i686-pc-linux-gnu/3.4.2.2.2.2/libstdc++.la: No such file |
| 10 |
> or directory |
| 11 |
> libtool: link: `/usr/lib/gcc/i686-pc-linux-gnu/3.4.2.2.2.2/libstdc++.la' |
| 12 |
> is not a valid libtool archive |
| 13 |
> |
| 14 |
> It makes no sense that 3.4.2.2.2.2 so: |
| 15 |
> Which is the variable that is being read and where is it stored? I |
| 16 |
> didn't find it neither in /etc/env.d/ nor in /etc/env.d/gcc/ |
| 17 |
> |
| 18 |
> Thanks for the info. |
| 19 |
|
| 20 |
when you emerge gcc and the ebuild detects that you're merging a new |
| 21 |
version, it runs fix_libtool_files.sh <old version>. this fixes any |
| 22 |
references to <old version> so that they now point to the current gcc |
| 23 |
version. obviously you've never installed 3.4.2.2.2.2, so something is |
| 24 |
going seriously wrong there... |
| 25 |
|
| 26 |
gcc-config to your current compiler and run fix_libtool_files.sh 3.4.2.2.2.2 |
| 27 |
|
| 28 |
|
| 29 |
|
| 30 |
-- |
| 31 |
gentoo-dev@g.o mailing list |
Archives