When building with cross, a container image using Ubuntu 16.04 is being used. This seems to be the cause for creating a binary which will segfault (or run into other such failures) when running on aarch64.
On the other side: Having the other PR might offer a quick way out should this occur on other targets. However, I am not sure it's that likely and worth it.
When building with cross, a container image using Ubuntu 16.04 is being used. This seems to be the cause for creating a binary which will segfault (or run into other such failures) when running on aarch64.
Using Ubuntu 20.04 does not produce this issue.
Also see:
This might be a better way than https://github.com/trustification/trustify/pull/387 … as it doesn't add new code to work around this, but uses the existing, which should work anyway.
On the other side: Having the other PR might offer a quick way out should this occur on other targets. However, I am not sure it's that likely and worth it.