Florian Weimer <[email protected]> writes:
> Today, I pushed a redhat-rpm-config update to rawhide,
> redhat-rpm-config-260-1.fc39. The only expected change is that
> -Wno-complain-wrong-lang now shows up in %optflags (but not
> %build_cflags etc.). It should prevent Fortran compilers from warning
> on -Werror=format-security (and failing to build with -Werror). That
> bogus -Werror=format-security is also gone from %build_fflags. I think
> I found a relatively concise way to express this in the macros language
> (using non-lexical macro bindings).
>
> There's some code in there for more -Werror= options, but it's disabled
> by default pending Fesco approval.
>
> I tested this change and it seems to work as expected, but I thought I
> should send this note nevertheless.
I'm seeing warnings when building with the new redhat-rpm-config with
clang:
warning: unknown warning option '-Wno-complain-wrong-lang'; did you
mean '-Wno-c++11-long-long'? [-Wunknown-warning-option]
I'm also seeing other warnings that appear to be related:
/builddir/build/SPECS/llvm.spec: line 259: Macro %__build_for_lang_any
defined but not used within scope
/builddir/build/SPECS/llvm.spec: line 259: Macro %__build_for_lang_cxx
defined but not used within scope
/builddir/build/SPECS/llvm.spec: line 259: Macro %__build_for_lang_any
defined but not used within scope
/builddir/build/SPECS/llvm.spec: line 259: Macro %__build_for_lang_c
defined but not used within scope
/builddir/build/SPECS/llvm.spec: line 259: Macro %__build_for_lang_any
defined but not used within scope
/builddir/build/SPECS/llvm.spec: line 259: Macro %__build_for_lang_c
defined but not used within scope
/builddir/build/SPECS/llvm.spec: line 259: Macro %__build_for_lang_cxx
defined but not used within scope
/builddir/build/SPECS/llvm.spec: line 259: Macro %__build_for_lang_any
defined but not used within scope
/builddir/build/SPECS/llvm.spec: line 259: Macro %__build_for_lang_c
defined but not used within scope
/builddir/build/SPECS/llvm.spec: line 259: Macro %__build_for_lang_cxx
defined but not used within scope
All of this is happening on s390x.
Source: https://kojipkgs.fedoraproject.org//work/tasks/7633/103007633/build.log
--
Tulio Magno
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
