From nobody Mon Apr 25 05:12:29 2022 X-Original-To: freebsd-ports@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 A93461990840 for ; Mon, 25 Apr 2022 05:12:45 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from mx2.catspoiler.org (mx2.catspoiler.org [IPv6:2607:f740:16::d18]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "amnesiac", Issuer "amnesiac" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4KmtSD6QJBz4m7Q; Mon, 25 Apr 2022 05:12:44 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received-SPF: pass (mx2.catspoiler.org: 76.212.85.177 is whitelisted) receiver=mx2.catspoiler.org; client-ip=76.212.85.177; helo=gw.catspoiler.org; envelope-from=truckman@FreeBSD.org; x-software=spfmilter 2.001 http://www.acme.com/software/spfmilter/ with libspf2-1.2.10; Received: from gw.catspoiler.org ([76.212.85.177]) by mx2.catspoiler.org (8.16.1/8.16.1) with ESMTPS id 23P5CYnJ001406 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=FAIL); Mon, 25 Apr 2022 05:12:35 GMT (envelope-from truckman@FreeBSD.org) Received-SPF: pass (gw.catspoiler.org: 192.168.101.2 is whitelisted) receiver=gw.catspoiler.org; client-ip=192.168.101.2; helo=mousie.catspoiler.org; envelope-from=truckman@FreeBSD.org; x-software=spfmilter 2.001 http://www.acme.com/software/spfmilter/ with libspf2-1.2.10; Received: from mousie.catspoiler.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.16.1/8.16.1) with ESMTPS id 23P5CTEG041929 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 24 Apr 2022 22:12:29 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Date: Sun, 24 Apr 2022 22:12:29 -0700 (PDT) From: Don Lewis Subject: Re: Chromium and Iridium consistently not building for 123amd64 latest To: Rene Ladan cc: Pau Amma , freebsd-ports@freebsd.org Message-ID: References: <171EBF3C-350D-4C4B-A589-4966F3118B28.ref@yahoo.com> <171EBF3C-350D-4C4B-A589-4966F3118B28@yahoo.com> List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=us-ascii Content-Disposition: INLINE X-Rspamd-Queue-Id: 4KmtSD6QJBz4m7Q X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=softfail (mx1.freebsd.org: 2607:f740:16::d18 is neither permitted nor denied by domain of truckman@FreeBSD.org) smtp.mailfrom=truckman@FreeBSD.org X-Spamd-Result: default: False [-3.08 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FREEFALL_USER(0.00)[truckman]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-0.998]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[FreeBSD.org]; R_SPF_SOFTFAIL(0.00)[~all:c]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.99)[-0.985]; MLMMJ_DEST(0.00)[freebsd-ports]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:36236, ipnet:2607:f740:16::/48, country:US]; RCVD_TLS_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-ThisMailContainsUnwantedMimeParts: N On 24 Apr, Rene Ladan wrote: > On Mon, Apr 18, 2022 at 11:38:36PM +0000, Pau Amma wrote: >> On 2022-04-18 22:10, Mark Millard wrote: >> > Looking at the log shows other failures during 97% : >> >> [massive snip] >> >> > I suspect that the rest of the time was its very slow scanning >> > of the huge log file to report on the type of failure. This can >> > take 2+ hours of itself before the actual kill happens. I ran into this issue recently with a non-standard build of openoffice that produced multi-GB log files. The scan was taking > 24 hours. It might be more efficient to use a sed script that quits on first match instead of all of those greps. Something using hyperscan would probably be even better.