This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: binutils > 2.21.51.0.2 fails to build glibc
On Tue, Jan 11, 2011 at 9:58 PM, Mike Frysinger <vapier@gentoo.org> wrote:
> On Tuesday, January 11, 2011 23:03:02 H.J. Lu wrote:
>> On Tue, Jan 11, 2011 at 6:30 PM, Alan Modra <amodra@gmail.com> wrote:
>> > Do you think it is OK for a new GNU ld to without warning build older
>> > versions of glibc that segfault at runtime?
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>
>> Not exactly, it segfault at build-time
>
> while it may fail during `make`, it fails while executing the freshly compiled
> local binaries. ?so yes, much of glibc was compiled, and then it segfaulted
> while executing.
>
>> If you want to use the latest
>> binutils to BUILD your glibc, I think it is OK to require you to patch
>> your glibc. I can provide a patch for glibc 2.12.
>
> i think that would help out a lot of people
Please use commit 0bdbd36b52d7e46202701bb7e1658f4491e7c366
on hjl/release/2.12/x86 branch at
http://git.kernel.org/?p=devel/glibc/hjl/x86.git;a=summary
>> I fixed the problem in glibc. ?.ctor isn't standard. All ELF C run-time
>> libraries should switch to .init_array anyway.
>
> and how are they supposed to know that ? ?all people know now is that they
> upgrade their binutils, rebuild things, and the result randomly segfaults. ?if
> you're going to purpusefully link broken binaries, you need to warn people.
> -mike
I should have put a big warning in my binutils release note.
--
H.J.