rpms/redhat-rpm-config
7
0
Fork 0
Code Issues Pull Requests Releases Activity

Switch %build_type_safety_c to 1 (#2142177)

Browse Source
This commit is contained in:
Florian Weimer 2023-09-26 18:36:28 +02:00
parent df12b70625
commit a2798ac4c1
3 changed files with 19 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
buildflags.md
View File

@ -117,15 +117,17 @@ or:
### Controlling Type Safety ### Controlling Type Safety
The macro `%build_type_safety_c` can be set to change the C type The macro `%build_type_safety_c` can be set to change the C type
safety level. By default (value 0), all C constructs that GCC accepts safety level. The default level is 1, see below. It can be set to 0
for backwards compatibility with obsolete language standards are to get historic levels of type safety. Changing the type safety level
accepted during package builds. Packages can set may depend on correct `CFLAGS` propagation during the build. The
`%build_type_safety_c` to higher values to adopt future `%build_type_safety_c` macro needs to be set before `CFLAGS`-related
distribution-wide type-safety increases early. macros are expanded by RPM (that is, earlier in the file works
better).
When changing the `%build_type_safety_c` level to increase it, spec Packages can set `%build_type_safety_c` to higher values to adopt
file should use a construct like this to avoid *lowering* a future future distribution-wide type-safety increases early. When changing
default: the `%build_type_safety_c` level to increase it, spec file should use
a construct like this to avoid *lowering* a future default:
``` ```
%if %build_type_safety_c < 2 %if %build_type_safety_c < 2
@ -133,6 +135,10 @@ default:
%endif %endif
``` ```
At level 0, all C constructs that GCC accepts for backwards
compatibility with obsolete language standards are accepted during
package builds.
At level 1, the following additional error categories are enabled: At level 1, the following additional error categories are enabled:
* `-Werror=implicit-int`: Reject declarations and definitions that * `-Werror=implicit-int`: Reject declarations and definitions that

2
macros
View File

@ -393,7 +393,7 @@ for k,_ in pairs(stripped_flags) do print(k .. " ") end
# This can be set to a positive integer to obtain increasing type # This can be set to a positive integer to obtain increasing type
# safety levels for C. See buildflags.md. # safety levels for C. See buildflags.md.
%build_type_safety_c 0 %build_type_safety_c 1
# Some linkers default to a build-id algorithm that is not supported by rpmbuild, # Some linkers default to a build-id algorithm that is not supported by rpmbuild,
# so we need to specify the right algorithm to use. # so we need to specify the right algorithm to use.

5
redhat-rpm-config.spec
View File

@ -4,7 +4,7 @@
# 2) When making changes, increment the version (in baserelease) by 1. # 2) When making changes, increment the version (in baserelease) by 1.
# rpmdev-bumpspec and other tools update the macro below, which is used # rpmdev-bumpspec and other tools update the macro below, which is used
# in Version: to get the desired effect. # in Version: to get the desired effect.
%global baserelease 266 %global baserelease 267
Summary: Red Hat specific rpm configuration files Summary: Red Hat specific rpm configuration files
Name: redhat-rpm-config Name: redhat-rpm-config
@ -254,6 +254,9 @@ install -p -m 644 -t %{buildroot}%{_rpmluadir}/fedora common.lua
%doc buildflags.md %doc buildflags.md
%changelog %changelog
* Tue Sep 26 2023 Florian Weimer <fweimer@redhat.com> - 267-1
- Switch %%build_type_safety_c to 1 (#2142177)
* Thu Sep 07 2023 Maxwell G <maxwell@gtmx.me> - 266-1 * Thu Sep 07 2023 Maxwell G <maxwell@gtmx.me> - 266-1
- Split out forge macros to forge-srpm-macros package - Split out forge macros to forge-srpm-macros package