Skip to content
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

Mandrel 20.3.0.0.Beta1-java11: Could not find agent library native-image-diagnostics-agent #114

Closed
sherl0cks opened this issue Nov 20, 2020 · 5 comments · Fixed by graalvm/mandrel-packaging#79 or #115

Comments

@sherl0cks
Copy link

Building a native image results in:

Error occurred during initialization of VM
Could not find agent library native-image-diagnostics-agent on the library path, with error: libnative-image-diagnostics-agent.so: cannot open shared object file: No such file or directory
Error: Image build request failed with exit status 1

Issue is not present on mandrel 20.2-java11.

@zakkak
Copy link
Collaborator

zakkak commented Nov 20, 2020

Hi @sherl0cks,
Did you use any special flags like -Dquarkus.native.additional-build-args='--trace-object-instantiation=...'?

@sherl0cks
Copy link
Author

@zakkak I did have that one but it broke for a different reason. When removed, I got this error. Here is my current setting:
quarkus.native.additional-build-args=--initialize-at-run-time=java.awt.image.AreaAveragingScaleFilter,-H:DynamicProxyConfigurationFiles=dynamic-proxy.json,-H:ResourceConfigurationFiles=resources-config.json,-H:ReflectionConfigurationFiles=reflection-config.json,--report-unsupported-elements-at-runtime

@zakkak
Copy link
Collaborator

zakkak commented Nov 20, 2020 via email

@sherl0cks
Copy link
Author

K will try without it and report back. Thanks for the quick replies @zakkak

@sherl0cks
Copy link
Author

sherl0cks commented Nov 21, 2020

OK so removing --report-unsupported-elements-at-runtime gets the image to build, but I still have AWT issues at runtime as described in graalvm/mandrel#180. For now, leaving this issue open because it does seem to be a regression from 20.2 where --report-unsupported-elements-at-runtime works fine.

matthyx pushed a commit to matthyx/quarkus-images that referenced this issue Sep 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants