Date: Wed, 11 Nov 2020 15:16:35 +0000 From: bugzilla-noreply@freebsd.org To: toolchain@FreeBSD.org Subject: [Bug 250740] mail/mailsync 12.2-RELEASE breaks package build Message-ID: <bug-250740-29464-3iuR2SND9V@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-250740-29464@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250740 --- Comment #4 from Fernando ApesteguĂa <fernape@FreeBSD.org> --- (In reply to Dimitry Andric from comment #3) Hi Dimitry! Yes, it does something similar with "and", "or"... and workarounds the problem by using -fno-name-operators. Having a look at the code it looks like the author thought that flag would protect them: extern "C" { /* If you use gcc, you may also have to use -fno-operator-names */ #define private cclientPrivate /* private to c-client */ #define and cclientAnd /* C99 doesn't realize that ISO 646 is dead */ #define or cclientOr #define not cclientNot #endif Now, my question is why does it work in different versions of clang, including the most recent one but seems to fail from time to time across versions? -- You are receiving this mail because: You are on the CC list for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-250740-29464-3iuR2SND9V>
