I had gcc-3.2.1 installed as my default complier. After emerging gcc-2.95.3-r8 for some embedded development I was doing, I emerged gcc-config to switch between the two. gcc-config happily overwrote the binaries (replacing them with wrappers) for 3.2.1 when I switched to 2.95.3 ... which of course broke my real system badly, leaving me with (almost) no way to switch back. gcc-config should have warned me that the gcc-3.2.1 I had installed was not compatible with it, or it should have upgraded it to one that was. Reproducible: Didn't try Steps to Reproduce: 1.install gcc-3.2.1, emerge gcc-config 2.install gcc compatible with gcc-config 3.use gcc-config to setup gcc installed in step 2. 4. gcc-3.2.1 is now broken. Actual Results: gcc-config overwrote actuall gcc binaries with wrappers, breaking gcc-3.2.1 install. Expected Results: refused to install, or upgraded gcc-3 ebuild to one compatible with gcc-config.
When last did you update ? gcc-3.2.1 is not in portage anymore, and gcc-3.2.1-r7 (from -r5 already I think) did support gcc-config ...
Before this install, I updated around 1.4rc2 ? (I know, I should have updated my entire install when 1.4 came out, but everything was working just fine, if it ain't broke, don't fix it...)
This is why there is no more ebuilds without gcc-config support. I tried to sync everything over months, and then removed the ebuilds not supporting it. I am marking this as wont fix, because all the preparation have been done, and it is difficult to have gcc-config installing the first time not assuming it should setup everything (as that could possibly break bootstrap). If you need packages to get up and going, please mail me with your specs.
