On Mon, Aug 3, 2020 at 8:32 PM Jerry James wrote:
>
> On Sun, Aug 2, 2020 at 11:27 AM Jerry James wrote:
> > You can point the finger of blame at least partly at me for this.
> > Version 0.15.0 of check introduced the use of
> > __attribute__((printf)) to check the arguments to some of the
>
On Sun, Aug 2, 2020 at 11:27 AM Jerry James wrote:
> You can point the finger of blame at least partly at me for this.
> Version 0.15.0 of check introduced the use of
> __attribute__((printf)) to check the arguments to some of the
> calls. However, upstream didn't do it right, with the
On Sun, Aug 2, 2020 at 9:55 AM Fabio Valentini wrote:
> I'm looking through F33 FTBFS issues, and I see an increasing number
> of packages that fail to build because their test suites (using check)
> fail to build with errors like this:
>
> /usr/include/check.h:502:27: note: declared here
> 502
Hi all,
I'm looking through F33 FTBFS issues, and I see an increasing number
of packages that fail to build because their test suites (using check)
fail to build with errors like this:
/usr/include/check.h:502:27: note: declared here
502 | CK_DLL_EXP void CK_EXPORT _ck_assert_failed(const char
