Date: Sat, 09 Sep 2023 08:39:50 +0000 From: bugzilla-noreply@freebsd.org To: gnome@FreeBSD.org Subject: [Bug 273649] textproc/enchant: Fix build with LLVM/clang++ 16 Message-ID: <bug-273649-6497-AJGegAyT9z@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-273649-6497@https.bugs.freebsd.org/bugzilla/> References: <bug-273649-6497@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D273649 --- Comment #3 from Olivier Certner <olivier.freebsd@free.fr> --- (In reply to Alexey Dokuchaev from comment #2) The only errors this build produces are these: > error: ISO C++17 does not allow 'register' storage class specifier and there are dozens of them. They are harmless, and in fact were fixed upstream long ago (in 2017). For there reasons, I don't think it's worth it to patch them out. I'll also no= te that upstream explicitly requires C++11 in the newer 1.6.1 version (from 20= 17) of the 1.x series. So I tend to think that this should go in as is (perhaps using "USE_CXXSTD=3Dc++11" instead). An alternative would be to upgrade to 1.6.1= , but this can be done afterwards with no harm (it is likely to take more time, a= nd right now I can't). As to why there are no fallouts, for 13, that's normal since apparently the last builds were with clang 14.0.5, whereas I have clang 16.0.6 (I'm on 13-STABLE from end of August). The latter clang version is also the one us= ed for the latest pkg builds for 14-STABLE, where no fallouts can be seen, and= I'm not sure why. FWIW, I'm using the ports tree at 38c671e45e4bae21a0199079d08273c1f171e1d4. What do you think? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-273649-6497-AJGegAyT9z>