Drop gperftools-profiler configure switch

This switch is believed to be unnecessary. The possibility to use
gperftools CPU profiler was kept, one needs to set 'CFLAGS' and
'LDFLAGS' accordingly.

configure.ac

@@ -902,27 +902,6 @@ AS_CASE([$with_zlib],
 AC_SUBST([ZLIB_CFLAGS])
 AC_SUBST([ZLIB_LIBS])
 
-#
-# Google/Great Performance Tools CPU Profiler
-#
-AC_MSG_CHECKING(whether to use gperftools profiler)
-AC_ARG_WITH(gperftools-profiler,
-	    AS_HELP_STRING([--with-gperftools-profiler],
-			   [use gperftools CPU profiler]),
-	    use_profiler="$withval", use_profiler="no")
-
-case $use_profiler in
-	yes)
-		AC_MSG_RESULT(yes)
-		AC_DEFINE([HAVE_GPERFTOOLS_PROFILER], 1,
-		[Define to use gperftools CPU profiler.])
-		LIBS="$LIBS -lprofiler"
-		;;
-	*)
-		AC_MSG_RESULT(no)
-		;;
-esac
-
 #
 # Check if the system supports glibc-compatible backtrace() function.
 #

win32utils/Configure

@@ -2674,7 +2674,6 @@ exit 0;
 #  --with-json-c not supported on WIN32 (package not available on WIN32)
 #  --with-zlib supported
 #  --with-purify not supported (package available on WIN32 but for free?)
-#  --with-gperftools-profiler not supported (package not available on WIN32)
 #  --with-locktype not supported on WIN32 (not yet available on WIN32)
 #  --with-readline supported
 #  --with-protobuf-c not supported (no reason to until libfstrm is ready)