https://sourceware.org/bugzilla/show_bug.cgi?id=28848
--- Comment #7 from Richard Earnshaw <rearnsha at gcc dot gnu.org> --- (In reply to Nick Clifton from comment #6) > Fair enough. The thing that worries me is that the problematic file - > crti.o - comes from glibc and is going to affect the building of a lot of > projects. So whilst glibc can be fixed, that will take some time, and in > the meantime other peoples projects are stuck. A solution which will allow > builds to complete - even if it means ignoring a warning message from the > linker, is probably preferable to triggering an assert. It doesn't come from glibc, it comes from a debian-local patch to glibc, as I understand it. -- You are receiving this mail because: You are on the CC list for the bug.
