From nobody Tue May 27 15:39:24 2025 X-Original-To: dev-commits-ports-main@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 4b6Gyx0bt7z5xZFP; Tue, 27 May 2025 15:39:37 +0000 (UTC) (envelope-from gerald@pfeifer.com) Received: from hamza.pair.com (hamza.pair.com [209.68.5.143]) (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 4b6Gyv6SnRz3LcM; Tue, 27 May 2025 15:39:35 +0000 (UTC) (envelope-from gerald@pfeifer.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=pfeifer.com header.s=pair-202402271039 header.b=b2dEQGk7; dmarc=none; spf=pass (mx1.freebsd.org: domain of gerald@pfeifer.com designates 209.68.5.143 as permitted sender) smtp.mailfrom=gerald@pfeifer.com Received: from hamza.pair.com (localhost [127.0.0.1]) by hamza.pair.com (Postfix) with ESMTP id 5C15533F15; Tue, 27 May 2025 11:39:29 -0400 (EDT) Received: from [192.168.144.87] (ip-109-40-48-108.web.vodafone.de [109.40.48.108]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by hamza.pair.com (Postfix) with ESMTPSA id 54DA333EFB; Tue, 27 May 2025 11:39:27 -0400 (EDT) Date: Tue, 27 May 2025 18:39:24 +0300 (+03) From: Gerald Pfeifer To: Vladimir Druzenko , "Jason W. Bacon" cc: Hayzam Sherif , ports-committers@FreeBSD.org, dev-commits-ports-all@FreeBSD.org, dev-commits-ports-main@FreeBSD.org Subject: Re: git: 40478d7acd2a - main - biology/bifrost: Unbreak build on 15-CURRENT In-Reply-To: <82d64a95-d614-48df-9ba5-cce10209c19f@gmail.com> Message-ID: References: <202505151138.54FBcqe4040748@gitrepo.freebsd.org> <20a662ed-1233-c096-8615-c4df9e277713@pfeifer.com> <84105b29-4d52-fd89-4e20-6bb37f04b4da@pfeifer.com> <82d64a95-d614-48df-9ba5-cce10209c19f@gmail.com> List-Id: Commits to the main branch of the FreeBSD ports repository List-Archive: https://lists.freebsd.org/archives/dev-commits-ports-main List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: dev-commits-ports-main@freebsd.org Sender: owner-dev-commits-ports-main@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pfeifer.com; h=date:from:to:cc:subject:in-reply-to:message-id:references:mime-version:content-type; s=pair-202402271039; bh=asGju/GKM3TqEyIffZXu03CVKKUR1F6V9V0kYkSU2AU=; b=b2dEQGk7YGWOgG0j4L0ZhQsx4SKzCf2o38nsuXyiAqXS3Us94EFOEWVIGh9xEuEnhYNQsgbfE8ejDZKsprQ6Wjm9Yi28f1QjF+0tymVP5WEpGzV+CHHgAPHEtoJlCCrOF1nrAAXTQEY5CcPlbu8t2V8OlolNVQR4720EWlrRRaoqpooA5EY12XADhwvB/2G54VnrADsksesCmuALWViVjJqzCkOtMXDe+aWwG2o1AIbwmVLR4Ah0dD+EuggiLp1Ge8RpsL23u+w4bEH9mcDkAURNvCWMZ5kpUBaqVFmDJObQ/dfXoc2RgCIKCvFQQ0+kRB+nwk/3odYlrRV8naUXaA== X-Scanned-By: mailmunge 3.11 on 209.68.5.143 X-Spamd-Result: default: False [-3.47 / 15.00]; NEURAL_HAM_LONG(-0.99)[-0.991]; NEURAL_HAM_MEDIUM(-0.99)[-0.990]; NEURAL_HAM_SHORT(-0.99)[-0.985]; R_DKIM_ALLOW(-0.20)[pfeifer.com:s=pair-202402271039]; R_SPF_ALLOW(-0.20)[+a:hamza.pair.com]; MIME_GOOD(-0.10)[text/plain]; ASN(0.00)[asn:7859, ipnet:209.68.0.0/18, country:US]; ARC_NA(0.00)[]; MISSING_XM_UA(0.00)[]; FREEFALL_USER(0.00)[gerald]; MIME_TRACE(0.00)[0:+]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; DMARC_NA(0.00)[pfeifer.com]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; RCPT_COUNT_FIVE(0.00)[6]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MLMMJ_DEST(0.00)[dev-commits-ports-all@FreeBSD.org,dev-commits-ports-main@FreeBSD.org]; RCVD_TLS_LAST(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; DKIM_TRACE(0.00)[pfeifer.com:+] X-Rspamd-Queue-Id: 4b6Gyv6SnRz3LcM X-Spamd-Bar: --- On Mon, 26 May 2025, Jason Bacon wrote: >>> (USE_GCC itself is not problematic, especially if something really is >>> GCC-specific. Just using it to work around clang getting stricter over >>> time has often bitten us with loads of extra work and delays when then >>> updating GCC_DEFAULT.) >> Maybe try "USES=llvm:max=18" as a workaround? > I would consider that if it proved difficult to fix for the base > compiler, but I'd hate to have a compiler dependency if we can avoid it. Agreed. This is why I raised USE_GCC being such a compiler dependency, where I'd prefer USES=llvm:max=18 over USE_GCC=yes which causes those problems down the path when upgrading GCC_DEFAULt. On Tue, 27 May 2025, Jason Bacon wrote: > Updated bifrost and kallisto are committed. Very nice, thank you! Especially for thinking of the other port as well. > Hayzam came up with a DataStorage.tcc fix, and later found the same > suggestion here: > > https://github.com/pmelsted/bifrost/pull/18/files Nice. Looks like both our ports tree improved and upstream hopefully also will pick up that fix. Gerald