On Sat, Aug 1, 2009 at 2:33 PM, Jacob Todd<jaketodd...@gmail.com> 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 versions should not remain. >> >> How would I remove these? >> >> Thanks, >> Mark >> >> 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.1.2 >> [8] i686-pc-linux-gnu-4.3.2 * >> dragonfly ~ # >> > > emerge -C =cat/pack-ver > > -- > Jake Todd > // If it isn't broke, tweak it! >
So far I've been unable to get this working. Tried to Google around for more info on this but found nothing so possibly it's just a spelling problem I haven't figured out? I've finished updating the machine and this is one of the last things I'd like to take care of. No rush. Doesn't hurt anything that they are there, but would be nice to clean up. Thanks, Mark 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 ~ #
