Closed exquo closed 1 year ago
Probably have a look here: https://github.com/signalapp/libsignal/issues/481
Thanks, yes, I have used the advice from https://github.com/signalapp/libsignal/issues/481#issuecomment-1220904129. Following it, the builds succeed for the aarch64-linux-gnu
and i686-linux-gnu
targets. However, for armv7-linux-gnueabihf
it still fails..
The QEMU approach discussed there is apparently viable. But it's a very different path from a straightforward cross-compilation. I would like to try resolve this without using emulation, since Rust should be "cross-compilation native".
Any updates on this ?
I've added a pull request to upstream boring ssl. Should be in the next libsignal release: https://github.com/signalapp/libsignal/labels/awaiting%20release
Thanks @morph027!
I'll close this issue when the workflow automatically builds everything successfully on picking up the next upstream release.
In the meantime, I'll try to also add the armv7
build object to the current release.
Do you have a release?
I currently added the older 0.18.1 version to the 0.21.1 jar file. seems to work, at least for sending
2 things for the documentation I have a raspberry 4 and it uses arm7 platform (not aarch like described in the readme) to get the old version into the jar file, use zip command WITHOUT u parameter
You can try the artifact from https://gitlab.com/packaging/libsignal-client/-/issues/2#note_1224620739
Thank you very much @morph027 for submitting the fix upstream! With it the new releases build for ARMv7 target again!
I've also ran a workflow that added the armv7-unknown-linux-gnueabihf
file to the v0.21.1 release.
After the BoringSSL lib has been added as a dependency of
libsignal
, cross-compiling the latter fails for targetarmv7-linux-gnueabihf
: https://github.com/exquo/signal-libs-build/actions/runs/3411284904/jobs/5675310584However, building the
boring
library itself for the same target in the same environment succeeds.. https://github.com/exquo/signal-libs-build/actions/runs/3411698940/jobs/5676237923Asked upstream: https://github.com/signalapp/libsignal/issues/481#issuecomment-1306017143