Bug#792204: gcc-5: FTBFS on sparc64, mismatched symbols files
On 07/12/2015 06:10 PM, John Paul Adrian Glaubitz wrote:
> On 07/12/2015 06:05 PM, John Paul Adrian Glaubitz wrote:
>> Unfortunately, the mail setup on raverin is currently broken which is why
>> it's possible to view the logs without logging in to the machine.
>
> I meant to say "it's *not* possible to view logs without logging in".
I don't think that just removing these symbols on sparc64 as proposed in #777169
is the right way, leaving sparc64 in the same situation as armel (see #727621).
see ./include/std/future
#if defined(_GLIBCXX_HAS_GTHREADS) && defined(_GLIBCXX_USE_C99_STDINT_TR1) \
&& (ATOMIC_INT_LOCK_FREE > 1)
Apparently this doesn't trigger on sparc64, so please find out why not. I assume
ATOMIC_INT_LOCK_FREE is the culprit here.
Reply to: