From nobody Wed Mar 19 07:18:49 2025 X-Original-To: freebsd-java@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4ZHg722rhHz5qjnm for ; Wed, 19 Mar 2025 07:18:54 +0000 (UTC) (envelope-from SRS0=Cl8V=WG=klop.ws=ronald-lists@realworks.nl) Received: from smtp-relay-int.realworks.nl (smtp-relay-int.realworks.nl [194.109.157.24]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4ZHg720dsHz3WXv for ; Wed, 19 Mar 2025 07:18:54 +0000 (UTC) (envelope-from SRS0=Cl8V=WG=klop.ws=ronald-lists@realworks.nl) Authentication-Results: mx1.freebsd.org; none Date: Wed, 19 Mar 2025 08:18:49 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=klop.ws; s=rw2; t=1742368731; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to; bh=q/c3s+5DEZqOR+mrW6u0HUbA5aYOIaVWH36/f9AnAuc=; b=ksfg5K2qNPvNJzuNlkdQ3drmmTsQczOpTR15Z/qJlE+4TSBoiz6qjoy1UXvZMRsOvVkRgi KGK4YJhxh5l5WgoaBFlcMs55G79kYuJvxA3R5sPgnoe6d2+yio7bc+dIRfrTClkrkf3nse iIMhcC630yPh8KzKNdmS7EWgRIc9R3ZBW2Yrm1rp6ymdu2fS3qHcEIYMbvhUjZhtbqYl4y fDsTPZlW7p+Tr8DqMcxrxA0sAISoAw4KcsHtRuQwP5pW4XYe5z2CndQIu3tCMdD9yC5kog eX1rVVX9pi2CpOsajCsR/8600E5GqLXrewYJ3vKHZtgw+qfogFpX+SAdoQOeOA== From: Ronald Klop To: Jonathan Chen Cc: freebsd-java@freebsd.org Message-ID: <676433057.896.1742368729995@localhost> In-Reply-To: <82f3dead-8438-4ecb-91d4-ccc486c72c3f@chen.org.nz> Subject: Re: java/openjdk19 fails to build on aarch64 List-Id: Porting Java to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-java List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-java@FreeBSD.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_895_757565974.1742368729992" X-Mailer: Realworks (742.22) Importance: Normal X-Priority: 3 (Normal) X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:3265, ipnet:194.109.0.0/16, country:NL] X-Rspamd-Queue-Id: 4ZHg720dsHz3WXv X-Spamd-Bar: ---- ------=_Part_895_757565974.1742368729992 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Van: Jonathan Chen Datum: 19 maart 2025 07:27 Aan: freebsd-java@freebsd.org Onderwerp: Re: java/openjdk19 fails to build on aarch64 >=20 >=20 > On 18/03/25 01:15, Harald Eilertsen wrote: > > On Mon, Mar 17, 2025 at 04:41:13PM +1300, Jonathan Chen wrote: > >> =3D=3D=3D> Building for openjdk19-19.0.2+7.1_1 > >> Error: The configuration is not up to date for 'bsd-aarch64-server-rel= ease'. > >=20 > > Check /usr/ports/openjdk19/work/jdk19u-jdk-19.0.2-7-1/build/bsd-aarch64= -server-release/configure.log > >=20 > > To see if the configure step completes, and if not, what causes it to > > fail. >=20 > I've compared the configure.log+spec.gmk on aarch64 against amd64, and ha= ven't noted anything unusual. However, on my aarch64 system, gmake notices = that the files in make/autoconf are newer than build/bsd-aarch64-server-rel= ease/spec.gmk and this triggers the failure. To be fair, this is true, as l= ibraries.m4 has been patched. I do not know why this does not occur on amd6= 4. >=20 > I've forced the build to ignore the autoconf check, and this allows the b= uild to complete. >=20 > Cheers. > --=20 > Jonathan Chen=20 >=20 >=20 >=20 >=20 >=20 >=20 How did you enforce this? I could commit the =E2=80=9Cfix=E2=80=9D if it is= trivial. Regards, Ronald ------=_Part_895_757565974.1742368729992 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable

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:
>> =3D=3D=3D>  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-aarch6= 4-server-release/configure.log
>
> To see if the configure step completes, and if not, what causes it to<= br> > fail.

I've compared the configure.log+spec.gmk on aarch64 against amd64, and have= n't noted anything unusual. However, on my aarch64 system, gmake notices th= at the files in make/autoconf are newer than build/bsd-aarch64-server-relea= se/spec.gmk and this triggers the failure. To be fair, this is true, as lib= raries.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 bui= ld to complete.

Cheers.
-- 
Jonathan Chen




How did you enforce this? I could commit the =E2=80=9C= fix=E2=80=9D if it is trivial.

Regards,
Ronald=

------=_Part_895_757565974.1742368729992--