On 09/11/17 18:09, Christopher Li wrote: > On Fri, Nov 10, 2017 at 2:03 AM, Ramsay Jones > <ramsay@xxxxxxxxxxxxxxxxxxxx> wrote: >> >> Ah, no longer puzzled. Hmm, didn't there used to be a rule like: >> >> sparse-llvm.o sparse-llvm.sc: BASIC_CFLAGS += $(LLVM_CFLAGS) >> > > I search the history. Nope, I miss that when I add the selfcheck. > I did not catch this error because on FC26 missing the LLVM_CFLAGS > does not cause compile error. Heh, our emails crossed. > > $ llvm-config --cflags > -I/usr/include -O2 -g -pipe -Wall -Werror=format-security > -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong > --param=ssp-buffer-size=4 -grecord-gcc-switches > -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m64 -mtune=generic > -fPIC -Wall -W -Wno-unused-parameter -Wwrite-strings > -Wno-missing-field-initializers -pedantic -Wno-long-long -Wno-comment > -Werror=date-time -ffunction-sections -fdata-sections -O2 -g -DNDEBUG > -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS > -D__STDC_LIMIT_MACROS > > "llvm-config --cflags" does not introduce new header file searching directory. Ah, OK. So, 'llvm-config --cflags' produces different output on whichever platform Luc is on? ATB, Ramsay Jones -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
