You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had a working environment with client-maven-plugin 0.1.30 and GraalVM 20.2.0 - until my application got more complex and now linking fails only on Android, while Linux is still linking fine. It fails on my local Fedora 32 machine, as well on the Ubuntu in Github Actions. It fails with GraalVM 20.2 as well as 20.3-dev (from today)
The output is
[Di. Sep. 22 21:41:07 MESZ 2020][INFO] ==================== LINK TASK ====================
Download progress: 0,06 / 0,06M
[Di. Sep. 22 21:41:09 MESZ 2020][INFO] [SUB] /home/prelle/.gluon/substrate/Android/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/bin/../lib/gcc/aarch64-linux-android/4.9.x/../../../../aarch64-linux-android/bin/ld.gold: error: /home/prelle/git/Mondtor/target/client/aarch64-android/gvm/lib/libsnappyjava.a:1:1: invalid character
[Di. Sep. 22 21:41:10 MESZ 2020][INFO] [SUB] clang: error: linker command failed with exit code 1 (use -v to see invocation)
[Di. Sep. 22 21:41:10 MESZ 2020][SEVERE] Process link failed with result: 1
The full linker command line (according to the log) is:
Client plugin 0.1.32 - which I seem to have missed - works like a charm. From what I see from the logs, it doesn't try to link with libsnappyjava anymore.
I had a working environment with client-maven-plugin 0.1.30 and GraalVM 20.2.0 - until my application got more complex and now linking fails only on Android, while Linux is still linking fine. It fails on my local Fedora 32 machine, as well on the Ubuntu in Github Actions. It fails with GraalVM 20.2 as well as 20.3-dev (from today)
The output is
The full linker command line (according to the log) is:
The static archive in question (libsnappyjava.a) does not seem to be a regular "ar archive"
libsnappy seems to be android-related. It seems, that the different library format of libsnappy.a is a problem, but I don't know how to deal with it.
The text was updated successfully, but these errors were encountered: