-
Notifications
You must be signed in to change notification settings - Fork 19
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
Build failure: unsupported features; unbalanced monitors #15
Comments
Hey @aviflax thanks for dropping by! The unbalanced monitor issue is due to I should have some time soon to check out your project and see if I can get it building. Looks like maybe some stuff related to reflection? I can't make Clojure Conj this year but hope to soon! |
Wow thanks @taylorwood for the super-rapid and super-helpful response! That hacky workaround looks pretty good actually! I’m a little more intimidated by the situation with Thank you! |
Update: I’ve implemented the hacky workaround from Clojurl to work around the issue with the Now I’m getting Verbose Output
This is from https://github.com/FundingCircle/fc4-framework/commit/f76b856314d480cf68692f61a08e8934fee663c3 which is currently HEAD of |
Update: I perused oracle/graal#1074 and then added Now I’m getting Verbose Output
|
I was able to build your branch with Clojure 1.10.1 on the GraalVM 19.2.1 Docker image:
The only change I had to make was |
Taylor, thank you so much! I’ll revisit this and pick it back up from where you left it, hopefully in a few weeks. Thanks! 🤗 |
@aviflax I got similar-looking errors but only after trying commits after (and including) b3823a4 -- I also tried
In my case, builds are successful up through commit 7773c73 -- here I had |
I failed to mention that what I tried with was a separate project. Sorry for any confusion. |
I just tried building FundingCircle/fc4-framework@ 36aad75491a7c08b2b5db932b6749a69baa71e23 (tip of native-image branch) -- but I get:
|
Upgrading my clj / clojure to the latest version (1.10.1.492) seems to have addressed this issue (thanks @seancorfield). I have a running native image binary of fc4 that doesn't crash on startup now, @aviflax :) Things I did to get this running (a Linux distribution, fwiw):
Not quite there yet though, as I get:
Adding a reflection.json file with appropriate content (and adding |
This exception at runtime has me stumped:
FWIW, the reflection.json file is zipped below: |
@sogaiu - did you ever find a solution for this ? I'm running into a similar error using graal and a file watcher library. I'm trying to setup my reflection file to include the java.nio.file.StandardWatchEventKinds$StdWatchEventKind[] but haven't had much luck. |
@teesloane I don't think I did. My recommendation is to ask on clojurians slack #graalvm channel about your specific situation. |
@sogaiu will do, thanks! edit: solution was to add this to my reflection file:
|
👋 hi @taylorwood, I hope you don’t mind me dropping another general “I have no idea what I’m doing” issue on you. Given that it’s been almost exactly a year since my last attempt (#2) I wanted to try again to create a native image of my project. I didn’t get very far and I don’t really understand the error output, so I’m hoping you might have a few minutes to point me in the right direction.
I’m running MacOS 10.14.5 and I’m using GraalVM CE 19.2.1 and native-image 19.2.1.
Here’s the profile I added to my
deps.edn
:and here’s the output when I run
clojure -A:native-image
:output
My guess is that you could walk me through fixing the “unsupported features” but that last error, the “unbalanced monitors” error — that looks familiar, IIRC that’s related to some incompatibility between GraalVM/native-image and certain code paths in the Clojure runtime… which might be non-work-around-able? If that’s the case, if we’re stuck, then there’s no need to resolve the other errors… but I’d appreciate whatever pointers you’d care to share!
If it helps, feel free to take a look at my branch of my project with that profile added.
(Also, if you’ll be at the Conj next month in Raleigh, I’ll be there too and I’d love to catch up!)
The text was updated successfully, but these errors were encountered: