Opened 12 years ago
Last modified 10 years ago
#4589 new Bugs
<runtime-debugging>on does nothing for libstdc++...
| Reported by: | Owned by: | Vladimir Prus | |
|---|---|---|---|
| Milestone: | To Be Determined | Component: | build |
| Version: | Boost 1.43.0 | Severity: | Problem |
| Keywords: | Cc: | flast@… |
Description
...but should at least <define>_GLIBCXX_DEBUG to enable libstdc++ debug mode.
Attachments (1)
Change History (4)
comment:1 by , 12 years ago
| Component: | Building Boost → build |
|---|---|
| Owner: | set to |
comment:2 by , 10 years ago
| Cc: | added |
|---|
by , 10 years ago
| Attachment: | boost-libstdc++-runtime-debugging.patch added |
|---|
comment:3 by , 10 years ago
I think that should use toolset.flags in gcc.jam like followings.
--- tools/build/v2/tools/gcc.jam
+++ tools/build/v2/tools/gcc.jam
@@ -490,6 +490,7 @@ toolset.flags gcc.compile DEFINES <define> ;
toolset.flags gcc.compile INCLUDES <include> ;
toolset.flags gcc.compile.c++ TEMPLATE_DEPTH <c++-template-depth> ;
toolset.flags gcc.compile.fortran USER_OPTIONS <fflags> ;
+toolset.flags gcc.compile.c++ DEFINES <runtime-debugging>on : _GLIBCXX_DEBUG ;
rule compile.c++.pch ( targets * : sources * : properties * )
{
I tested under x86_64-linux-gnu / GCC 4.7.2 and works fine.
Note:
See TracTickets
for help on using tickets.

an old patch that fixes this issue.