Richard Henderson <r...@redhat.com> writes: > There's no "good" place for this. The description in Makefile.def that > libitm uses c++ is only used insofar as the dependencies for libitm -- it's > built after libstdc++ as the language support library. If we put this into > the toplevel configure.ac directly, we have to write a bunch of shell code > which seems less than helpful. > > Putting into gcc/cp/config-lang.in is a layering violation, it's true. But > until there's another instance that needs handling, it seems premature to > build infrastructure to handle this. And it's only one line after all...
That doesn't work. It breaks bootstrap on targets that are unsupported by libitm because the stage2 compiler is built with the host g++ instead of the stage1 g++, eventually breaking down due to -Werror. You get the same error when configuring with --disable-target-libitm. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."
