| 1 |
On Friday 19 Dec 2014 15:09:37 Peter Humphrey wrote: |
| 2 |
> On Friday 19 December 2014 11:18:34 Mick wrote: |
| 3 |
> > I run fix_libtool_files.sh after a new gcc |
| 4 |
> > is installed, BEFORE I remove the old version. I made a bit of a habit |
| 5 |
> > of this, but I don't know if modern ebuilds of gcc actually run the same |
| 6 |
> > script post install. |
| 7 |
> |
| 8 |
> I've found that emerge -c gcc runs fix_libtool_files.sh automatically. This |
| 9 |
> has been true for quite a while now. |
| 10 |
|
| 11 |
Peter, I thought that this was the case, but recently I had to run |
| 12 |
fix_libtool_files.sh manually. I removed the old gcc thinking all is good, |
| 13 |
after I had switched to the new gcc with gcc-config, but I ended up with |
| 14 |
errors. I had to reinstall the old gcc, run fix_libtool_files.sh and then |
| 15 |
unmerge it again before the errors went away. |
| 16 |
|
| 17 |
-- |
| 18 |
Regards, |
| 19 |
Mick |
Archives