Date: Fri, 30 Aug 2024 21:03:31 +0200 From: Dimitry Andric <dim@FreeBSD.org> To: J David <j.david.lists@gmail.com> Cc: freebsd-ports@freebsd.org Subject: Re: Building certain ports fails with errors in system C++ libraries Message-ID: <D141B06A-7CF5-4A0B-AE72-C684332C66FF@FreeBSD.org> In-Reply-To: <CABXB=RRLZdJ27%2Bb_oHDdo%2BRsYnFx0Jix0WdCXsLhKHvvEMM8yg@mail.gmail.com> References: <CABXB=RQyTBJ1y-PzVey%2BabKNP=o5ydQGx6B%2Bq6p%2B=Y11=5H_DQ@mail.gmail.com> <2B2BB530-202A-4359-BFC9-A608A8FC66FE@FreeBSD.org> <CABXB=RSzP6%2B%2B8psA1%2BaXgRPn6kR6k7g8X%2Br-Or3PuqA8ayg6%2Bg@mail.gmail.com> <2047D1EE-A369-4F88-93C3-E11AEC3A22E9@FreeBSD.org> <CABXB=RRLZdJ27%2Bb_oHDdo%2BRsYnFx0Jix0WdCXsLhKHvvEMM8yg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 30 Aug 2024, at 20:45, J David <j.david.lists@gmail.com> wrote: >=20 > On Fri, Aug 30, 2024 at 2:36=E2=80=AFPM Dimitry Andric = <dim@freebsd.org> wrote: >> Try using the attached patch. >=20 > Wow. That's... nasty... but effective. Haven't tested (I'm not the end > user) but it does build that way. I guess it's probably safe because > it's not like the code could have also been using std::hex somewhere. This program is written in a bit of a weird mixed C and C++ style. It looks like somebody tried to modernize an aging C codebase, then stopped halfway through. :) It is not really anything special though, there are loads of programs in ports that have strange or sloppy coding styles. If there is still an active upstream you can always try to prod them to fix it, but if they are grumpy or if upstream is dead, you can either patch out all the nastiness, or delete the port. > Do you want to open a bug report about it? It's your patch. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D281141 -Dimitry
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D141B06A-7CF5-4A0B-AE72-C684332C66FF>