| 1 |
Bill Kenworthy <billk@×××××××××.au> [14-12-19 08:00]: |
| 2 |
> On 19/12/14 13:39, meino.cramer@×××.de wrote: |
| 3 |
> > Hi, |
| 4 |
> > |
| 5 |
> > (this happens on a embedded system) |
| 6 |
> > |
| 7 |
> > I ran into a problem I think... |
| 8 |
> > |
| 9 |
> > As adviced I run |
| 10 |
> > |
| 11 |
> > emerge --depclean -v -p |
| 12 |
> > |
| 13 |
> > after a greater update to world. |
| 14 |
> > (by the way: Updateing the world is generally to a bad idea...;) |
| 15 |
> > |
| 16 |
> > Beside other things, gcc-4.7.3 was slated for removal. As |
| 17 |
> > gcc-4.8.3 was already installed and gcc-config shows that it |
| 18 |
> > is active, I started the above command without "-p".... |
| 19 |
> > And it screws up the whole thing badly: |
| 20 |
> > There were many, many applications (the shell for example...) |
| 21 |
> > which were directly linked to |
| 22 |
> > /usr/lib/gcc/armv7a-hardfloat-linux-gnueabi/4.7.3/libgcc_s.so.1 |
| 23 |
> > and/or |
| 24 |
> > /usr/lib/gcc/armv7a-hardfloat-linux-gnueabi/4.7.3/libstdc++.so.6 |
| 25 |
> > |
| 26 |
> > After clearing the sdcard and reinstalling the backup I started |
| 27 |
> > to emerge all affected ebuilds by hand...only to find, that they |
| 28 |
> > were again linked against the old libs. |
| 29 |
> > |
| 30 |
> > I checked again with gcc-config and found: |
| 31 |
> > |
| 32 |
> > beagleboneblack:/root>gcc-config -L |
| 33 |
> > /usr/lib/gcc/armv7a-hardfloat-linux-gnueabi/4.8.3 |
| 34 |
> > beagleboneblack:/root>gcc-config -c |
| 35 |
> > armv7a-hardfloat-linux-gnueabi-4.8.3 |
| 36 |
> > beagleboneblack:/root>gcc-config -E |
| 37 |
> > export PATH="/usr/armv7a-hardfloat-linux-gnueabi/gcc-bin/4.8.3:/lib/rc/bin:/bin:/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/bin/:/opt/bin:/usr/armv7a-hardfloat-linux-gnueabi/gcc-bin/4.8.3:/usr/games/bin:/root/bin" |
| 38 |
> > export GCC_SPECS="" |
| 39 |
> > |
| 40 |
> > |
| 41 |
> > What is going on here? Why still the old compiler and its libraries |
| 42 |
> > are used? How can I convince Gentoo to finally switch ti gcc-4.8.3? |
| 43 |
> > |
| 44 |
> > What do you think? |
| 45 |
> > |
| 46 |
> > Best regards, |
| 47 |
> > Meino |
| 48 |
> > |
| 49 |
> > |
| 50 |
> |
| 51 |
> Did you run fix_libtool_files.sh? - you have to do it manually after |
| 52 |
> switching gcc to a bew version. |
| 53 |
> |
| 54 |
> BillK |
| 55 |
> |
| 56 |
> |
| 57 |
> |
| 58 |
Hi Bill, |
| 59 |
|
| 60 |
Thanks for your help and hint! :) |
| 61 |
|
| 62 |
In the meanwhile I found a trace of a bad install of version 4.8.3: |
| 63 |
/etc/env.d/*gcc* was not updated. |
| 64 |
|
| 65 |
Currently I am reinstalling the whole gcc-4.8.3. - suit and after |
| 66 |
that I will call fix_libtool_files.sh. |
| 67 |
|
| 68 |
Hope it will fix it! |
| 69 |
Best regards, |
| 70 |
Meino |
Archives