The odd thing is that this compiler flag is hardcoded into the build by the upstream. I'm wondering why Fedora hits this when no one else seems to.
I mean, I'm fine to disable it, because the Chromium codebase is a tomb of horrors anyway, and if I have to sacrifice that flag to make it happy, so be it. ~tom On Wed, Mar 13, 2019 at 10:37 AM Jakub Jelinek <ja...@redhat.com> wrote: > On Wed, Mar 13, 2019 at 10:28:29AM -0400, Tom Callaway wrote: > > I tried removing some of the compiler flags to see if I could identify > what > > might be triggering this, and removing "-fno-delete-null-pointer-checks" > > seems to make this error vanish. > > -fno-delete-null-pointer-checks is certainly an option that requests that > the compiler does not fold comparisons against NULL at compile time based > on > assumption that objects have non-NULL address, so sure, if it has such > asserts, > it is incompatible with that option, you can't have both. > > Jakub >
_______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
