On Mon, Aug 3, 2009 at 1:22 PM, Willie Wong<ww...@math.princeton.edu> wrote:
> On Mon, Aug 03, 2009 at 01:03:39PM -0700, Penguin Lover Mark Knecht squawked:
>> dragonfly ~ # emerge -Cp =cat/pack-ver
>> !!! '=cat/pack-ver' is not a valid package atom.
>> !!! Please check ebuild(5) for full details.
>> dragonfly ~ #
>>
>> dragonfly ~ # eix pack-ver
>> No matches found.
>> dragonfly ~ #
>
> The OP meant cat as in "category", pack as in "package name" and ver
> as in "version". You are supposed to supply the correct package and
> version and category for the command.
>
> For example, to unmerge gcc-4.3.0 would be
>
> emerge --unmerge =sys-devel/gcc-4.3.0
>
> substitute the package you want to remove as applicable.
>
> W

Please Willie, that's too obvious and was attempted before I posted
the first time. ;-)

I repeat that the suggestion from Jacob doesn't work:

dragonfly ~ # gcc-config -l
 [1] i686-pc-linux-gnu-3.3.3
 [2] i686-pc-linux-gnu-3.4.4
 [3] i686-pc-linux-gnu-3.4.4-hardened
 [4] i686-pc-linux-gnu-3.4.4-hardenednopie
 [5] i686-pc-linux-gnu-3.4.4-hardenednopiessp
 [6] i686-pc-linux-gnu-3.4.4-hardenednossp
 [7] i686-pc-linux-gnu-4.3.2 *
dragonfly ~ # emerge -Cp =sys-devel/gcc-3.4.4

>>> These are the packages that would be unmerged:

--- Couldn't find '=sys-devel/gcc-3.4.4' to unmerge.

>>> No packages selected for removal by unmerge
dragonfly ~ # emerge -Cp =sys-devel/gcc-3.3.3

>>> These are the packages that would be unmerged:

--- Couldn't find '=sys-devel/gcc-3.3.3' to unmerge.

>>> No packages selected for removal by unmerge
dragonfly ~ #

Again as history, I first noticed this issue when emerging gcc-4.3.2.
I had 4.1.2 on the system, in use, as well as these old line items in
gcc-config. Once I had rebuilt the system with 4.3.2 I did an emerge
-C =sys-devel/gcc-4.1.2 and got rid of that one both from the system
and this list, but this thread was about 'stranded' options which are
the 3.3.3 and 3.4.4 selections.

Are these options held in a file somewhere that can be edited by hand?
Is there some option to gcc-config that can clean them up?

Thanks,
Mark

Reply via email to