From owner-freebsd-java@freebsd.org Tue Jul 9 03:53:47 2019 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 9E23F15CD8DE for ; Tue, 9 Jul 2019 03:53:47 +0000 (UTC) (envelope-from glewis@eyesbeyond.com) Received: from misty.eyesbeyond.com (gerbercreations.com [71.39.140.16]) by mx1.freebsd.org (Postfix) with ESMTP id 0DD7274318 for ; Tue, 9 Jul 2019 03:53:44 +0000 (UTC) (envelope-from glewis@eyesbeyond.com) Received: from misty.eyesbeyond.com (localhost.eyesbeyond.com [127.0.0.1]) by misty.eyesbeyond.com (8.15.2/8.15.2) with ESMTP id x693rAxv086094; Mon, 8 Jul 2019 20:53:11 -0700 (PDT) (envelope-from glewis@eyesbeyond.com) Received: (from glewis@localhost) by misty.eyesbeyond.com (8.15.2/8.15.2/Submit) id x693r9oD086093; Mon, 8 Jul 2019 20:53:09 -0700 (PDT) (envelope-from glewis@eyesbeyond.com) X-Authentication-Warning: misty.eyesbeyond.com: glewis set sender to glewis@eyesbeyond.com using -f Date: Mon, 8 Jul 2019 20:53:09 -0700 From: Greg Lewis To: Jonathan Chen Cc: freebsd-java@freebsd.org Subject: Re: java/openjdk11 fails in "configure" Message-ID: <20190709035309.GA75164@misty.eyesbeyond.com> References: <20190708054659.GA25444@misty.eyesbeyond.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.12.1 (2019-06-15) X-Rspamd-Queue-Id: 0DD7274318 X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [2.08 / 15.00]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_SPAM_SHORT(0.56)[0.557,0]; MIME_GOOD(-0.10)[text/plain]; HAS_XAW(0.00)[]; DMARC_NA(0.00)[eyesbeyond.com]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.41)[0.406,0]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[cached: mail.iagu.net]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_SPAM_LONG(0.15)[0.145,0]; R_SPF_NA(0.00)[]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:209, ipnet:71.32.0.0/13, country:US]; IP_SCORE(-0.01)[asn: 209(-0.01), country: US(-0.06)] X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jul 2019 03:53:47 -0000 On Mon, Jul 08, 2019 at 10:33:41PM +1200, Jonathan Chen wrote: > On Mon, 8 Jul 2019 at 17:48, Greg Lewis wrote: > > > > On Sat, Jul 06, 2019 at 09:29:53PM +1200, Jonathan Chen wrote: > > > Hi, > > > > > > I'm currently seeing the following build failures on java/openjdk11 > > > during the "configure" phase: > > > [...] > > > configure: Will use user supplied compiler CC=cc > > > checking for cc... /usr/local/libexec/ccache/cc > > > checking resolved symbolic links for CC... /usr/local/bin/ccache > > > configure: Please use --enable-ccache instead of providing a wrapped compiler. > > > configure: error: /usr/local/libexec/ccache/cc is a symbolic link to > > > ccache. This is not supported. > > > configure exiting with result code 1 > > > ===> Script "configure" failed unexpectedly. > > > Please report the problem to java@FreeBSD.org [maintainer] and attach the > > > "/construction/xports/java/openjdk11/work/openjdk-jdk11u-jdk-11.0.3-7-2/config.log" > > > including the output of the failure of your make command. Also, it might be > > > a good idea to provide an overview of all packages installed on your system > > > (e.g. a /usr/local/sbin/pkg-static info -g -Ea). > > > *** Error code 1 > > > > > > Stop. > > > make: stopped in /xports/java/openjdk11 > > > > > > The build system (synth) has been configured to use ccache; and the > > > last known successful build was prior to r505640. > > > > If you revert r505640 and r505653 does ccache work? > > If I revert r505640, the build succeeds with ccache enabled. Thanks. After reviewing things, I think that this working previously was unintentional. I'll note that the Makefile for the port explicitly passes --disable-ccache as a configure argument. I'll also note the error message you're getting: configure: Will use user supplied compiler CC=cc checking for cc... /usr/local/libexec/ccache/cc checking resolved symbolic links for CC... /usr/local/bin/ccache configure: Please use --enable-ccache instead of providing a wrapped compiler. configure: error: /usr/local/libexec/ccache/cc is a symbolic link to ccache. This is not supported. If you remove the --disable-ccache from the configure args and instead add a block like this below: .if exists(${LOCALBASE}/bin/ccache) CONFIGURE_ARGS+= --enable-ccache .endif does that do the right thing (after you remove the overrides of CC, etc.)? How much does using ccache actually speed up the build? Or to put it another way, is the complexity worth it? -- Greg