1 |
On Mon, 5 Mar 2007 23:04:34 +0800, Mark David Dumlao wrote: |
2 |
|
3 |
> > This means either =sys-libs/libstdc++-v3-3.3* or =sys-devel/gcc-3.3*. |
4 |
> > If neither is installed the first listed will be used. this indicates |
5 |
> > that you already have gcc-3.3* installed. If you have nothing that |
6 |
> > needs it (very few packages fail to compile on 4.1 now), you can |
7 |
> > unmerge gcc-3.3 and the next emerge world will install |
8 |
> > sys-libs/libstdc++ instead. |
9 |
> |
10 |
> |
11 |
> hey thanks. So I think the more elegant solution is to install |
12 |
> sys-libs/libstdc++, |
13 |
> unmerge my overlayed virtual/libstdc++, delete my overlayed |
14 |
> virtual/libstdc++, |
15 |
> then reemerge --oneshot virtual/libstdc++ again, this time using the |
16 |
> one in the |
17 |
> portage tree. |
18 |
|
19 |
Do you already have sys-libs/libstdc++ installed? If you had, you |
20 |
wouldn't need GCC 3.3. In fact, I have a feeling the packages are mutually |
21 |
exclusive as both provide libstdc++. Just remove your overlayed version, |
22 |
remove any installed versions of gcc-3.3* and update world again. |
23 |
|
24 |
> I don't think I can just delete my overlay before then |
25 |
> or it might |
26 |
> fess up unmerging. |
27 |
|
28 |
It won't. unmerging doesn't use the ebuild in the portage tree but the |
29 |
one saved in /var/db/pkg when the package was merged. |
30 |
|
31 |
|
32 |
-- |
33 |
Neil Bothwick |
34 |
|
35 |
I don't work here. I'm a consultant. |