checking whether /usr/lib/gcc/x86_64-unknown-linux-gnu/4.4.1/../../../../x86_64-unknown-linux-gnu/bin/as is GNU as... yes checking whether /usr/lib/gcc/x86_64-unknown-linux-gnu/4.4.1/../../../../x86_64-unknown-linux-gnu/bin/ld is GNU ld... yes checking for /usr/lib/gcc/x86_64-unknown-linux-gnu/4.4.1/../../../../x86_64-unknown-linux-gnu/bin/as... /usr/lib/gcc/x86_64-unknown-linux-gnu/4.4.1/../../../../x86_64-unknown-linux-gnu/bin/as checking version of /usr/lib/gcc/x86_64-unknown-linux-gnu/4.4.1/../../../../x86_64-unknown-linux-gnu/bin/as... 2.20.51.0.1.20090905, bad checking for /usr/lib/gcc/x86_64-unknown-linux-gnu/4.4.1/../../../../x86_64-unknown-linux-gnu/bin/ld... /usr/lib/gcc/x86_64-unknown-linux-gnu/4.4.1/../../../../x86_64-unknown-linux-gnu/bin/ld checking version of /usr/lib/gcc/x86_64-unknown-linux-gnu/4.4.1/../../../../x86_64-unknown-linux-gnu/bin/ld... 2.20.51.0.1.20090905, bad checking for pwd... /bin/pwd checking for i686-pc-linux-gnu-gcc... (cached) x86_64-unknown-linux-gnu-gcc checking version of x86_64-unknown-linux-gnu-gcc... 4.4.1, ok checking for gnumake... no checking for gmake... gmake checking version of gmake... 3.81, ok checking for gnumsgfmt... no checking for gmsgfmt... gmsgfmt checking version of gmsgfmt... 0.17, ok checking for makeinfo... makeinfo checking version of makeinfo... 4.13, ok checking for sed... sed checking version of sed... 4.2.1, ok checking for autoconf... autoconf checking whether autoconf works... yes configure: error: *** These critical programs are missing or too old: as ld *** Check the INSTALL file for required versions. * * ERROR: sys-libs/glibc-2.10.1 failed.
http://sourceware.org/git/?p=glibc.git;a=patch;h=4c14c8c348ee3e9a5fea3608cabcabdb275b6141
(In reply to comment #1) > http://sourceware.org/git/?p=glibc.git;a=patch;h=4c14c8c348ee3e9a5fea3608cabcabdb275b6141 Uum… do I just patch the source with that? Your message is a bit… short… ^^ Who will do the ebuild and put in into Portage?
Created attachment 204136 [details, diff] Output of patching glibc-2.10.1 with the patch mentioned in commend #1 I just tried that patch, by modifying the ebuild as follows: > eblit-src_unpack-post() { > ? > einfo "Patching bug 284393 (sys-libs/glibc doesn't like the new binutils)" > epatch "${FILESDIR}"/2.10.1-r1/new-binutils.patch …, calling it glibc-2.10.1-r1, and using the file linked in comment #1 as “new-binutils.patch”. The result was that the patch failed with the output in the attached file. :/
Ah great. Now that failed emerge with your patch killed my original »emerge -e world«, which was at 860 of 1304 packages and had compiled since yesterday noon! Thank you VERY much, Ryan. :( I HATE that bug :/ (I’m Going to file a report for that one! :)
Created attachment 204151 [details, diff] the Navid-friendly version sorry, i assumed that if you're using a masked binutils version you would know how to apply a patch from upstream. :P you forgot to cd "${S}" before epatch, but the patch would have failed anyways because of the Changelog hunk. here's one that will apply.
(In reply to comment #5) > sorry, i assumed that if you're using a masked binutils version you would know > how to apply a patch from upstream. :P It’s ok. I accept being called stupid for this. ^^ /me is living on the edge. The best way to learn, is to crash and burn. :P > you forgot to cd "${S}" before epatch, but the patch would have failed anyways > because of the Changelog hunk. here's one that will apply. Thank you. :) I thought epatch would do this automatically. But I should have read the epatch documentation I guess. P.S.: You have won one free question about Haskell, game design, psychology, nutrition science, neural nets, or the worst quirks of the "beloved" Internet Explorer… in case you might need it. ;)
I had to play with glibc today so I added this one, hope toolchain don't mind.
(In reply to comment #7) > I had to play with glibc today so I added this one, hope toolchain don't mind. Hmm… Is there something I don’t understand? Because I don’t see how this resolves the issue…? ^^
(In reply to comment #8) > Is there something I don’t understand? Because I don’t see how this resolves > the issue…? Maybe run `emerge --sync`.
