From owner-freebsd-java@freebsd.org Mon Jan 29 14:29:03 2018 Return-Path: Delivered-To: freebsd-java@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3DE34ECA173 for ; Mon, 29 Jan 2018 14:29:03 +0000 (UTC) (envelope-from list+org.freebsd.java@io7m.com) Received: from mail.io7m.com (mail.io7m.com [IPv6:2001:19f0:5:752:f000::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.io7m.com", Issuer "arc7 CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E789075FD9; Mon, 29 Jan 2018 14:29:02 +0000 (UTC) (envelope-from list+org.freebsd.java@io7m.com) Received: from copperhead.int.arc7.info (unknown [IPv6:2a02:390:7502:2:0:2:1:0]) by mail.io7m.com (Postfix) with ESMTPSA id 7AB9956F9; Mon, 29 Jan 2018 14:29:01 +0000 (UTC) Date: Mon, 29 Jan 2018 14:28:46 +0000 From: Mark Raynsford Organization: io7m.com OpenPGP: id=B84E17747616C6174C68D5E55C1A7B712812CC05; url=http://io7m.com/pgp/B84E_1774_7616_C617_4C68_D5E5_5C1A_7B71_2812_CC05.key MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/WPUt.dQrt13.ZGmwoe=F_70"; protocol="application/pgp-signature" X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jan 2018 14:29:03 -0000 --Sig_/WPUt.dQrt13.ZGmwoe=F_70 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hello. > As a Java user and developer on FreeBSD, I'd like to inquire how this > change will affect the FreeBSD ports. I'm a Java user and developer, and use Java on FreeBSD (but I don't work on the JDK or the FreeBSD java ports). My understanding is that the work that needs to be done only needs to be done the once: It seems as though someone needs to add new definitions to this file: http://hg.openjdk.java.net/jdk9/jdk9/file/a08cbfc0e4ec/common/autoconf/to= olchain.m4 Otherwise, if you attempt to build the JDK on FreeBSD, the ./configure step will fail complaining that there isn't a valid toolchain on this platform. I don't know if there's more BSD-specific code needed in the JDK, but I'd think that the above would be a one-off change that would apply to all future releases (hopefully the change would get pushed upstream). There's also this repository: http://hg.openjdk.java.net/bsd-port/jdk9/ ... but it doesn't seem like anything is happening there. --=20 Mark Raynsford | http://www.io7m.com --Sig_/WPUt.dQrt13.ZGmwoe=F_70 Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iHUEARYKAB0WIQS4Thd0dhbGF0xo1eVcGntxKBLMBQUCWm8vngAKCRBcGntxKBLM BVw0AP90eGUIdLuQhVqCIhOm5NkAGn5yIvP6tROFlg/ovNEBuwEA9hBDBdWi7duC RfeeaO1DwJoHWLBJlUCGvKrW4CEpYw4= =plkr -----END PGP SIGNATURE----- --Sig_/WPUt.dQrt13.ZGmwoe=F_70--