public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "asharif.tools at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/13695] New: glibc doesn't build properly with -frecord-gcc-switches in CFLAGS Date: Wed, 15 Feb 2012 18:54:00 -0000 [thread overview] Message-ID: <bug-13695-131@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=13695 Bug #: 13695 Summary: glibc doesn't build properly with -frecord-gcc-switches in CFLAGS Product: glibc Version: 2.11 Status: NEW Severity: normal Priority: P2 Component: libc AssignedTo: drepper.fsp@gmail.com ReportedBy: asharif.tools@gmail.com Classification: Unclassified Reproduction: 1. Build a toolchain with CFLAGS="-frecord-gcc-switches". 2. Try building an executable with gold as the linker. It will fail. See: http://sources.redhat.com/ml/binutils/2011-11/msg00238.html The reason is the following: """The glibc/csu/Makefile runs this code through a sed script that deletes everything between HEADER_ENDS and _init_PROLOG_BEGINS, which loses the ".text" directive, and the code for call_gmon_start ends up placed in the .GCC.command.line section.""" taken from this ML thread: http://sources.redhat.com/ml/binutils/2012-02/msg00109.html -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2012-02-15 18:54 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-15 18:54 asharif.tools at gmail dot com [this message] 2012-02-15 19:55 ` [Bug libc/13695] " tschwinge at sourceware dot org 2012-02-16 2:35 ` asharif.tools at gmail dot com 2012-02-16 4:29 ` asharif.tools at gmail dot com 2012-02-16 4:30 ` asharif.tools at gmail dot com 2012-02-16 11:46 ` tschwinge at sourceware dot org 2012-02-17 17:34 ` vapier at gentoo dot org 2012-02-21 0:52 ` jsm28 at gcc dot gnu.org 2014-06-26 15:28 ` fweimer at redhat dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-13695-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).