-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Native compilation error with cryptacular 1.2.7 #1648
Comments
I am bit confused what's the problem. Looking at vt-middleware/cryptacular@v1.2.6...v1.2.7 I do not see any change in the signature of |
Hi @ppalaga , you are being hit by oracle/graal#6253 and not getting the actual exception. Reproducing the issue with a build of oracle/graal#9856 I get the following: Logs:
So the issue seems to be caused by vt-middleware/cryptacular@v1.2.6...v1.2.7#diff-79f5fd15734b0c8d16d038017e19d75ec56704f75801b9778021e49fcf7d3876R577 which references |
Great analysis, thanks a lot, @zakkak! |
@zakkak, are you on Linux x64 by any chance and can you share your build of oracle/graal#9856 somehow so that I can continue with fixing this issue? I have added an OperatorCreationException stub as well as all bouncycastle classes referenced in |
Sure. Please note that the link is valid for only one download so please don't click on it if you are not @ppalaga :) |
Thanks again, @zakkak, I was able to run the native compilation with your build of GraalVM
I have added the following options to application.properties to enable the new feature:
However, I do not see any expected NoClassDefFoundException, just the one I see with the regular GraalVM:
Is there anything else I need to do to see the real cause of the issue? |
Hmmm, not sure what's wrong there.
@ppalaga you should now be able to grab and use a dev build from https://github.com/graalvm/graalvm-ce-dev-builds/releases which doesn't require any additional flags (and has oracle/graal#6253 fixed). Can you give it a try and see if it gives a better trace? If not please let me know how to reproduce the issue. |
Steps to reproduce with #1649:
As a workaround, we stay at cryptacular 1.2.6
The text was updated successfully, but these errors were encountered: