| 1 |
On Friday 02 June 2006 00:12, Sven Köhler wrote: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> it seems, i have some *.la files on my system, that don't belong to any |
| 5 |
> ebuild anymore. I noticed that, because the new revdep-rebuild |
| 6 |
> (gentoolkit 0.2.2) also check *.la files, and some were broken (pointing |
| 7 |
> to a libstdc++.la of gcc 4.1.1 - but gcc 4.1.1 has none). |
| 8 |
> |
| 9 |
> So the history is: |
| 10 |
> - gcc 3.4.5 was installed |
| 11 |
> - emerged gcc 4.1.1 |
| 12 |
> (so 3.4.5 _and_ 4.1.1 were installed) |
| 13 |
> - updated gcc 3.4.5 to 3.4.6 |
| 14 |
> (4.1.1 remained installed) |
| 15 |
> |
| 16 |
> so after gcc 3.4.5 was unmerged, there was this procedure that updates |
| 17 |
> all the *.la files which point to the (now uninstalled) libstdc++ of gcc |
| 18 |
> 3.4.5. |
| 19 |
> |
| 20 |
> Could it be, that this procedure modifies the timestamps of the *.la |
| 21 |
> files? And is this the reason, that the *.la files don't get unmerged? |
| 22 |
|
| 23 |
That's correct: |
| 24 |
https://bugs.gentoo.org/show_bug.cgi?id=71265 |
| 25 |
|
| 26 |
-- |
| 27 |
gentoo-dev@g.o mailing list |
Archives