Bug#939687: clazy: FTBFS on armel: undefined reference to symbol '__atomic_load_4@@LIBATOMIC_1.0'

To: Paul Gevers <elbrus@debian.org>, 939687@bugs.debian.org
Subject: Bug#939687: clazy: FTBFS on armel: undefined reference to symbol '__atomic_load_4@@LIBATOMIC_1.0'
From: Lisandro Damián Nicanor Pérez Meyer <perezmeyer@gmail.com>
Date: Thu, 12 Sep 2019 11:59:54 -0300
Message-id: <[🔎] 20190912145954.kyn3dqriqvk3h2ee@tonks>
Reply-to: Lisandro Damián Nicanor Pérez Meyer <perezmeyer@gmail.com>, 939687@bugs.debian.org
In-reply-to: <[🔎] 156788273794.4838.7802908507993552330.reportbug@testavoira.marsaxlokk.dhcp.io>
References: <[🔎] 156788273794.4838.7802908507993552330.reportbug@testavoira.marsaxlokk.dhcp.io> <[🔎] 156788273794.4838.7802908507993552330.reportbug@testavoira.marsaxlokk.dhcp.io>

On 19/09/07 08:58, Paul Gevers wrote:
> Source: clazy
> Version: 1.5-1
> Severity: serious
> Tags: ftbfs
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> 
> Dear maintainer,
> 
> During a binNMU of clazy during the llvm-defaults transition, you package FTBFS
> on armel. Can you please check and fix the situation?

This seems more a bug in the toolchain than anything else. I'm currently trying it on a porterbox.

Reply to:

References:
- Bug#939687: clazy: FTBFS on armel: undefined reference to symbol '__atomic_load_4@@LIBATOMIC_1.0'
  - From: Paul Gevers <elbrus@debian.org>

Prev by Date: Processing of qtcreator_4.10.0-2_source.changes
Next by Date: qtcreator_4.10.0-2_source.changes ACCEPTED into unstable
Previous by thread: Bug#939687: clazy: FTBFS on armel: undefined reference to symbol '__atomic_load_4@@LIBATOMIC_1.0'
Next by thread: Bug#939687: Help needed
Index(es):
- Date
- Thread