1 |
On Mon, 5 Mar 2007 18:45:23 +0800, Mark David Dumlao wrote: |
2 |
|
3 |
> I did an emerge --update --newuse world and it keeps trying to build |
4 |
> gcc-3.3.4 and ends in errors. Upon further inspection, I found that I |
5 |
> already have gcc-4.1.1-r3. Everything was working prior to that, and I |
6 |
> couldn't understand why it kept asking for gcc-3.3. I went through a |
7 |
> whole lot of equeries and headbanging to find the package that wanted |
8 |
> gcc-3.3. libstdc++ itself didn't seem to want it, but im not that good |
9 |
> at reading ebuilds just yet. |
10 |
|
11 |
Add --tree to the above emerge command. |
12 |
|
13 |
> I checked the ebuild of virtual/libstdc++ and it gives me an rdepends |
14 |
> of = gcc-3.3.* |
15 |
|
16 |
The full depend is |
17 |
|
18 |
RDEPEND="|| ( =sys-libs/libstdc++-v3-3.3* =sys-devel/gcc-3.3* )" |
19 |
|
20 |
This means either =sys-libs/libstdc++-v3-3.3* or =sys-devel/gcc-3.3*. If |
21 |
neither is installed the first listed will be used. this indicates that |
22 |
you already have gcc-3.3* installed. If you have nothing that needs it |
23 |
(very few packages fail to compile on 4.1 now), you can unmerge gcc-3.3 |
24 |
and the next emerge world will install sys-libs/libstdc++ instead. |
25 |
|
26 |
equery list gcc will show you exactly which gcc packages you have |
27 |
installed. |
28 |
|
29 |
|
30 |
-- |
31 |
Neil Bothwick |
32 |
|
33 |
Top Oxymorons Number 18: Taped live |