From nobody Mon Aug 07 23:54:46 2023 X-Original-To: freebsd-current@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 4RKY8Y0j6Tz4pn4Q for ; Mon, 7 Aug 2023 23:54:53 +0000 (UTC) (envelope-from yuri@aetern.org) Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (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 4RKY8X1frvz4Yhj for ; Mon, 7 Aug 2023 23:54:51 +0000 (UTC) (envelope-from yuri@aetern.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=aetern.org header.s=fm3 header.b=EbEx1dCt; dkim=pass header.d=messagingengine.com header.s=fm3 header.b="L RoQTsB"; spf=pass (mx1.freebsd.org: domain of yuri@aetern.org designates 64.147.123.21 as permitted sender) smtp.mailfrom=yuri@aetern.org Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id D856E320077A for ; Mon, 7 Aug 2023 19:54:49 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Mon, 07 Aug 2023 19:54:50 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aetern.org; h=cc :content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm3; t= 1691452489; x=1691538889; bh=f/VJ2RzPXw0jPZfPBrm8TXI8+GWbi7ZNuzG Xwap3G80=; b=EbEx1dCtSEmqH/vsVfwhUjwpr6Tk3hqHFICQr3eQCrrSG9QwBug gEK+OjLLxBvSjblvSsO28e/Dsvi65BhpoZQESiQd3CiWZYcs6iUU6mBan+/PiENY 11tujxah3qcDlTfPhu6JuR87nrP2sadK+ApQQJ1Qz7FnN+Rrs0ucuO6Vi2s/djS5 pSdoDgL+HqKkNjUSk4FyHQBGhZbmjASVnluWZssOZQ0GSMjdPx9qnGjwck4HnrLc 0oJQ/87EYUlvNXhhS5pDBIq44/omXnAKnmdVEzWtfts2pjqmS8j45gW5fj9nV48g kosO/vBmD6zzzxbcGCE8SQ+5eZIt5e9wdAg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1691452489; x= 1691538889; bh=f/VJ2RzPXw0jPZfPBrm8TXI8+GWbi7ZNuzGXwap3G80=; b=L RoQTsBcOxvMQ5cH37u65Ya9vVAtGnKo9HL/dkDwNs49COHHe6Ar3IT5SsWTdWuRW We1lUnnodWvxXjvYZH8cyZ/srZkxN7YOYgC5Rpy34mtj8haq21jiNCJLNWbuTW1B FDOa632rz566DQOsdCBXdjTx403I+Zlo7s+O7rMzHwCXSJlMRyIPp8beXLI3nvEx YTON4F57wrfYjCuo98AsRIyE/tlrpRk3xEwknOMtsxT3AOoCKi4akXYMP88f7W0O bhhkgQMEVp+yEjqbVpRFAByHQkXuLNTjajuUlnJ7btBCYJmj1ui8/scXIO/j98iV SAaBl3CRr2xWpQSWg8sew== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrledugddviecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepkfffgggfuffvfhfhjggtgfesthekre dttddvjeenucfhrhhomhepjghurhhiuceohihurhhisegrvghtvghrnhdrohhrgheqnecu ggftrfgrthhtvghrnhepteekvefgfeetjeehieefudeivdekudektedufffgjeelhfdtje ekleehvdekuddunecuffhomhgrihhnpehfrhgvvggsshgurdhorhhgnecuvehluhhsthgv rhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhephihurhhisegrvghtvghrnh drohhrgh X-ME-Proxy: Feedback-ID: i0d79475b:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Mon, 7 Aug 2023 19:54:48 -0400 (EDT) Message-ID: <73d081d7-5df6-9fe4-659d-edb191c94be4@aetern.org> Date: Tue, 8 Aug 2023 01:54:46 +0200 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Jail compile error on CURRENT? Content-Language: en-US To: freebsd-current@freebsd.org References: <20230806225055.bbccc4fc13e41f50ec524621@j.email.ne.jp> From: Yuri In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4RKY8X1frvz4Yhj X-Spamd-Bar: / X-Rspamd-Pre-Result: action=no action; module=multimap; Matched map: local_wl_from X-Spamd-Result: default: False [0.61 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; R_DKIM_ALLOW(-0.20)[aetern.org:s=fm3,messagingengine.com:s=fm3]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.21]; XM_UA_NO_VERSION(0.01)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; DKIM_TRACE(0.00)[aetern.org:+,messagingengine.com:+]; local_wl_from(0.00)[yuri@aetern.org]; FREEFALL_USER(0.00)[yuri]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; ASN(0.00)[asn:29838, ipnet:64.147.123.0/24, country:US] James Gritton wrote: > On 2023-08-07 13:29, Dimitry Andric wrote: >> On 7 Aug 2023, at 04:50, Yoshihiro Ota wrote: >>> >>> Am I the only one seeing this error? >>> I'm on 12.4-RELEASE amd64 and building CURRENT as of now. >>> >>> jaillex.c:2228:43: error: unused parameter 'yyscanner' >>> [-Werror,-Wunused-parameter] >>> void *yyalloc (yy_size_t  size , yyscan_t yyscanner) >>>                                          ^ >>> jaillex.c:2233:58: error: unused parameter 'yyscanner' >>> [-Werror,-Wunused-parameter] >>> void *yyrealloc  (void * ptr, yy_size_t  size , yyscan_t yyscanner) >>>                                                         ^ >>> jaillex.c:2245:36: error: unused parameter 'yyscanner' >>> [-Werror,-Wunused-parameter] >>> void yyfree (void * ptr , yyscan_t yyscanner) >>>                                   ^ >>> 6 errors generated. >>> *** [jaillex.o] Error code 1 >>> >> >> It seems you are not crazy. :) I can reproduce the error, and I think it >> might be caused by: >> >> https://cgit.freebsd.org/src/commit/?id=086e0149ae56641af245ce472e787c2f67d3aea5 >> >> However, as to why this does not result in an error (or even a warning) >> on -CURRENT, I have no clue. Maybe in the mean time flex in -CURRENT got >> updated... > > That is indeed the culprit.  Fortunately, it builds from 13.2-RELEASE, > so building CURRENT from 12 can be done in two steps.  I hate to be the > reason the update doesn't work directly, but the include capability I > added to jail(8) requires re-entrant lex, which apparently managed to > work around the error in 13.  They reason it doesn't give a warning BTW > is these two lines that lex adds: > >         struct yyguts_t * yyg = (struct yyguts_t*)yyscanner; >         (void)yyg; > > That makes yyscanner officially "used" even though its value is never > actually read.  I suspect the version of lex in 12.4-RELEASE doesn't > have one or both of those lines. > > Perhaps you could add such lines to the offending functions yourself, > and continue the make.  Or maybe build (and install) lex on its own > first; by the time you see this error, there should already be a newer > version of lex you could pop into place. > > There's probably something I should do to make this work better, or > perhaps some note I should put into UPDATING before 14.0 is released. Or there is already a recipe for bootstrapping lex in Makefile.inc1, though for somewhat older versions; possibly it could be updated for < 13? .if ${BOOTSTRAPPING} < 1000033