* * ERROR: sys-devel/gcc-4.1.2 failed. * Call stack: * ebuild.sh, line 49: Called src_unpack * environment, line 4635: Called gcc_src_unpack * environment, line 2992: Called disgusting_gcc_multilib_HACK * environment, line 1144: Called die * The specific snippet of code: * die "Your profile is no longer supported by portage."; * The die message: * Your profile is no longer supported by portage. * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/sys-devel/gcc-4.1.2/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-devel/gcc-4.1.2/temp/environment'. BUT when i list my profiles i see: sqlserv ~ # eselect profile list Available profile symlink targets: [1] default-linux/amd64/2007.0 [2] default-linux/amd64/2007.0/desktop [3] default-linux/amd64/2007.0/no-multilib [4] default-linux/amd64/2007.0/server [5] hardened/amd64 [6] hardened/amd64/multilib [7] selinux/2007.0/amd64 [8] selinux/2007.0/amd64/hardened [9] default/linux/amd64/2008.0 [10] default/linux/amd64/2008.0/desktop [11] default/linux/amd64/2008.0/developer [12] default/linux/amd64/2008.0/no-multilib [13] default/linux/amd64/2008.0/server * [14] hardened/linux/amd64 Reproducible: Always
hooliz, you did several things wrong when submitting this bugreport. For _every_ problem with compiling/installing/running/using packages/software, you have to choose "Gentoo Linux" in the Product field. Your Summary is useless as it doesn't provide a brief description of the problem this bug was submitted for. Last but not least, you did not even read what portage told you to do in case you submit a bugreport. Do you see the line If you need support, post the topmost build error, and the call stack if relevant. in your description? This means you should post the first error which occured during compilation and not just the errormessage, portage is always giving when problems occur which cause emerge to stop unexpectedly. Furthermore, please provide the output of emerge --info as well and maybe a brief description of how to reproduce the problem in case you did some special steps to trigger the problem.
1) Please update your profile (point your favourite web browser to the URL to find out how). If that doesn't solve the problem, reopen this bug report after you do these two things: 2) Please post your `emerge --info' in a comment. 3) Please attach the file `/var/tmp/portage/sys-devel/gcc-4.1.2/temp/build.log' to this bug report.
*** Bug 251512 has been marked as a duplicate of this bug. ***
