Bug 45312 – gcc-config-1.3.5 has no default profile installed during catalyst stage building

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Pieter Van den Abeele (RETIRED) 2004-03-21 13:03:28 UTC]

When I tried using a newer gcc snapshot to build G5 optimized things, the bootstrap process always failed with some cryptic error. I finally found out (cost a lot of frustration) what caused the process to fail. gcc-config did not install a default profile. I had to add a 

gcc-config powerpc-unknown-linux-gnu-3.3.3 

to the script to make it work. My guess is that either the gcc ebuilds or the new gcc-config is at fault. 
This needs to be fixed asap :-)

[Comment 1 John Davis (zhen) (RETIRED) 2004-03-21 13:29:34 UTC]

since it always worked before, it is probably a gcc bug. stick it to 'em :)

[Comment 2 John Davis (zhen) (RETIRED) 2004-04-05 13:32:34 UTC]

actually, where did you add that fix? Was it for stage1 or something else?

[Comment 3 jochen 2004-04-19 11:28:27 UTC]

Created attachment 29634 [details, diff]
use correct path for gcc-config

that's because catalyst tries to use /usr/sbin/gcc-config (whereas the binary
is in /usr/bin)

*ouch* :-(

[Comment 4 John Davis (zhen) (RETIRED) 2004-04-26 08:16:17 UTC]

woot root # which gcc-config
/usr/bin/gcc-config
woot root # ls -l /usr/sbin/gcc-config
lrwxrwxrwx    1 root     root           17 Feb 24 15:47 /usr/sbin/gcc-config -> ../bin/gcc-config

actually, its in both (symlinked). i don't think that the symlink would cause any problems ...

[Comment 5 John Davis (zhen) (RETIRED) 2004-05-17 17:08:16 UTC]

fixed in cvs, will be in portage w/ catalyst 1.0.8