Can not upgade to glibc-2.12.2. This is a new install and I am upgrading from the glibc that came with the Hardened Stage 3 tar ball. configure: error: forced unwind support is required * ERROR: sys-libs/glibc-2.12.2 failed (compile phase): * failed to configure glibc Reproducible: Always Steps to Reproduce: 1.install stage 3 tar ball 2.upgrade glibc 3. Actual Results: configure: error: forced unwind support is required * ERROR: sys-libs/glibc-2.12.2 failed (compile phase): * failed to configure glibc Expected Results: glibc-2.12.2 installed Please see attachement for emege --info and emerge output for glbic. This is on a i3 Intel mobile cpu using 64bit libraries(system). double checked to make sure softlinks were correct for libraries.
Created attachment 274447 [details] Emerge output of glibc and emerge --info Emerge output of glibc and emerge --info
These kinds of errors I have only seen when trying to switch no-multilib -> multilib profiles. Please check so that is not in fact what you are currently doing.
(In reply to comment #2) > These kinds of errors I have only seen when trying to switch no-multilib -> > multilib profiles. > Please check so that is not in fact what you are currently doing. @xake, I'm pretty sure that's it, take a look at this: /usr/lib/gcc/x86_64-pc-linux-gnu/4.4.5/../../../../x86_64-pc-linux-gnu/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-pc-linux-gnu/4.4.5/libgcc.a when searching for -lgcc /usr/lib/gcc/x86_64-pc-linux-gnu/4.4.5/../../../../x86_64-pc-linux-gnu/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-pc-linux-gnu/4.4.5/libgcc.a when searching for -lgcc /usr/lib/gcc/x86_64-pc-linux-gnu/4.4.5/../../../../x86_64-pc-linux-gnu/bin/ld: cannot find -lgcc collect2: ld returned 1 exit status @darin, can you tell use which stage3 you used --- particularly mutlilib vs no-multilib. And also give us the output of eselect profile list. Try switching to multilib and seeing if glibc then builds.
I am using stage3-amd64-hardened-20110428.tar.bz2. I can not submit the tar ball though....seems to big to be accepted.
Also wanted to state that Aleister said this isn't a multilib problem but a bug that Blue also hit.
By the way, have you tried re-emerging gcc?
I helped the reporter out in IRC. gcc -print-multi-lib showed that he was working with a no-multilib system. He's repeating his steps with stage3-amd64-hardened-20110526.tar.bz2 which I check and is showing correct multilib. I'm going to close this for now. Please feel free to reopen if the 20110526 tarball shows the same misbehavior.
