On Mon, Aug 3, 2009 at 1:22 PM, Willie Wong 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 ~ #
>>
>> dra
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 ~
On Sat, Aug 1, 2009 at 2:33 PM, Jacob Todd wrote:
> On Sat, Aug 01, 2009 at 04:41:51PM -0700, Mark Knecht wrote:
>> I was updating my wife's machine today and noticed that there are a
>> number of older/stranded gcc-config's left on the machine. I still
>> have gcc-4.1.2 but the other 3.3/3.4 versi
On Sat, Aug 01, 2009 at 04:41:51PM -0700, Mark Knecht wrote:
> I was updating my wife's machine today and noticed that there are a
> number of older/stranded gcc-config's left on the machine. I still
> have gcc-4.1.2 but the other 3.3/3.4 versions should not remain.
>
> How would I remove these?
>
I was updating my wife's machine today and noticed that there are a
number of older/stranded gcc-config's left on the machine. I still
have gcc-4.1.2 but the other 3.3/3.4 versions should not remain.
How would I remove these?
Thanks,
Mark
dragonfly ~ # gcc-config -l
[1] i686-pc-linux-gnu-3.3.3
5 matches
Mail list logo