build: Don't strip generated binaries

Except for some minor saving in disk space, stripping the binaries
doesn't bring any benefits and it might prevent us from getting usable
debugging information even from binaries build with DEBUG not set. Most
distributions will strip the binaries as part of their packaging process
anyhow.

If someone really wants stripped binaries as a result of the netsniff-ng
build, they could still add '-s' to CFLAGS or call strip manually.

Signed-off-by: Tobias Klauser <tklauser@distanz.ch>

3 files changed, 0 insertions, 17 deletions

diff --git a/Cmds b/Cmds
index fdb80ea..67d34cf 100644
--- a/Cmds
+++ b/Cmds
@@ -8,11 +8,6 @@ SHELL := $(shell if [ -x /bin/bash ]; then echo /bin/bash; else echo /bin/sh; fi
 LDQ = $(Q)echo -e "  LD\t$@" && $(CCACHE) $(CC)
 CCNQ = $(CCACHE) $(CC)
 CCQ = $(Q)echo -e "  CC\t$<" && $(CCNQ)
-ifeq ($(DEBUG), 1)
-  STRIPQ = $(Q)true
-else
-  STRIPQ = $(Q)echo -e "  STRIP\t$@" && $(STRIP)
-endif
 
 # sparse related
 C =
diff --git a/Makefile b/Makefile
index 6550e05..0dd349f 100644
--- a/Makefile
+++ b/Makefile
@@ -177,4 +177,3 @@ $(foreach tool,$(TOOLS),$(eval $(call TOOL_templ,$(tool))))
 
 $(TOOLS):
 	$(LDQ) $(LDFLAGS) -o $@/$@ $@/*.o $($@-libs)
-	$(STRIPQ) $@/$@
diff --git a/configure b/configure
index 30ad368..8956f0f 100755
--- a/configure
+++ b/configure
@@ -22,7 +22,6 @@ HAVE_TPACKET3=0
 
 [ -z "$CC" ] && CC="${CROSS_COMPILE}gcc"
 [ -z "$LD" ] && LD="${CROSS_COMPILE}gcc"
-[ -z "$STRIP" ] && STRIP="${CROSS_COMPILE}strip"
 if [ "x$SYSROOT" != "x" ] ; then
 	PKG_CONFIG_PATH="$SYSROOT/usr/lib/pkgconfig:$PKG_CONFIG_PATH"
 fi
@@ -85,16 +84,6 @@ check_toolchain()
 		echo "PKG_CONFIG=$PKG_CONFIG" >> Config
 		echo "PKG_CONFIG_PATH=$PKG_CONFIG_PATH" >> Config
 	fi
-
-	echo -n "[*] Checking $STRIP ... "
-	if [ "x$(which $STRIP 2>> config.log)" == "x" ] ; then
-		echo "[NO]"
-		MISSING_TOOLCHAIN=1
-	else
-		echo "[YES]"
-		echo "STRIP=$STRIP" >> Config
-	fi
-
 }
 
 check_flex()