hhoffstaette commented on issue #1029:
URL: https://github.com/apache/maven-mvnd/issues/1029#issuecomment-2180607908
I tested the binary from the CI run and it works. 🙌
x86-64-v2 would have been fine too but whatever; thank you very much! ❤️
--
This is an automated message from the
cstamas commented on issue #1029:
URL: https://github.com/apache/maven-mvnd/issues/1029#issuecomment-2180579187
Please retest with binaries built by CI from here:
https://github.com/apache/maven-mvnd/actions/runs/9597334445
--
This is an automated message from the Apache Git Service.
To
cstamas commented on issue #1029:
URL: https://github.com/apache/maven-mvnd/issues/1029#issuecomment-2176759313
To reproduce, use mvnd-1.x branch and I had these changes (yes, I also
enabled FFM, so it may affected it):
```diff
diff --git a/client/pom.xml b/client/pom.xml
index ba94
hhoffstaette commented on issue #1029:
URL: https://github.com/apache/maven-mvnd/issues/1029#issuecomment-2176742791
> Tried several `-march` options on Fedora 40 with
That doesn't look right..neither compatibility nor v1/v2 should use e.g.
AVX2 or AVX512.
But thanks for taking a l
cstamas commented on issue #1029:
URL: https://github.com/apache/maven-mvnd/issues/1029#issuecomment-2176725966
Tried several `-march` options on Fedora 40 with
```
openjdk version "22.0.1" 2024-04-16
OpenJDK Runtime Environment GraalVM CE 22.0.1+8.1 (build 22.0.1+8-jvmci-b01)
Ope
gnodet commented on issue #1029:
URL: https://github.com/apache/maven-mvnd/issues/1029#issuecomment-2175268475
As a workaround, one can export the env variable`MVND_CLIENT=jvm` to bypass
the native client.
--
This is an automated message from the Apache Git Service.
To respond to the mess
mthmulders commented on issue #1029:
URL: https://github.com/apache/maven-mvnd/issues/1029#issuecomment-2174306317
I remember having seen a similar issue in one of my pet projects. I remember
adding `-march=compatibility` to the build flags fixed it. See [`native-image`
build
options](http
