This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/52765] -std=c++0x requires multilib for non-optimized libstdc++
- From: "redi at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 30 Mar 2012 09:59:51 +0000
- Subject: [Bug libstdc++/52765] -std=c++0x requires multilib for non-optimized libstdc++
- Auto-submitted: auto-generated
- References: <bug-52765-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52765
--- Comment #10 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-03-30 09:59:51 UTC ---
(In reply to comment #9)
> I have experimented with this configure option. I didn't know about it: what is
> the intended way of using the debug libraries?
I use debug/libstdc++.so via LD_LIBRARY_PATH when I want to run in gdb and
step-through code in the library. i.e. I link as normal, but switch to using
the debug lib at run-time. Obviously if using static linking that doesn't work
so you'd have to decide to use that lib at link-time.
I mentioned it here because it's a common (and supported) way to get a
libstdc++ built with -O0 while keeping the primary libs built with the usual
flags (-O2 etc.)