Re: Building certain ports fails with errors in system C++ libraries

From: J David <j.david.lists_at_gmail.com>
Date: Fri, 30 Aug 2024 18:36:42 UTC
On Fri, Aug 30, 2024 at 2:19 PM Dimitry Andric <dim@freebsd.org> wrote:
> 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.)