From nobody Fri Aug 30 18:36:42 2024 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 4WwRhB1dJgz5PV9V for ; Fri, 30 Aug 2024 18:36:58 +0000 (UTC) (envelope-from jdavidlists@gmail.com) Received: from mail-pf1-x42e.google.com (mail-pf1-x42e.google.com [IPv6:2607:f8b0:4864:20::42e]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4WwRh95GRZz4Qfv; Fri, 30 Aug 2024 18:36:57 +0000 (UTC) (envelope-from jdavidlists@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pf1-x42e.google.com with SMTP id d2e1a72fcca58-71431524f33so1686057b3a.1; Fri, 30 Aug 2024 11:36:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1725043016; x=1725647816; darn=freebsd.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=dhNctsEQalEUTrGGu0LrGhAsVv9PBsZNYIYSoq3K5Ro=; b=B3QB8qlRtV8mrRSbEIb5EMRjhb+0azsKjIt1KzyPGQH32Iq20hAsrWCaeDVlnk4BMI +fPSQI0O8KwqUFRCT/7x+/fxYAlySn4FDrdXpcoxTzNyiDsIOKdtw/khUjkuwK6ZueVX Tr/LHmKqJLTdFfw0iIOn3mIrnijmWZabJKZGy2rTwPV3quSZ46+VMmke7v4kdEVoH0g5 lnZ155iiWmQLzerV0+zarhNv/pj/jxy0m9fAotsx3kWPGCWtiXPDV+01n5QDZBUeYvlX VmUazV17gxDNLgJ884wlhR1IefircWjYjXdn2STU5ITTbcixrs8eCwecprvPSRnzfxcz OpOA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1725043016; x=1725647816; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=dhNctsEQalEUTrGGu0LrGhAsVv9PBsZNYIYSoq3K5Ro=; b=SKnu5ZxmFLeIFcAflAhpFtt8FzkjuEQQKsodeRcO3qgT5c2m1lKVLCyvX6Ccu9BVBb mqBaxtoA/xYxf5ng/gRAIl9/RBUe2DUlPf1r57fzwNhj9qyrRUIDq7xd6M0/Xi6xeEud LsR2G+l6lBcCCufRLs/WTXCTv6S47Vxk4kRJ6+5gIk/+eQEC2exuizT1OldzPQ4E3O/D WXwhPOhhB1NCYqK7iignpZUvB/WgNSBa+rensHVp92rpTNLwf8dsSy4l9zoo4Dl1aFIB bbtnMZjlbD2uUdwf2LQPtVBZgAH0PEPNUbnWrETHfvwnNcFH3Y2WnWeLREKku/fK6OPS AsVQ== X-Gm-Message-State: AOJu0YyDj5AeZH1N6mUgmKUGZI1T53Zzb3d2LUI5zdhwgSrf/tl8SZBR Hor1pacpv2ue1IDvHQmqroU0rGVY6UROy20MRg+1IBU6GbHwpjLRl/rIBjVbEFovdHBYitSjuV4 +yOVH5Ufvzza8iGIt9MeP5MXicMaN7w== X-Google-Smtp-Source: AGHT+IHVEDJhphKw1HFKVEYpMUV+HMxqTHuR/hs2fgO+/zuWfKky3Bby4XIyZf+1FFucsEiuTIlP598kFB0iswMF2Ug= X-Received: by 2002:a17:90b:1c90:b0:2cd:4593:2a8e with SMTP id 98e67ed59e1d1-2d8561a358amr7518369a91.15.1725043015849; Fri, 30 Aug 2024 11:36:55 -0700 (PDT) List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-ports@freebsd.org Sender: owner-freebsd-ports@FreeBSD.org MIME-Version: 1.0 References: <2B2BB530-202A-4359-BFC9-A608A8FC66FE@FreeBSD.org> <6B3FF656-064D-48BF-85B2-3028D868F04A@FreeBSD.org> In-Reply-To: <6B3FF656-064D-48BF-85B2-3028D868F04A@FreeBSD.org> From: J David Date: Fri, 30 Aug 2024 14:36:42 -0400 Message-ID: Subject: Re: Building certain ports fails with errors in system C++ libraries To: Dimitry Andric Cc: freebsd-ports@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4WwRh95GRZz4Qfv On Fri, Aug 30, 2024 at 2:19=E2=80=AFPM Dimitry Andric wr= ote: > As to your question about why it builds for the package builders, my > guess is that these use the oldest supported releases, so 13.3 and 14.0, > which have older versions of the libc++ headers. That could be true for 14.0; I haven't tried that version. But it doesn't appear to build on 13.3 either. However, based on Freshports, it looks like maybe the 13.3 builds are only succeeding for armv6 and powerpc64. So maybe I'm not the only one after all. As you pointed out, redefining "hex" isn't a smart move, which kind of puts this in "how did it ever work?" territory. std::hex is not exactly new! Is this worth reporting as a port bug? What could the maintainer even do? Build a patch that renames every use of this interloping "hex" #define? Yuck. Thanks for helping to track it down. (And apologies for the incomplete send earlier.)