> I believe that C++ tests pick the correct bits/c++config for > -m32. Can't libitm do something similar?
The problem is that the -I for the build is chosen at the toplevel, *before* iterating over the multilibs, whereas the -I for testing is chosen in dejagnu, *after* iterating over the multilibs. This, despite the toplevel *build* flags coming from "libstdc++-v3/scripts/testsuite_flags" (which returns different results for each multilib).
