From nobody Mon Jul 29 21:10:31 2024 X-Original-To: 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 4WXrcB1pDGz5S0qB for ; Mon, 29 Jul 2024 21:10:34 +0000 (UTC) (envelope-from 0101019100549f03-812be491-ffb7-4868-a5f5-806ab347bfb8-000000@us-west-2.amazonses.com) Received: from a27-187.smtp-out.us-west-2.amazonses.com (a27-187.smtp-out.us-west-2.amazonses.com [54.240.27.187]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 4WXrc90Bwlz4pkC; Mon, 29 Jul 2024 21:10:32 +0000 (UTC) (envelope-from 0101019100549f03-812be491-ffb7-4868-a5f5-806ab347bfb8-000000@us-west-2.amazonses.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=amazonses.com header.s=7v7vs6w47njt4pimodk5mmttbegzsi6n header.b=ge54FBah; dmarc=none; spf=pass (mx1.freebsd.org: domain of 0101019100549f03-812be491-ffb7-4868-a5f5-806ab347bfb8-000000@us-west-2.amazonses.com designates 54.240.27.187 as permitted sender) smtp.mailfrom=0101019100549f03-812be491-ffb7-4868-a5f5-806ab347bfb8-000000@us-west-2.amazonses.com DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=7v7vs6w47njt4pimodk5mmttbegzsi6n; d=amazonses.com; t=1722287431; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From:In-Reply-To:Content-Type:Content-Transfer-Encoding:Feedback-ID; bh=XNw0ulal2OhMiL/vuaGfglaU2hW9cXXhMdNJ3Ijes6A=; b=ge54FBahVxesuAq8ulby/yUagMwjcPLTHt8q2lL+ucIjt5nCXkDv3vfH4Xml/svM BI9YXJ6mXH+vyviyrZcrgt+QipxHdd79VJYe38Iv+bU8ZbCzxlOItUm33GqFrONBdKf tNwX9XyhfU1bwnJfZBmURTWSfbLmwViH/LL2W3yU= X-Authentication-Warning: misty.eyesbeyond.com: Host laptop.eyesbeyond.com [10.0.0.19] claimed to be [10.0.0.19] Message-ID: <0101019100549f03-812be491-ffb7-4868-a5f5-806ab347bfb8-000000@us-west-2.amazonses.com> Date: Mon, 29 Jul 2024 21:10:31 +0000 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 User-Agent: Mozilla Thunderbird Subject: Re: openjdk17/18 fails because of dtrace ? Content-Language: en-GB To: Kurt Jaeger , glewis@freebsd.org Cc: java@freebsd.org References: From: Greg Lewis In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Feedback-ID: ::1.us-west-2.57h2ou5HkLStqinMcFspxvx9Ae9MkLBpzbLgKiDKs1s=:AmazonSES X-SES-Outgoing: 2024.07.29-54.240.27.187 X-Spamd-Bar: / X-Spamd-Result: default: False [0.32 / 15.00]; FORGED_MUA_THUNDERBIRD_MSGID_UNKNOWN(2.50)[]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.992]; FORGED_SENDER(0.30)[glewis@eyesbeyond.com,0101019100549f03-812be491-ffb7-4868-a5f5-806ab347bfb8-000000@us-west-2.amazonses.com]; R_SPF_ALLOW(-0.20)[+ip4:54.240.0.0/18]; R_DKIM_ALLOW(-0.20)[amazonses.com:s=7v7vs6w47njt4pimodk5mmttbegzsi6n]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; MIME_TRACE(0.00)[0:+]; RCVD_IN_DNSWL_NONE(0.00)[54.240.27.187:from]; DWL_DNSWL_NONE(0.00)[amazonses.com:dkim]; ASN(0.00)[asn:16509, ipnet:54.240.24.0/22, country:US]; TO_DN_SOME(0.00)[]; ARC_NA(0.00)[]; DMARC_NA(0.00)[eyesbeyond.com]; RCPT_COUNT_THREE(0.00)[3]; FROM_HAS_DN(0.00)[]; HAS_XAW(0.00)[]; RCVD_COUNT_ZERO(0.00)[0]; FROM_NEQ_ENVFROM(0.00)[glewis@eyesbeyond.com,0101019100549f03-812be491-ffb7-4868-a5f5-806ab347bfb8-000000@us-west-2.amazonses.com]; MLMMJ_DEST(0.00)[java@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[amazonses.com:+] X-Rspamd-Queue-Id: 4WXrc90Bwlz4pkC On 7/24/24 11:37 PM, Kurt Jaeger wrote: > Hi! > >>> When building openjdk17 or 18, it fails very early in the build because >>> >>> dtrace: failed to compile script /wrkdirs/usr/ports/java/openjdk18/work/jdk18u-jdk-18.0.2-9-1/build/bsd-x86_64-server-release/hotspot/variant-server/support/dtrace/hotspot.h.d: "/usr/lib/dtrace/ipfw.d", line 126: syntax error near "in_addr_t" >>> >>> Any ideas how to fix this ? >> --disable-dtrace >> >> in CONFIGURE_ARGS seems to work ? > This is on 14.1-amd64, FYI... > Disabling dtrace in the configuration would definitely work.  I haven't encountered it myself, but I don't usually build on 14.1-amd64. Have you tried this with the latest openjdk17 (committed a couple of days ago)?  Are the package builder machines having the same problem? -- Greg