Date: Wed, 19 Mar 2025 19:27:00 +1300 From: Jonathan Chen <jonc@chen.org.nz> To: freebsd-java@freebsd.org Subject: Re: java/openjdk19 fails to build on aarch64 Message-ID: <82f3dead-8438-4ecb-91d4-ccc486c72c3f@chen.org.nz> In-Reply-To: <iex7bu3ac3zrotj54uhslayrf7alib2wynwfj6avzgbrpbk4y6@xjvmygqra6nr> References: <4dda4c06-fc1c-40e0-9960-048c9c776125@chen.org.nz> <iex7bu3ac3zrotj54uhslayrf7alib2wynwfj6avzgbrpbk4y6@xjvmygqra6nr>
index | next in thread | previous in thread | raw e-mail
On 18/03/25 01:15, Harald Eilertsen wrote: > On Mon, Mar 17, 2025 at 04:41:13PM +1300, Jonathan Chen wrote: >> ===> Building for openjdk19-19.0.2+7.1_1 >> Error: The configuration is not up to date for 'bsd-aarch64-server-release'. > > Check /usr/ports/openjdk19/work/jdk19u-jdk-19.0.2-7-1/build/bsd-aarch64-server-release/configure.log > > To see if the configure step completes, and if not, what causes it to > fail. I've compared the configure.log+spec.gmk on aarch64 against amd64, and haven't noted anything unusual. However, on my aarch64 system, gmake notices that the files in make/autoconf are newer than build/bsd-aarch64-server-release/spec.gmk and this triggers the failure. To be fair, this is true, as libraries.m4 has been patched. I do not know why this does not occur on amd64. I've forced the build to ignore the autoconf check, and this allows the build to complete. Cheers. -- Jonathan Chen <jonc@chen.org.nz>help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?82f3dead-8438-4ecb-91d4-ccc486c72c3f>