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

Couldn't determine GraalVM version #1232

Open
westinyang opened this issue Sep 21, 2023 · 10 comments
Open

Couldn't determine GraalVM version #1232

westinyang opened this issue Sep 21, 2023 · 10 comments
Labels
bug Something isn't working

Comments

@westinyang
Copy link

westinyang commented Sep 21, 2023

I just made a try with graalvm 21. I did not work

java.io.IOException: Couldn't determine GraalVM version
	at com.gluonhq.substrate.model.InternalProjectConfiguration.getGraalVersion(InternalProjectConfiguration.java:139)

java -version

java version "21" 2023-09-19
Java(TM) SE Runtime Environment Oracle GraalVM 21+35.1 (build 21+35-jvmci-23.1-b15)
Java HotSpot(TM) 64-Bit Server VM Oracle GraalVM 21+35.1 (build 21+35-jvmci-23.1-b15, mixed mode, sharing)

Same problem: gluonhq/gluonfx-maven-plugin#489

@westinyang westinyang added the bug Something isn't working label Sep 21, 2023
@SaptarshiSarkar12
Copy link

SaptarshiSarkar12 commented Sep 21, 2023

I am also facing the same issue.

@Anivie
Copy link

Anivie commented Sep 22, 2023

I am find a possible cause is that the regular expression in the fileInternalProjectConfiguration.java was unable to match the new release:

java version "21" 2023-09-19
Java(TM) SE Runtime Environment Oracle GraalVM 21+35.1 (build 21+35-jvmci-23.1-b15)
Java HotSpot(TM) 64-Bit Server VM Oracle GraalVM 21+35.1 (build 21+35-jvmci-23.1-b15, mixed mode, sharing)

@SaptarshiSarkar12
Copy link

@Anivie Yes, the regex does not seem to match the latest version.

@credmond
Copy link

Can I ask a question... Anytime I attempt anything other than Gluon's GraalVM build, I get various errors. I always give up in the end. I find substrate would need updates, etc, or there's some other obscure error.

How are you guys getting later GraalVM builds working (apart from 21, which I know is causing you issues)...?

@SaptarshiSarkar12
Copy link

@credmond I have used some configuration in pom.xml file for my Drifty project (A JavaFX app).
I am using GitHub Actions to build Drifty for Windows, macOS and Linux. You can check this workflow file for your reference.
The workflow automatically sets up Maven version 3.8.8 and installs all the required tools.

@SaptarshiSarkar12
Copy link

Let me know if you want to know anything else.

@credmond
Copy link

credmond commented Oct 28, 2023

Thanks. I think what you're doing with missing_symbols.c is key! But you're also setting a lot of other arguments, I will figure out what they're doing and apply to my own... Thank you, this is a good resource!

@SaptarshiSarkar12
Copy link

@credmond Yes, the C file solved some unknown missing method/class failures for windows build, in my case.
Happy to help you 😄!
Thank you!

@kristofdho
Copy link
Contributor

As a workaround you can use GraalVM 21.0.1 which was released 2 weeks ago and doesn't trigger the version issue.
A caveat though, we're running into an issue where the HomeFinderFeature is not found because substrate adds it to the configuration. I'm having trouble figuring out why this is required in the first place.

protected static final List<String> ENABLED_FEATURES =
new ArrayList<>(Arrays.asList("org.graalvm.home.HomeFinderFeature"));

@kkriske
Copy link
Contributor

kkriske commented Nov 11, 2023

I've added a PR to fix the aforementioned additional issues with the HomeFinderFeature, and some additional linker issues on Windows: #1236

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

6 participants