Closed brunonaibert closed 3 years ago
@guyharris, would this be better?
--- a/Makefile.in
+++ b/Makefile.in
@@ -127,7 +127,7 @@ $(PROG): $(OBJ) @V_PCAPDEP@
$(CC) $(FULL_CFLAGS) $(LDFLAGS) -o $@ $(OBJ) $(LIBS)
version.o: version.c
- $(CC) $(CFLAGS) -c version.c
+ $(CC) $(FULL_CFLAGS) -c version.c
version.c: $(srcdir)/VERSION
@rm -f $@
@guyharris, would this be better?
--- a/Makefile.in +++ b/Makefile.in @@ -127,7 +127,7 @@ $(PROG): $(OBJ) @V_PCAPDEP@ $(CC) $(FULL_CFLAGS) $(LDFLAGS) -o $@ $(OBJ) $(LIBS) version.o: version.c - $(CC) $(CFLAGS) -c version.c + $(CC) $(FULL_CFLAGS) -c version.c version.c: $(srcdir)/VERSION @rm -f $@
Much better solution. Thanks. I modified it as suggested, ran the blhc and there were no warnings. It would be an interesting modification for a future version.
That should work.
(We do the version stuff differently now for libpcap and tcpdump, without a version.c file; it's set as PACKAGE_VERSION in config.h in the configure script.)
Found a better way to do it, this problem should be resolved now.
Nope, that was not better, committed a fix to the "fix", in the end the diff discussed above (with FULL_CFLAGS
) is the right fix.
The resolution is that the next release will have the change that the original requestor confirmed working. Closing.
During the compilation of the tcpslice .deb package I use blhc to check for hardening issues. Absence of CPPFLAGS was pointed out:
I don't know if it's the most suitable mode, I solved it with the following patch: