Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1908185
Summary: | Possible GCC 11 regression when building Clementine: error: static assertion failed: invalid specialization | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Robert-André Mauchin 🐧 <zebob.m> |
Component: | clementine | Assignee: | Robert-André Mauchin 🐧 <zebob.m> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | aoliva, dmalcolm, fweimer, jakub, jgrulich, jwakely, law, mpolacek, msebor, nickc, oget.fedora, sipoyare, zebob.m |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-12-17 06:00:24 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1868278 |
Description
Robert-André Mauchin 🐧
2020-12-16 03:27:10 UTC
FWIW, my tester trips this as well, but clementine was failing with gcc-10 in rawhide before the introduction of gcc-11, so it never got high enough on my todo list to chase down. This is a package bug, not a GCC bug. The build.log shows that these build flags are used: --std=c++0x -U__STRICT_ANSI__ This is stupid. It asks for strict C++0x conformance, then asks for non-strict conformance. Just use -std=gnu++0x which means non-strict mode. Better yet, remove that flag and let GCC use its default (which is now -std=gnu++17). It's 2020, you don't need to add options to get "C++0x" features now. (In reply to Jonathan Wakely from comment #2) > This is stupid. It asks for strict C++0x conformance, then asks for > non-strict conformance. Or more accurately, it asks the compiler for a strict conformance mode, then lies to the standard library about what mode the compiler is using. (In reply to Jonathan Wakely from comment #2) > This is a package bug, not a GCC bug. > > The build.log shows that these build flags are used: > > --std=c++0x -U__STRICT_ANSI__ > > This is stupid. It asks for strict C++0x conformance, then asks for > non-strict conformance. > > Just use -std=gnu++0x which means non-strict mode. > > Better yet, remove that flag and let GCC use its default (which is now > -std=gnu++17). It's 2020, you don't need to add options to get "C++0x" > features now. (In reply to Jonathan Wakely from comment #3) > (In reply to Jonathan Wakely from comment #2) > > This is stupid. It asks for strict C++0x conformance, then asks for > > non-strict conformance. > > Or more accurately, it asks the compiler for a strict conformance mode, then > lies to the standard library about what mode the compiler is using. Thanks for your help, |