Re: Running Tests Fails with very Minor Fix

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On 2017-09-30 07:01 PM, Jonathan Wakely wrote:
> On 30 September 2017 at 22:42, nick wrote:
>> Greetings,
>>
>> I tried running the tests with:
>> make bootstrap
>> make -k check
>> and it fails like this:
>> make[5]: Entering directory '/home/nick/gcc/obdjir/x86_64-pc-linux-gnu/32/libatomic'
>> make  all-recursive
>> make[6]: Entering directory '/home/nick/gcc/obdjir/x86_64-pc-linux-gnu/32/libatomic'
>> Making all in testsuite
>> make[7]: Entering directory '/home/nick/gcc/obdjir/x86_64-pc-linux-gnu/32/libatomic/testsuite'
>> make[7]: Nothing to be done for 'all'.
>> make[7]: Leaving directory '/home/nick/gcc/obdjir/x86_64-pc-linux-gnu/32/libatomic/testsuite'
>> make[7]: Entering directory '/home/nick/gcc/obdjir/x86_64-pc-linux-gnu/32/libatomic'
>> true  DO=all multi-do # make
>> make[7]: Leaving directory '/home/nick/gcc/obdjir/x86_64-pc-linux-gnu/32/libatomic'
>> make[6]: Leaving directory '/home/nick/gcc/obdjir/x86_64-pc-linux-gnu/32/libatomic'
>> make[5]: Leaving directory '/home/nick/gcc/obdjir/x86_64-pc-linux-gnu/32/libatomic'
>> make[4]: Leaving directory '/home/nick/gcc/obdjir/x86_64-pc-linux-gnu/libatomic'
>> make[3]: Leaving directory '/home/nick/gcc/obdjir/x86_64-pc-linux-gnu/libatomic'
>> make[2]: Leaving directory '/home/nick/gcc/obdjir/x86_64-pc-linux-gnu/libatomic'
>> make[1]: Target 'check-target' not remade because of errors.
>> make[1]: Leaving directory '/home/nick/gcc/obdjir'
>> Makefile:2292: recipe for target 'do-check' failed
>> make: *** [do-check] Error 2
>> make: Target 'check' not remade because of errors.
> 
> This only says that Make failed because of some earlier error, which
> you didn't show.
> 
>> I have no idea why but I added this very minor fix:
>> error_at (EXPR_LOCATION (call_expr), "cannot tail-call: %s", _(reason));
>>
>> The only odd thing about this build is I am running it through ccache but I have no
>> idea how that would cause issues. Thoughts?
> 
> There's no way we can say why this did or didn't fix an error that you
> didn't show us.
> 
What info do you require. I am just showing you code changes as that's generally a question
asked.

Nick



[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux