Created attachment 434754 [details] build.log Two instances of this are reported in my build.log: > checking minix/config.h usability... /var/tmp/portage/sys-devel/gcc-5.3.0/work/gcc-5.3.0/libcpp/expr.c: In function ‘unsigned int cpp_classify_number(cpp_reader*, const cpp_token*, const char**, source_location)’: > /var/tmp/portage/sys-devel/gcc-5.3.0/work/gcc-5.3.0/libcpp/expr.c:681:18: error: format not a string literal and no format arguments [-Werror=format-security] > 0, message); > ^ > /var/tmp/portage/sys-devel/gcc-5.3.0/work/gcc-5.3.0/libcpp/expr.c:684:39: error: format not a string literal and no format arguments [-Werror=format-security] > virtual_location, 0, message); > ^ > cc1plus: some warnings being treated as errors > Makefile:224: recipe for target 'expr.o' failed > make[3]: *** [expr.o] Error 1 And: > checking whether x86_64-pc-linux-gnu-gcc supports -Wstrict-prototypes... /var/tmp/portage/sys-devel/gcc-5.3.0/work/gcc-5.3.0/libcpp/macro.c: In function ‘bool create_iso_definition(cpp_reader*, cpp_macro*)’: > /var/tmp/portage/sys-devel/gcc-5.3.0/work/gcc-5.3.0/libcpp/macro.c:3087:58: error: format not a string literal and no format arguments [-Werror=format-security] > cpp_error (pfile, CPP_DL_ERROR, paste_op_error_msg); > ^ > /var/tmp/portage/sys-devel/gcc-5.3.0/work/gcc-5.3.0/libcpp/macro.c:3100:58: error: format not a string literal and no format arguments [-Werror=format-security] > cpp_error (pfile, CPP_DL_ERROR, paste_op_error_msg); > ^ > cc1plus: some warnings being treated as errors > Makefile:224: recipe for target 'macro.o' failed > make[3]: *** [macro.o] Error 1
Created attachment 434756 [details] gcc-build-logs.tar.bz2
Created attachment 459124 [details] gcc-5.4.0-r2-build.log This also occurs with sys-devel/gcc-5.4.0-r2.
Created attachment 554260 [details] gcc-8.2.0-r4 build.log This is still an issue with gcc-8.2.0-r4.
That has to be fixed upstream. Non-literal format strings are common for gettext-like NLS code when format string comes from localization files.