Unable to start presto-cli on ppc64le and ARM

[helix-loop]

After successfully starting presto server I am not able to start presto-cli from CLI install.

Trying to build presto from source with ./mvnw clean install -DskipTests succeeds after various dependencies not mentioned in the build requirements are installed.

However starting the built version of presto-cli with ./presto-cli-0.269-SNAPSHOT-executable.jar --server localhost:8080 --catalog hive --schema default results in the following

Exception in thread "main" java.lang.UnsatisfiedLinkError: Could not load library. Reasons: [no jansi64-0.269-SNAPSHOT-ce338f0 in java.library.path: [/usr/java/packages/lib, /usr/lib/powerpc64le-linux-gnu/jni, /lib/powerpc64le-linux-gnu, /usr/lib/powerpc64le-linux-gnu, /usr/lib/jni, /lib, /usr/lib], no jansi-0.269-SNAPSHOT-ce338f0 in java.library.path: [/usr/java/packages/lib, /usr/lib/powerpc64le-linux-gnu/jni, /lib/powerpc64le-linux-gnu, /usr/lib/powerpc64le-linux-gnu, /usr/lib/jni, /lib, /usr/lib], no jansi in java.library.path: [/usr/java/packages/lib, /usr/lib/powerpc64le-linux-gnu/jni, /lib/powerpc64le-linux-gnu, /usr/lib/powerpc64le-linux-gnu, /usr/lib/jni, /lib, /usr/lib], /tmp/libjansi-64-0-13026983343810661197.269-SNAPSHOT-ce338f0: /tmp/libjansi-64-0-13026983343810661197.269-SNAPSHOT-ce338f0: cannot open shared object file: No such file or directory (Possible cause: can't load AMD 64-bit .so on a Power PC 64 LE-bit platform)]
	at org.fusesource.hawtjni.runtime.Library.doLoad(Library.java:182)
	at org.fusesource.hawtjni.runtime.Library.load(Library.java:140)
	at org.fusesource.jansi.internal.CLibrary.<clinit>(CLibrary.java:42)
	at org.fusesource.jansi.AnsiConsole.wrapOutputStream(AnsiConsole.java:48)
	at org.fusesource.jansi.AnsiConsole.<clinit>(AnsiConsole.java:38)
	at com.facebook.presto.cli.Console.run(Console.java:91)
	at com.facebook.presto.cli.Presto.main(Presto.java:31)

There is already an issue from 2020 with the same error and a possible "workaround" (#14546), but it is closed without a proper solution as far as I can see. However the following issue seems to me like the same issue but with a M1 aarch64 architecture on macOS. #17146

What are possible solutions for both errors and how can the source of the issue be located?

OS / architecture
Debian 11 Bullseye / pcc64le

Version
0.269-SNAPSHOT