Date: Wed, 19 Mar 2025 08:18:49 +0100 (CET) From: Ronald Klop <ronald-lists@klop.ws> To: Jonathan Chen <jonc@chen.org.nz> Cc: freebsd-java@freebsd.org Subject: Re: java/openjdk19 fails to build on aarch64 Message-ID: <676433057.896.1742368729995@localhost> In-Reply-To: <82f3dead-8438-4ecb-91d4-ccc486c72c3f@chen.org.nz>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] Van: Jonathan Chen <jonc@chen.org.nz> Datum: 19 maart 2025 07:27 Aan: freebsd-java@freebsd.org Onderwerp: Re: java/openjdk19 fails to build on aarch64 > > > 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 > > > > > > How did you enforce this? I could commit the “fix” if it is trivial. Regards, Ronald [-- Attachment #2 --] <html><head></head><body><br><p><small><strong>Van:</strong> Jonathan Chen <jonc@chen.org.nz><br><strong>Datum:</strong> 19 maart 2025 07:27<br><strong>Aan:</strong> freebsd-java@freebsd.org<br><strong>Onderwerp:</strong> Re: java/openjdk19 fails to build on aarch64<br></small></p><blockquote style="margin-left: 5px; border-left: 3px solid #ccc; margin-right: 0px; padding-left: 5px;"><div class="MessageRFC822Viewer do_not_remove" id="P"><!-- P --> <!-- processMimeMessage --><div class="TextPlainViewer do_not_remove" id="P.P"><!-- P.P -->On 18/03/25 01:15, Harald Eilertsen wrote:<br> > On Mon, Mar 17, 2025 at 04:41:13PM +1300, Jonathan Chen wrote:<br> >> ===> Building for openjdk19-19.0.2+7.1_1<br> >> Error: The configuration is not up to date for 'bsd-aarch64-server-release'.<br> > <br> > Check /usr/ports/openjdk19/work/jdk19u-jdk-19.0.2-7-1/build/bsd-aarch64-server-release/configure.log<br> > <br> > To see if the configure step completes, and if not, what causes it to<br> > fail.<br> <br> 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.<br> <br> I've forced the build to ignore the autoconf check, and this allows the build to complete.<br> <br> Cheers.<br> -- <br> Jonathan Chen <jonc@chen.org.nz><br> <br> <br> </jonc@chen.org.nz></div><!-- TextPlainViewer --> <hr> </div><!-- MessageRFC822Viewer --> </blockquote><br><br>How did you enforce this? I could commit the “fix” if it is trivial.<div><br></div><div>Regards,</div><div>Ronald<br><br></div></body></html>help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?676433057.896.1742368729995>