GCC 5.1 and sanitizer issue

Jonathan Wakely jwakely.gcc@gmail.com
Tue Jun 9 10:36:00 GMT 2015


On 9 June 2015 at 10:27, Millad Ghane <millad.mg@gmail.com> wrote:
> Hi Jonathan,
>
> Thanks for your consideration.
>
>
> GCC: current gcc
> ==============
> Simple answer: 4.4.7
> Full answer:
> ----------------
> Using built-in specs.
> Target: x86_64-redhat-linux

Then building GCC 5.1 should work fine, that's strange.

> Right now, I think I have overcome above issue. But, a new issue comes
> up. It is shown in here. It seems the issue is about LibGOMP (which I
> need it).
> =====================
> ...
> checking for C compiler default output file name... a.out
> checking whether the C compiler works... configure: error: in
> `/home/sarood1/millad/gcc-build/x86_64-unknown-linux-gnu/libgomp':
> configure: error: cannot run C compiled programs.
> If you meant to cross compile, use `--host'.
> See `config.log' for more details.
> make[1]: *** [configure-target-libgomp] Error 1
> make[1]: Leaving directory `/home/sarood1/millad/gcc-build'
> make: *** [all] Error 2

You can look in gcc-build/x86_64-unknown-linux-gnu/libgomp/config.log
to see the error that causes the "cannot run C compiled programs"
problem.



More information about the Gcc-help mailing list