| 1 |
Mick <michaelkintzios@×××××.com> [14-12-19 17:12]: |
| 2 |
> On Friday 19 Dec 2014 15:53:53 meino.cramer@×××.de wrote: |
| 3 |
> > Mick <michaelkintzios@×××××.com> [14-12-19 16:52]: |
| 4 |
> > > On Friday 19 Dec 2014 15:23:58 meino.cramer@×××.de wrote: |
| 5 |
> > > > Peter Humphrey <peter@××××××××××××.uk> [14-12-19 16:12]: |
| 6 |
> > > > > On Friday 19 December 2014 11:18:34 Mick wrote: |
| 7 |
> > > > > > I run fix_libtool_files.sh after a new gcc |
| 8 |
> > > > > > is installed, BEFORE I remove the old version. I made a bit of a |
| 9 |
> > > > > > habit of this, but I don't know if modern ebuilds of gcc actually |
| 10 |
> > > > > > run the same script post install. |
| 11 |
> > > > > |
| 12 |
> > > > > I've found that emerge -c gcc runs fix_libtool_files.sh |
| 13 |
> > > > > automatically. This has been true for quite a while now. |
| 14 |
> > > > |
| 15 |
> > > > Hi Peter, |
| 16 |
> > > > |
| 17 |
> > > > that implies that running fix_libtool_files.sh right after installing |
| 18 |
> > > > gcc is ok before removing the old gcc. This is the opposite from |
| 19 |
> > > > previous mail. |
| 20 |
> > > > |
| 21 |
> > > > By the way: I could'n find optino "-c" for emerge in the manpages... |
| 22 |
> > > |
| 23 |
> > > Meino, to avoid misunderstandings: |
| 24 |
> > > |
| 25 |
> > > 1. Emerge the new gcc package. |
| 26 |
> > > |
| 27 |
> > > 2. Use gcc-config to change to the new gcc version. |
| 28 |
> > > |
| 29 |
> > > 3. Run 'env-update && source /etc/profile'. |
| 30 |
> > > |
| 31 |
> > > 4. Run fix_libtool_files.sh, although I would think that this is |
| 32 |
> > > redundant these days. |
| 33 |
> > > |
| 34 |
> > > 5. Unmerge the old gcc version. |
| 35 |
> > |
| 36 |
> > Hi Mick, |
| 37 |
> > |
| 38 |
> > thanks for makeing things clear! :) |
| 39 |
> > One man - one word - one gcc version! :)) |
| 40 |
> > |
| 41 |
> > THX! |
| 42 |
> |
| 43 |
> You're welcome. Peter's right the '--depclean --verbose' options will warn |
| 44 |
> you if something you have already installed depends on the old gcc version. |
| 45 |
> |
| 46 |
> -- |
| 47 |
> Regards, |
| 48 |
> Mick |
| 49 |
|
| 50 |
Hi, |
| 51 |
|
| 52 |
backup done! |
| 53 |
|
| 54 |
now... |
| 55 |
|
| 56 |
gcc-4.8.3 is installed, gcc-config points to the new compiler, the |
| 57 |
environment is updated (I logged out and in again) and I checked |
| 58 |
/etc/env.d/04gcc-armv7a-hardfloat-linux-gnueabi for using the new |
| 59 |
compiler. So everything is fine...except... |
| 60 |
|
| 61 |
If I would remove the old compiler now, my system would again be |
| 62 |
broken. |
| 63 |
|
| 64 |
I run the following little loop (zsh) "(.)" means: "only files"): |
| 65 |
|
| 66 |
for i in /sbin/*(.) /bin/*(.) /usr/sbin/*(.) /usr/bin/*(.) |
| 67 |
do |
| 68 |
ldd $i | grep -q -s '/usr/lib/gcc/armv7a-hardfloat-linux-gnueabi/4.7.3/libgcc_s.so.1' |
| 69 |
if [[ "$?" == "0" ]] ; then echo $i >> /tmp/gccfiles6.txt ; fi |
| 70 |
done |
| 71 |
|
| 72 |
I did find |
| 73 |
|
| 74 |
1033 |
| 75 |
|
| 76 |
executables still linked against |
| 77 |
|
| 78 |
/usr/lib/gcc/armv7a-hardfloat-linux-gnueabi/4.7.3/libgcc_s.so.1 |
| 79 |
|
| 80 |
and may be there are more being linked against other libs of the old |
| 81 |
compiler. |
| 82 |
|
| 83 |
Should I rebuild Gentoo? |
| 84 |
This would take a very very long time on this little system... |
| 85 |
|
| 86 |
How to proceed now? |
| 87 |
|
| 88 |
Best |
| 89 |
Meino |
Archives