| 1 |
> |
| 2 |
> > I checked the ebuild of virtual/libstdc++ and it gives me an rdepends |
| 3 |
> > of = gcc-3.3.* |
| 4 |
> |
| 5 |
> The full depend is |
| 6 |
> |
| 7 |
> RDEPEND="|| ( =sys-libs/libstdc++-v3-3.3* =sys-devel/gcc-3.3* )" |
| 8 |
> |
| 9 |
> This means either =sys-libs/libstdc++-v3-3.3* or =sys-devel/gcc-3.3*. If |
| 10 |
> neither is installed the first listed will be used. this indicates that |
| 11 |
> you already have gcc-3.3* installed. If you have nothing that needs it |
| 12 |
> (very few packages fail to compile on 4.1 now), you can unmerge gcc-3.3 |
| 13 |
> and the next emerge world will install sys-libs/libstdc++ instead. |
| 14 |
|
| 15 |
|
| 16 |
hey thanks. So I think the more elegant solution is to install |
| 17 |
sys-libs/libstdc++, |
| 18 |
unmerge my overlayed virtual/libstdc++, delete my overlayed |
| 19 |
virtual/libstdc++, |
| 20 |
then reemerge --oneshot virtual/libstdc++ again, this time using the one in |
| 21 |
the |
| 22 |
portage tree. I don't think I can just delete my overlay before then or it |
| 23 |
might |
| 24 |
fess up unmerging. |
| 25 |
|
| 26 |
-- |
| 27 |
thing. |
Archives