Re: armel-specific Rust build failure: atomic builtins clashing
On 11/1/19 1:44 PM, Sascha Steinbiss wrote:
> Hmm. I don't see any explicit definition of, say, __sync_fetch_and_add
> in Suricata code. It is used in a wrapper somewhere, but not defined :/
> In the case of the problematic __sync_val_compare_and_swap_4, for
> example, it is never seen in the Suricata code at all.
>
> 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 have to look up what we did back then. It must be in the rustc source
package.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Reply to: