On Thu, 23 Aug 2012, jojelino wrote: > On 2012-08-20 AM 6:44, Ji?í Pale?ek wrote: > > Hello, > > > > I tried to run "make check-c++" from the top directory of the source > > code. During the run, all of the libgomp tests run by it failed. From > > the log file, you can see that the gcc from the system (rather than the > > gcc currently built) was run: > > > > Executing on host: gcc > > -B/mnt/extras/src/gcc2/i686-pc-linux-gnu/libgomp/ -B/mnt/extras/src ... > > ... > > gcc: error: unrecognized command line option '-fno-diagnostics-show-caret' > > > > Other tests (like libstdc++) correctly use the currently built gcc: > > > > Executing on host: /mnt/extras/src/gcc2/host-i686-pc-linux-gnu/gcc/g++ > > -shared-libgcc ... > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > > > Any ideas how this could be fixed? > > > > Regards > > Jiri Palecek > > > You need to modify Makefile to export CC,CXX variables so that dejagnu can > execute built compiler.
No, that's wrong. "make check-c++" should just work out of the box and does for most people, specifically native builds. > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51498 has similar workaround. That PR lacks analysis and comments with requests are unanswered, though it's suggesting the same thing somewhat out of the blue. If you're the author of that report, please fill in details asked for in the comments. I'm guessing it's rather an issue with the canadian cygwin/mingw32 environment (in contrast with the native GNU/Linux in this message). brgds, H-P
