Re: armel-specific Rust build failure: atomic builtins clashing

[Sascha Steinbiss <satta@debian.org>]

Hi Adrian,

[...]
>> I think the clashing symbols might be emitted indirectly by the Rust
>> compiler in libsuricata.a (as libsuricata.a is just the artifact for the
>> part of Suricata written in Rust) and will only cause a clash when
>> trying to link the Rust code with the rest of the Suricata C code (as
>> libgcc provides these as well).
>
> I do remember that we explicitly undefined the atomic functions for armel
> in the rustc package because we were running into the same problem.

I see.

> I have to look up what we did back then. It must be in the rustc source
> package.

I would be glad if you could do that. You were also the one filing that
GitHub issue I referenced ;)
Not sure if it is as related as I might think it is, though...

Many thanks
Sascha