I have a weird problem. I am attempting to update gradle for building C++ gcc stuff on linux aarch64. I have played with both HEAD and 8.7.0 (because that is our production version). Both have the same problem. When I build the gradle bin.zip on the aarch64 machine, I get weird errors in normal configuration phase of gradle. This has zero to do with my changes. If I do the same 8.7.0 build on my intel linux machine and push it to the aarch64 machine, same weird configuration errors. However, configuration phase works just fine if I pull 8.7 from gradle.org repository. (Yes, I was cleaning out ~/.gradle/wrapper/dists when moving .zip file around.) What might be different in the gradle.org repository's build? Is there a specific java flavor that creates the build?

What is “push to aarch64”, that sounds atypical. Generally you’d check out the same repo on each machine, run ‘./gradlew’ which downloads/installs/executes Gradle.

"Push" is related to me making changes to gradle itself, not using it for building another project. I am struggling with a local build of gradle that is having weird problems only on the aarch64 linux. I tried to isolate the issue by building gradle on both intel and aarch64 platforms, then copying the bin.zip to the other machine. My builds of gradle on intel and aarch64 fail on execution only on aarch64. Both builds work fine on intel. Again, I did clean ~/.gradle/wrapper/dist to ensure replacement bin.zip used. Only the bin.zip that downloads from gradle.org works correctly. Hence my question about details of how it is built ... so that maybe I can duplicate and use locally.