This is the mail archive of the binutils@sourceware.org mailing list for the binutils project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
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 > 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
Attachment:
signature.asc
Description: This is a digitally signed message part.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |