Re: -D_FORTIFY_SOURCE not defined errors

2022-01-30 Thread Kevin Fenzi
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
> > > 
> > > -D_FORTIFY_SOURCE not defined
> > > -D_GLIBCXX_ASSERTIONS not defined
> > > 
> > > Yesterday I saw (somewhere in here) that those errors are fixed in
> > > the
> > > latest annobin.
> > > 
> > > Should I just wait for that fix to land in koji? If so, how long?
> > 
> > It was fixed yesterday.
> > Are you sure your builds were against
> > gcc-12.0.1-0.3.fc36 annobin-10.51-2.fc36
> > and not an older version of annobin?
> 
> But rawhide compose of last 2 days failed , so new annobin is not in
> buildroot  and this problem will still happen on copr for example 

Yep. You can enable the 'local' repo in mock and it will pull in the
koji buildroot. That may be slow depending on your BW, but it should
work. 

The rawhide compose failures the last two days are very fun: The 32bit
arm minimal image is failing to compose. It boots up in libvirt/qemu and
it's date is 2022-01-21 somehow. We just renewed the fedoraproject.org
wildcard cert last week, and it's not valid until 2022-01-27, so curl
fails to get the stage2 image, etc. This only happens it seems on armv7.

kevin


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: -D_FORTIFY_SOURCE not defined errors

2022-01-29 Thread Bob Hepple
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 them.

Cheers


Bob

On Sun, 30 Jan 2022 at 00:19, 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
> > >
> > > -D_FORTIFY_SOURCE not defined
> > > -D_GLIBCXX_ASSERTIONS not defined
> > >
> > > Yesterday I saw (somewhere in here) that those errors are fixed in
> > > the
> > > latest annobin.
> > >
> > > Should I just wait for that fix to land in koji? If so, how long?
> >
> > It was fixed yesterday.
> > Are you sure your builds were against
> > gcc-12.0.1-0.3.fc36 annobin-10.51-2.fc36
> > and not an older version of annobin?
>
> But rawhide compose of last 2 days failed , so new annobin is not in
> buildroot  and this problem will still happen on copr for example
>
> > Jakub
> > ___
> > devel mailing list -- devel@lists.fedoraproject.org
> > To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> > Fedora Code of Conduct:
> > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines:
> > https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives:
> > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> > Do not reply to spam on the list, report it:
> > https://pagure.io/fedora-infrastructure
>
> --
> Sérgio M. B.
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it: 
> https://pagure.io/fedora-infrastructure
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: -D_FORTIFY_SOURCE not defined errors

2022-01-29 Thread Sérgio Basto
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
> > 
> > Yesterday I saw (somewhere in here) that those errors are fixed in
> > the
> > latest annobin.
> > 
> > Should I just wait for that fix to land in koji? If so, how long?
> 
> It was fixed yesterday.
> Are you sure your builds were against
> gcc-12.0.1-0.3.fc36 annobin-10.51-2.fc36
> and not an older version of annobin?

But rawhide compose of last 2 days failed , so new annobin is not in
buildroot  and this problem will still happen on copr for example 

> Jakub
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines:
> https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure

-- 
Sérgio M. B.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: -D_FORTIFY_SOURCE not defined errors

2022-01-29 Thread Vitaly Zaitsev via devel

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 successful Rawhide compose. As a 
workaround you can use `--enablerepo=local`, but it will be very slow.


--
Sincerely,
  Vitaly Zaitsev (vit...@easycoding.org)
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: -D_FORTIFY_SOURCE not defined errors

2022-01-29 Thread Jakub Jelinek
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 the
> latest annobin.
> 
> Should I just wait for that fix to land in koji? If so, how long?

It was fixed yesterday.
Are you sure your builds were against
gcc-12.0.1-0.3.fc36 annobin-10.51-2.fc36
and not an older version of annobin?

Jakub
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: -D_FORTIFY_SOURCE not defined errors

2022-01-29 Thread Zbigniew Jędrzejewski-Szmek
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 the
> latest annobin.
> 
> Should I just wait for that fix to land in koji? If so, how long?

The fix already is in koji. So builds in koji should work. If you need
it for a local build, you can use something like [1] or [2].

[1] mock -i 
https://kojipkgs.fedoraproject.org//packages/annobin/10.53/1.fc36/x86_64/annobin-plugin-gcc-10.53-1.fc36.x86_64.rpm
 
https://kojipkgs.fedoraproject.org//packages/annobin/10.53/1.fc36/noarch/annobin-docs-10.53-1.fc36.noarch.rpm
mock -n ...
[2] mock --enablerepo=local ...

Zbyszek
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure