This looks like https://bugs.openjdk.java.net/browse/JDK-8237879
Workaround is to get an older version of GNU make (trivial to download
and build yourself) and configure with MAKE=yourmake on the configure
command line.
/Erik
On 2020-02-12 14:15, Ty Young wrote:
Hi,
Attempting to build any JDK version with a supported boot JDK results
in failure:
Building target 'images' in configuration 'linux-x86_64-server-release'
Warning: No SCM configuration present and no .src-rev
make[3]: *** No rule to make target
'/home/ty/Downloads/panama-foreign-linkToNative/build/linux-x86_64-server-release/buildtools/langtools_tools_classes/_the.BUILD_TOOLS_LANGTOOLS.vardeps',
needed by
'/home/ty/Downloads/panama-foreign-linkToNative/build/linux-x86_64-server-release/buildtools/langtools_tools_classes/_the.BUILD_TOOLS_LANGTOOLS_batch'.
Stop.
make[3]: *** Waiting for unfinished jobs....
make[3]: *** No rule to make target
'/home/ty/Downloads/panama-foreign-linkToNative/build/linux-x86_64-server-release/make-support/vardeps/make/ReleaseFile.gmk/create-info-file.vardeps',
needed by
'/home/ty/Downloads/panama-foreign-linkToNative/build/linux-x86_64-server-release/jdk/release'.
Stop.
make[2]: *** [make/Main.gmk:405: release-file] Error 2
make[2]: *** Waiting for unfinished jobs....
make[2]: *** [make/Main.gmk:70: buildtools-langtools] Error 2
make[3]: *** No rule to make target
'/home/ty/Downloads/panama-foreign-linkToNative/build/linux-x86_64-server-release/make-support/vardeps/make/ModuleWrapper.gmk/java.base/ORDERED_CFG_VARIANTS.vardeps',
needed by
'/home/ty/Downloads/panama-foreign-linkToNative/build/linux-x86_64-server-release/support/modules_libs/java.base/jvm.cfg'.
Stop.
make[3]: *** Waiting for unfinished jobs....
make[2]: *** [make/Main.gmk:158: java.base-copy] Error 2
ERROR: Build failed for target 'images' in configuration
'linux-x86_64-server-release' (exit code 2)
The exact commands used to compile are:
"bash configure --disable-warnings-as-errors" and "make images"
This used to work but after an update to *something* it no longer
builds. Given that I use Arch Linux(which uses newer software) it
could just be a bug introduced in some package and might be fixed
soon(TM) but I figure I'd hit up the this list to see if anyone can
confirm this.
