Package: blhc
Version: 0.05-0.1
Consider the following rule in a Makefile:
tmp-tt-table.c: $(srcdir)/tag_tree.list tag_tree_build
# gcc -E tag_tree.list does not work, so use a .c name
-rm -f tmp-t1.c
cp $(srcdir)/tag_tree.list tmp-t1.c
$(CC) $(CFLAGS) -E tmp-t1.c > ./tmp-tag-tree-build1.tmp
LD_LIBRARY_PATH=$$LD_LIBRARY_PATH:$(LD_LIBRARY_PATH) ./tag_tree_build
-s -i tmp-tag-tree-build1.tmp -o tmp-tt-table.c
blhc produces the following output when fed with the resulting build
log:
CPPFLAGS missing (-D_FORTIFY_SOURCE=2): # gcc -E tag_tree.list does not work,
so use a .c name
CPPFLAGS missing (-D_FORTIFY_SOURCE=2): # gcc -E tag_attr.list does not work,
so use a .c name
CPPFLAGS missing (-D_FORTIFY_SOURCE=2): # gcc -E tag_attr_ext.list does not
work, so use a .c name
CPPFLAGS missing (-D_FORTIFY_SOURCE=2): # gcc -E tag_tree_ext.list does not
work, so use a .c name
These are obviously false positives since the referred lines are not
actual calls to gcc but merely comments in the Makefile.
Regards,
Fabian Wolff
