Date: Wed, 19 Mar 2025 10:24:25 +0100 From: Harald Eilertsen <haraldei@anduin.net> To: freebsd-java@freebsd.org Subject: Re: java/openjdk19 fails to build on aarch64 Message-ID: <v3b7eyic52f4u2tebsksunsx53hcdldeo23n7kkat2fyavb3ny@oyaxpgtikpq6> In-Reply-To: <82f3dead-8438-4ecb-91d4-ccc486c72c3f@chen.org.nz> References: <4dda4c06-fc1c-40e0-9960-048c9c776125@chen.org.nz> <iex7bu3ac3zrotj54uhslayrf7alib2wynwfj6avzgbrpbk4y6@xjvmygqra6nr> <82f3dead-8438-4ecb-91d4-ccc486c72c3f@chen.org.nz>
index | next in thread | previous in thread | raw e-mail
On Wed, Mar 19, 2025 at 07:27:00PM +1300, Jonathan Chen wrote: > 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. libraries.m4 should be patched before configure is run, which again produces spec.gmk. Otherwise it would be no point in patching it to begin with... Could it be that you already had a configuration, so the patch was applied, but the configure step skipped? -- Haraldhelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?v3b7eyic52f4u2tebsksunsx53hcdldeo23n7kkat2fyavb3ny>