public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/61652] Option --enable-libstdcxx-debug doesn't build debug version of libsupc++.so Date: Wed, 25 Mar 2015 18:28:00 -0000 [thread overview] Message-ID: <bug-61652-4-ynBnmAlWaf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-61652-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61652 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2015-03-25 CC|jwakely.gcc at gmail dot com | Summary|Option |Option |--enable-libstdcxx-debug |--enable-libstdcxx-debug |doesn't pass debug compile |doesn't build debug version |options to libstdc++.so |of libsupc++.so Ever confirmed|0 |1 --- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> --- The option works perfectly, you should be able to look in $target/libstdc++-v3/config.log and see something like this: configure:17333: Debug build flags set to -g3 -O2 The problem is that libsupc++ is only build once, there's no separate debug/libsupc++.so, and dyncast.o is part of libsupc++.
prev parent reply other threads:[~2015-03-25 18:22 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-06-30 0:28 [Bug c++/61652] New: Option --enable-libstdcxx-debug doesn't pass debug options to libstdc++.so yuri at tsoft dot com 2015-03-25 18:08 ` [Bug c++/61652] Option --enable-libstdcxx-debug doesn't pass debug compile " redi at gcc dot gnu.org 2015-03-25 18:28 ` redi at gcc dot gnu.org [this message]
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-61652-4-ynBnmAlWaf@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /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).