This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug testsuite/49741] make -k check-c++0x not multilib aware
- From: "jason at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 15 Jul 2011 03:45:17 +0000
- Subject: [Bug testsuite/49741] make -k check-c++0x not multilib aware
- Auto-submitted: auto-generated
- References: <bug-49741-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49741
--- Comment #3 from Jason Merrill <jason at gcc dot gnu.org> 2011-07-15 03:44:30 UTC ---
Hmm, it seems that --tool_opts confuses the multilib support. In g++.exp we
have
if [info exists TOOL_OPTIONS] {
lappend ALWAYS_CXXFLAGS "additional_flags=[g++_include_flags
[get_multilibs ${TOOL_OPTIONS}] ]"
lappend ALWAYS_CXXFLAGS "ldflags=[g++_link_flags [get_multilibs
${TOOL_OPTIONS}] ]\
"
} else {
lappend ALWAYS_CXXFLAGS "additional_flags=[g++_include_flags
[get_multilibs] ]"
lappend ALWAYS_CXXFLAGS "ldflags=[g++_link_flags [get_multilibs] ]"
}
And apparently [get_multilibs "-std=gnu++0x"] gives a different result from
[get_multilibs].
This is a bug in dejagnu; there was a patch submitted for this issue many years
ago at
http://lists.gnu.org/archive/html/dejagnu/2002-10/msg00007.html
but it seems to have been ignored.
Hmm, maybe I should kludge around this with a custom flag after all...