Re: [gentoo-user] Remove stranded gcc-config's?

Re: [gentoo-user] Remove stranded gcc-config's?

[Jacob Todd]

[-- Attachment #1: Type: text/plain, Size: 773 bytes --]

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!

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

[gentoo-user] Remove stranded gcc-config's?

[Mark Knecht]

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 ~ #

Re: [gentoo-user] Remove stranded gcc-config's?

[Mark Knecht]

On Sat, Aug 1, 2009 at 2:33 PM, Jacob Todd<jaketodd422@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 ~ #

Re: [gentoo-user] Remove stranded gcc-config's?

[Willie Wong]

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

-- 
Pintsize: I'm always naked!
Sortir en Pantoufles: up 969 days, 19:07

Re: [gentoo-user] Remove stranded gcc-config's?

[Mark Knecht]

On Mon, Aug 3, 2009 at 1:22 PM, Willie Wong<wwong@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

[gentoo-user] Re: Remove stranded gcc-config's?

[walt]

On 08/03/2009 03:51 PM, Mark Knecht wrote:

> 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?

Have a look in /etc/env.d/gcc/ and /usr/libexec/gcc/ and /usr/lib/gcc/
for any old files or directories that shouldn't be there. Particular
attention to /etc/env.d/gcc.

Re: [gentoo-user] Re: Remove stranded gcc-config's?

[Mark Knecht]

On Mon, Aug 3, 2009 at 4:35 PM, walt<w41ter@gmail.com> wrote:
> On 08/03/2009 03:51 PM, Mark Knecht wrote:
>
>> 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?
>
> Have a look in /etc/env.d/gcc/ and /usr/libexec/gcc/ and /usr/lib/gcc/
> for any old files or directories that shouldn't be there. Particular
> attention to /etc/env.d/gcc.

Thanks Walt. slocate 3.3.3/3.4.4 sort of spreads out across the system
and shows a lot of stuff that probably shouldn't be around anymore.
/etc/env.d/gcc looks like the list of things I want to get rid of.
I'll try to double check against a system that's not having this
problem and experiement a bit with just deleting this stuff. (After
doing some backups first.)

Cheers,
Mark

Re: [gentoo-user] Re: Remove stranded gcc-config's?

[Mick]

[-- Attachment #1: Type: text/plain, Size: 2772 bytes --]

On Tuesday 04 August 2009, Mark Knecht wrote:
> On Mon, Aug 3, 2009 at 4:35 PM, walt<w41ter@gmail.com> wrote:
> > On 08/03/2009 03:51 PM, Mark Knecht wrote:
> >> 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?
> >
> > Have a look in /etc/env.d/gcc/ and /usr/libexec/gcc/ and /usr/lib/gcc/
> > for any old files or directories that shouldn't be there. Particular
> > attention to /etc/env.d/gcc.
>
> Thanks Walt. slocate 3.3.3/3.4.4 sort of spreads out across the system
> and shows a lot of stuff that probably shouldn't be around anymore.
> /etc/env.d/gcc looks like the list of things I want to get rid of.
> I'll try to double check against a system that's not having this
> problem and experiement a bit with just deleting this stuff. (After
> doing some backups first.)

I also seem to have an older gcc 3.4.5 listed:
# gcc-config -l
 [1] i686-pc-linux-gnu-3.4.5
 [2] i686-pc-linux-gnu-3.4.5-hardened
 [3] i686-pc-linux-gnu-3.4.5-hardenednopie
 [4] i686-pc-linux-gnu-3.4.5-hardenednopiessp
 [5] i686-pc-linux-gnu-3.4.5-hardenednossp
 [6] i686-pc-linux-gnu-4.3.2 *

and indeed it is still in:

$ ls -la /etc/env.d/gcc/
total 29
drwxr-xr-x 2 root root 408 Aug  4 23:03 .
drwxr-xr-x 4 root root 952 Jul  2 06:06 ..
lrwxrwxrwx 1 root root  23 May 15 06:15 .NATIVE -> i686-pc-linux-gnu-4.3.2
-rw-r--r-- 1 root root  32 May 15 06:15 config-i686-pc-linux-gnu
-rw-r--r-- 1 root root 292 Mar 30  2006 i686-pc-linux-gnu-3.4.5
-rw-r--r-- 1 root root 356 Mar 30  2006 i686-pc-linux-gnu-3.4.5-hardened
-rw-r--r-- 1 root root 361 Mar 30  2006 i686-pc-linux-gnu-3.4.5-hardenednopie
-rw-r--r-- 1 root root 364 Mar 30  2006 
i686-pc-linux-gnu-3.4.5-hardenednopiessp
-rw-r--r-- 1 root root 361 Mar 30  2006 i686-pc-linux-gnu-3.4.5-hardenednossp
-rw-r--r-- 1 root root 235 Apr  6 13:15 i686-pc-linux-gnu-4.3.2

It cannot be unmerged (not there) and fix_libtool_files.sh 3.4.5 completes 
immediately (unlike the few seconds it takes for any gcc packages that are 
still in my system).  At this stage it may just be a matter of deleting 
relevant files in /etc/env.d/gcc/ but I have not done that yet.

Where else do you find 3.3.3/3.4.4 in your system other 
than /usr/share/gcc-data/ or perhaps in portage?
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Re: Remove stranded gcc-config's?

[Mark Knecht]

On Tue, Aug 4, 2009 at 3:15 PM, Mick<michaelkintzios@gmail.com> wrote:
> On Tuesday 04 August 2009, Mark Knecht wrote:
>> On Mon, Aug 3, 2009 at 4:35 PM, walt<w41ter@gmail.com> wrote:
>> > On 08/03/2009 03:51 PM, Mark Knecht wrote:
>> >> 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?
>> >
>> > Have a look in /etc/env.d/gcc/ and /usr/libexec/gcc/ and /usr/lib/gcc/
>> > for any old files or directories that shouldn't be there. Particular
>> > attention to /etc/env.d/gcc.
>>
>> Thanks Walt. slocate 3.3.3/3.4.4 sort of spreads out across the system
>> and shows a lot of stuff that probably shouldn't be around anymore.
>> /etc/env.d/gcc looks like the list of things I want to get rid of.
>> I'll try to double check against a system that's not having this
>> problem and experiement a bit with just deleting this stuff. (After
>> doing some backups first.)
>
> I also seem to have an older gcc 3.4.5 listed:
> # gcc-config -l
>  [1] i686-pc-linux-gnu-3.4.5
>  [2] i686-pc-linux-gnu-3.4.5-hardened
>  [3] i686-pc-linux-gnu-3.4.5-hardenednopie
>  [4] i686-pc-linux-gnu-3.4.5-hardenednopiessp
>  [5] i686-pc-linux-gnu-3.4.5-hardenednossp
>  [6] i686-pc-linux-gnu-4.3.2 *
>
> and indeed it is still in:
>
> $ ls -la /etc/env.d/gcc/
> total 29
> drwxr-xr-x 2 root root 408 Aug  4 23:03 .
> drwxr-xr-x 4 root root 952 Jul  2 06:06 ..
> lrwxrwxrwx 1 root root  23 May 15 06:15 .NATIVE -> i686-pc-linux-gnu-4.3.2
> -rw-r--r-- 1 root root  32 May 15 06:15 config-i686-pc-linux-gnu
> -rw-r--r-- 1 root root 292 Mar 30  2006 i686-pc-linux-gnu-3.4.5
> -rw-r--r-- 1 root root 356 Mar 30  2006 i686-pc-linux-gnu-3.4.5-hardened
> -rw-r--r-- 1 root root 361 Mar 30  2006 i686-pc-linux-gnu-3.4.5-hardenednopie
> -rw-r--r-- 1 root root 364 Mar 30  2006
> i686-pc-linux-gnu-3.4.5-hardenednopiessp
> -rw-r--r-- 1 root root 361 Mar 30  2006 i686-pc-linux-gnu-3.4.5-hardenednossp
> -rw-r--r-- 1 root root 235 Apr  6 13:15 i686-pc-linux-gnu-4.3.2
>
> It cannot be unmerged (not there) and fix_libtool_files.sh 3.4.5 completes
> immediately (unlike the few seconds it takes for any gcc packages that are
> still in my system).  At this stage it may just be a matter of deleting
> relevant files in /etc/env.d/gcc/ but I have not done that yet.
>
> Where else do you find 3.3.3/3.4.4 in your system other
> than /usr/share/gcc-data/ or perhaps in portage?
> --
> Regards,
> Mick
>
Mick,
   I found stuff a bunch of places using slocate 3.3.3 or slocate
3.4.4, etc. I basically ended up erasing everything that wasn't
gcc-4.3.2 and it seems to have worked out OK for me so far. The
machine appears clean. I haven't discovered anything that doesn't
work. I was thinking about re-emerging gcc-4.3.2 just in case I
happened to delete something I shouldn't have, but so far everything
is cool.

Hope this helps,
Mark