This is the mail archive of the
mailing list for the GCC project.
Re: Problem running the libgomp testsuite
- From: Dodji Seketeli <dodji at seketeli dot org>
- To: JiÅÃ PaleÄek <jpalecek at web dot de>
- Cc: gcc at gcc dot gnu dot org, gcc-help at gcc dot gnu dot org
- Date: Mon, 20 Aug 2012 10:01:20 +0200
- Subject: Re: Problem running the libgomp testsuite
- References: <op.wja5cpxfu2flwt@debian>
I think this question should be directed at firstname.lastname@example.org.
Please send any response to this email there.
JiÅÃ PaleÄek <email@example.com> a Ãcrit:
> I tried to run "make check-c++" from the top directory of the source
Quoted from http://gcc.gnu.org/install/configure.html:
we highly recommend that GCC be built into a separate directory from
the sources which does not reside within the source tree.
> 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?
I guess you should try to use a build directory separate from the
sources and follow closely the instructions on the link above.