native-image `@argfile` parse failure on Windows with the error `Fatal error: Unsupported OptionOrigin` #4502

imkiva · 2022-04-22T12:17:56Z

Describe the issue

The @argfile option of native-image show Fatal error: Unsupported OptionOrigin: <the arg file>

For example, this command works (in powershell):

native-image '@args.txt'

while these do not

native-image '@.\args.txt'
native-image '@C:\Users\kiva\git\aya-dev\args.txt'

Steps to reproduce the issue

Please include both build steps as well as run steps

git clone --depth 1 https://github.com/aya-prover/aya-dev.git
.\gradlew nativeCompile

note: the args.txt is just copied from Gradle generated argument file, which is introduced in #3734 but I don't know whether this issue is due to native-image or the Gradle plugin, so I posted here (sorry)

Describe GraalVM and your environment:

GraalVM version: https://github.com/graalvm/graalvm-ce-dev-builds/releases/tag/22.2.0-dev-20220421_2218 (the java 17 version)
JDK major version: 17
OS: Windows 10 21H2 (19044.1645)
Architecture: AMD64

More details

Possibly this issue was introduced in #4464

File contents of args.txt and Stack trace: https://gist.github.com/imkiva/3aa4ee72f01df4774ca5c122e9ac4ff5

The text was updated successfully, but these errors were encountered:

oubidar-Abderrahim · 2022-04-27T14:11:35Z

Hi, Thank you for reporting this, we will take a look into it and get back to you

ozkanpakdil · 2022-04-29T18:09:33Z

I am also getting similar error here https://github.com/ozkanpakdil/java-curl/runs/6232783520?check_suite_focus=true
here is how I start mvn https://github.com/ozkanpakdil/java-curl/blob/master/.github/workflows/maven.yml#L27
linux and macos is not failing.

michael-simons · 2022-05-09T14:33:28Z

Same here https://github.com/michael-simons/neo4j-migrations/runs/6349806991?check_suite_focus=true#step:9:247

olpaw · 2022-05-09T14:40:13Z

@michael-simons can you confirm that this issue is windows only?

michael-simons · 2022-05-09T14:41:59Z

Yes I can as stupid me does test the build only on Linux machines https://github.com/michael-simons/neo4j-migrations/runs/6334931402?check_suite_focus=true in contrast to the binaries which I release for windows too.

Here's the concrete line @olpaw https://github.com/michael-simons/neo4j-migrations/runs/6334931402?check_suite_focus=true#step:7:83

This is about addressing oracle/graal#4502 which I discovered after releasing 1.5.5. So this commit is force-pushed onto the main branch and the 1.5.5 tag has been recreated accordingly.

olpaw · 2022-05-10T13:42:17Z

@imkiva thank you for your detailed bug report. The fix for this issue is in #4561

As you already mentioned above, one way to workaround the issue for the already released version 22.1 is to ensure that @argfile-use on Windows does not use complex Windows path strings. E.g. using

native-image @myargfile.txt

works just fine on Windows with 22.1, but to use e.g.

native-image @C:\ADE\OLabs\graal\substratevm\myargfile.txt

the changes from my PR are needed.

imkiva · 2022-05-10T13:48:39Z

@olpaw Thank you for the fix!

…s, however, a graalvm bug prevents a successful compile. See oracle/graal#4561, and oracle/graal#4502. Going to try with maven next.

Version 22.1.0 has a bug on windows. See oracle/graal#4502

Download libs Change graalvm version Version 22.1.0 has a bug on windows. See oracle/graal#4502 Bump version Version Disable windows build Disable windows build until new graalvm is release Added correct dir

Download libs Change graalvm version Version 22.1.0 has a bug on windows. See oracle/graal#4502 Bump version Version Disable windows build Disable windows build until new graalvm is release Added correct dir . Use fixed versions

Currently no Windows support. GraalVM in version 22.1.0 has a bug on windows. See oracle/graal#4502

sysmat · 2022-06-19T15:46:25Z

Same her:

ImageClasspath Entry: org.springframework.experimental:spring-native:jar:0.12.0:compile (file:///C:/Users/tomaz/.m2/repository/org/springframework/experimental/spring-native/0.12.0/spring-native-0.12.0.jar)
ImageClasspath Entry: com.example:si:jar:0.0.1-SNAPSHOT (file:///C:/Users/tomaz/Downloads/si/target/si-0.0.1-SNAPSHOT.jar)
jar:file:///C:/Users/tomaz/Downloads/si/target/si-0.0.1-SNAPSHOT.jar!/META-INF/native-image/org.springframework.aot/spring-aot/native-image.properties does not match recommended META-INF/native-image/${groupId}/${artifactId}/native-image.properties layout.
Downloading: Component catalog from www.graalvm.org
Processing Component: Native Image
Downloading: Component native-image: Native Image from github.com
Installing new component: Native Image (org.graalvm.native-image, version 22.1.0)
Executing: C:\Program Files\Java\graalvm-ce-java17-22.1.0\bin\native-image.cmd @C:\Users\tomaz\AppData\Local\Temp\native-image1565914727584519349args
Fatal error: Unsupported OptionOrigin: C:\Users\tomaz\AppData\Local\Temp\native-image1565914727584519349args

martinformi · 2022-07-20T11:11:50Z

I am following the example ./mvnw package -Dpackaging=native-image from documentation. How can I successfully test this on Windows? I am getting the same Unsupported OptionOrigin exception.

imkiva · 2022-07-20T11:53:12Z

I am following the example ./mvnw package -Dpackaging=native-image from documentation. How can I successfully test this on Windows? I am getting the same Unsupported OptionOrigin exception.

Try the newest dev builds here: https://github.com/graalvm/graalvm-ce-dev-builds/releases

sanshengshui · 2022-11-18T02:31:13Z

upgrade graalvm from 22.1.0 to 22.2.0, fix the above problem! thx

This will include a fix mentioned in oracle/graal#4502 which weseem to be hitting on.

This was a bit of a rabbit hole, but I just went with it. With the changes to sbt-ci-release, _somehow_ the graal native image generation was failing on windows. In order to combat that this pr makes some changes to CI and to the args we're using with Graal. I'll outline the changes below. - Migrate to `graalvm/setup-graalvm` for the graal jobs. This is necessary if we want to use the newer graal versions. When I tried with `setup-scala` I got jabba erros that what I was looking for doesn't exist. Plus `setup-scala` isn't _really_ worked on anymore, so migrating away is preferable. Plus, when using `setup-graalvm` it's easy to get things like the `native-image` command on all platforms. - Bump to 22.3.0. I tried to just bump slightly, but there is a bug in 22.1.0 on windows that I hit on oracle/graal#4502. It's fixed in the newer ones, so I just bumped up. - Use `actions/setup-java` instead of `setup-scala` for jvm tests. Same reason as above with maintenance, but also built-in sbt cache. For now we're still doing a lot on 11 (where the graal stuff is on 17) but I'm trying to not change this too much for now until I get everything green and releasing. Then I'll address that. - Move `publish-binaries-windows` into `publish-binaries`. Now that we are using `setup-graalvm` it's trivial to just keep these together, using `sbt` and just call it a day. No need for two separate ones. - Remove the windows-specific `graalVMNativeImageCommand`. Again, now that we're using `setup-graalvm` we easily have the `native-image` command on the PATH so we don't need to worry about all this extra stuff. - Change a few flags: - `--no-server` wasn't valid it seemed as we were getting a message on every run that it wasn't recognized and ignored. - `-H:EnableUrlProtocols` no just uses `--enable-url-protocols`. Apparently it's frowned upon to use the `-H` stuff since it's internal, so this was just a bit of cleaning up. We do have a couple others, but there doesn't seem to be alternatives so I left them as is. - `--allow-incomlete-classpath` This is the default now, so no need to have it. You can see a green build for all 3 os's [here in my fork](https://github.com/ckipp01/bloop/actions/runs/3787821939/jobs/6439973910). But let's see how all the other jobs go.

imkiva added bug native-image labels Apr 22, 2022

This was referenced Apr 22, 2022

Hello, Aya Native. aya-prover/aya-dev#388

Merged

Aya Native on Windows: serialization config seems broken? aya-prover/aya-dev#394

Closed

oubidar-Abderrahim self-assigned this Apr 27, 2022

sebhoss mentioned this issue May 5, 2022

graal build fails on windows metio/ilo#180

Closed

olpaw added the platform-windows label May 9, 2022

oubidar-Abderrahim assigned olpaw and unassigned oubidar-Abderrahim May 9, 2022

olpaw mentioned this issue May 10, 2022

[GR-38587] Make CommandLineOptionOrigin detection for @argfile-use work for Windows. #4561

Merged

miho mentioned this issue May 10, 2022

Plugin fails to execute nativeBuild task on Windows () graalvm/native-build-tools#232

Closed

graalvmbot closed this as completed in #4561 May 11, 2022

kazuki43zoo mentioned this issue May 29, 2022

Failed compiling on Windows: Unsupported OptionOrigin spring-attic/spring-native#1622

Closed

KevinRoebert added a commit to KevinRoebert/signal-cli that referenced this issue Jun 7, 2022

Change graalvm version

4746fe0

Version 22.1.0 has a bug on windows. See oracle/graal#4502

KevinRoebert mentioned this issue Jun 7, 2022

Native Image CI job AsamK/signal-cli#970

Closed

KevinRoebert added a commit to KevinRoebert/signal-cli that referenced this issue Jun 8, 2022

Native Image CI job

3181ebf

Currently no Windows support. GraalVM in version 22.1.0 has a bug on windows. See oracle/graal#4502

jvalkeal mentioned this issue Aug 4, 2022

Support testing macos/windows oracle/graalvm-reachability-metadata#24

Closed

ckipp01 added a commit to ckipp01/bloop that referenced this issue Dec 27, 2022

try 22.2

d76c348

This will include a fix mentioned in oracle/graal#4502 which weseem to be hitting on.

ckipp01 mentioned this issue Dec 27, 2022

refactor(ci): update graal release infrastructure scalacenter/bloop#1966

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

native-image `@argfile` parse failure on Windows with the error `Fatal error: Unsupported OptionOrigin` #4502

native-image `@argfile` parse failure on Windows with the error `Fatal error: Unsupported OptionOrigin` #4502

imkiva commented Apr 22, 2022 •

edited

Loading

oubidar-Abderrahim commented Apr 27, 2022

ozkanpakdil commented Apr 29, 2022 •

edited

Loading

michael-simons commented May 9, 2022

olpaw commented May 9, 2022

michael-simons commented May 9, 2022 •

edited

Loading

olpaw commented May 10, 2022 •

edited

Loading

imkiva commented May 10, 2022

sysmat commented Jun 19, 2022

martinformi commented Jul 20, 2022

imkiva commented Jul 20, 2022

sanshengshui commented Nov 18, 2022

native-image @argfile parse failure on Windows with the error Fatal error: Unsupported OptionOrigin #4502

native-image @argfile parse failure on Windows with the error Fatal error: Unsupported OptionOrigin #4502

Comments

imkiva commented Apr 22, 2022 • edited Loading

Describe the issue

Steps to reproduce the issue

Describe GraalVM and your environment:

More details

oubidar-Abderrahim commented Apr 27, 2022

ozkanpakdil commented Apr 29, 2022 • edited Loading

michael-simons commented May 9, 2022

olpaw commented May 9, 2022

michael-simons commented May 9, 2022 • edited Loading

olpaw commented May 10, 2022 • edited Loading

imkiva commented May 10, 2022

sysmat commented Jun 19, 2022

martinformi commented Jul 20, 2022

imkiva commented Jul 20, 2022

sanshengshui commented Nov 18, 2022

native-image `@argfile` parse failure on Windows with the error `Fatal error: Unsupported OptionOrigin` #4502

native-image `@argfile` parse failure on Windows with the error `Fatal error: Unsupported OptionOrigin` #4502

imkiva commented Apr 22, 2022 •

edited

Loading

ozkanpakdil commented Apr 29, 2022 •

edited

Loading

michael-simons commented May 9, 2022 •

edited

Loading

olpaw commented May 10, 2022 •

edited

Loading