On Sat, Jan 29, 2022 at 02:18:14PM +, Sérgio Basto wrote:
> On Sat, 2022-01-29 at 09:56 +0100, Jakub Jelinek wrote:
> > On Sat, Jan 29, 2022 at 04:03:06PM +1000, Bob Hepple wrote:
> > > One of my packages, stable for a long time, is now getting exotic
> > > errors in rawhide such as
> > >
> >
Hrmph! Those errors are gone but I now have others - looks like the
compiler has become much stricter:
/usr/include/c++/12/bits/basic_string.h:235:28: error: 'MEM[(const
struct basic_string *) + 176B]._M_dataplus._M_p' may be used
uninitialized [-Werror=maybe-uninitialized]
Hopefully I can patch
On Sat, 2022-01-29 at 09:56 +0100, Jakub Jelinek wrote:
> On Sat, Jan 29, 2022 at 04:03:06PM +1000, Bob Hepple wrote:
> > One of my packages, stable for a long time, is now getting exotic
> > errors in rawhide such as
> >
> > -D_FORTIFY_SOURCE not defined
> > -D_GLIBCXX_ASSERTIONS not defined
> >
On 29/01/2022 07:03, Bob Hepple wrote:
-D_FORTIFY_SOURCE not defined
-D_GLIBCXX_ASSERTIONS not defined
https://bugzilla.redhat.com/show_bug.cgi?id=2047148
Should I just wait for that fix to land in koji? If so, how long?
Already fixed in Koji.
Mock will be fixed only after the next
On Sat, Jan 29, 2022 at 04:03:06PM +1000, Bob Hepple wrote:
> One of my packages, stable for a long time, is now getting exotic
> errors in rawhide such as
>
> -D_FORTIFY_SOURCE not defined
> -D_GLIBCXX_ASSERTIONS not defined
>
> Yesterday I saw (somewhere in here) that those errors are fixed in
On Sat, Jan 29, 2022 at 04:03:06PM +1000, Bob Hepple wrote:
> One of my packages, stable for a long time, is now getting exotic
> errors in rawhide such as
>
> -D_FORTIFY_SOURCE not defined
> -D_GLIBCXX_ASSERTIONS not defined
>
> Yesterday I saw (somewhere in here) that those errors are fixed in
