Allow warnings in the build

Turning all warnings into errors is too strict for downstream packaging.
epel8
Benjamin A. Beasley 1 year ago
parent e00502a64f
commit 17d195d789

@ -118,10 +118,13 @@ CC='gcc'; export CC
CXX='g++'; export CXX CXX='g++'; export CXX
AR='gcc-ar'; export AR AR='gcc-ar'; export AR
%set_build_flags %set_build_flags
# Treating warnings as errors is too strict for downstream builds.
#
# Both --use-icf and --use-lto add compiler flags that only work with clang++, # Both --use-icf and --use-lto add compiler flags that only work with clang++,
# not with g++. We do get LTO on Fedora anyway, since we respect the # not with g++. We do get LTO on Fedora anyway, since we respect the
# distributions build flags. # distributions build flags.
%{python3} build/gen.py \ %{python3} build/gen.py \
--allow-warnings \
--no-last-commit-position \ --no-last-commit-position \
--no-strip \ --no-strip \
--no-static-libstdc++ --no-static-libstdc++

Loading…
Cancel
Save