Currently, when building on debian, there are a few things missing in the package linked to GraalVM, leading to these errors while launching LSC with java >=11:
[To redirect Truffle log output to a file use one of the following options:
* '--log.file=<path>' if the option is passed using a guest language launcher.
* '-Dpolyglot.log.file=<path>' if the option is passed using the host Java launcher.
* Configure logging using the polyglot embedding API.]
[engine] WARNING: The polyglot context is using an implementation that does not support runtime compilation.
The guest application code will therefore be executed in interpreted mode only.
Execution only in interpreted mode will strongly impact the guest application performance.
For more information on using GraalVM see https://www.graalvm.org/java/quickstart/.
To disable this warning the '--engine.WarnInterpreterOnly=false' option or use the '-Dpolyglot.engine.WarnInterpreterOnly=false' system property.
The solution has already been found and deployed in the maven tests, it must now be adapted for the packages.
To sum up:
adding a compiler directory (in /usr/lib/lsc-compiler?)
deploy these 4 files in lsc-compiler: compiler.jar compiler-management.jar graal-sdk.jar truffle-api.jar
add the following options in bin/lsc, but only for JDK >=11: (check the usefulness of each option in a production environment first)
Currently, when building on debian, there are a few things missing in the package linked to GraalVM, leading to these errors while launching LSC with java >=11:
The solution has already been found and deployed in the maven tests, it must now be adapted for the packages.
To sum up:
compiler.jar compiler-management.jar graal-sdk.jar truffle-api.jar