A sample configure session

Your session might look significantly different.
$ sh ./configure
creating cache ./config.cache
checking for gcc... gcc
checking whether the C compiler (gcc  ) works... yes
checking whether the C compiler (gcc  ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking for ranlib... ranlib
checking whether make sets ${MAKE}... yes
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/wait.h that is POSIX.1 compatible... yes
checking whether time.h and sys/time.h may both be included... yes
checking for string.h... yes
checking for fcntl.h... yes
checking for memory.h... yes
checking for malloc.h... yes
checking for unistd.h... yes
checking for ctype.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/param.h... yes
checking for sys/file.h... yes
checking for stdlib.h... yes
checking for working const... yes
checking whether struct tm is in sys/time.h or time.h... time.h
checking for flock... yes
checking for strcasecmp... yes
checking for mktime... yes
checking for ftruncate... yes
checking for SCO... checking for scosh... maybenot
updating cache ./config.cache
creating ./config.status
creating libs/bigplus/Makefile
creating libs/combine/Makefile
creating utils/mkstrip/Makefile
creating src/Makefile