Hi Sam,

thank you for this detailed answer. I will move forward and start to setup spamdyke on my new server - using it on a older one for years. Great code, thank you very much for the time and enegry you spent.
Best regards,
Arne

Am 19.08.2015 um 16:09 schrieb Sam Clippinger via spamdyke-users:
They're just warnings that I'm not checking the return value of a call to fscanf(). fscanf() reads data from a file into one or more variables; its return value shows how many variables were assigned. In the case of those lines, I'm using fscanf() to simply skip over any carriage return or newline characters at the end of a line and not assigning anything to any variables. That's why I'm not checking the return value -- I don't care about the actual data, I just want to move forward to the start of the next line. So the warnings are completely harmless.

But I don't like my code to generate warnings, so I'll get it fixed in the next version and add Ubuntu 14.04 to my list of test systems. Thanks for reporting this!

-- Sam Clippinger




On Aug 19, 2015, at 5:42 AM, Arne Metzger via spamdyke-users <spamdyke-users@spamdyke.org <mailto:spamdyke-users@spamdyke.org>> wrote:

Hi,

i am trying to make spamdyke on ubuntu 14.04. Make show several warnings

~/spamdyke-5.0.1/spamdyke# ./configure
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for stdint.h... (cached) yes
checking sys/inttypes.h usability... no
checking sys/inttypes.h presence... no
checking for sys/inttypes.h... no
checking for sys/types.h... (cached) yes
checking for stdint.h... (cached) yes
checking for sys/inttypes.h... (cached) no
checking whether time.h and sys/time.h may both be included... yes
checking for int16_t... no
checking for int32_t... no
checking for int64_t... no
checking for uint16_t... no
checking for uint32_t... no
checking for uint64_t... no
checking for dirent.h that defines DIR... yes
checking for library containing opendir... none required
checking for struct dirent.d_type... yes
checking whether DT_WHT is declared... yes
checking whether S_IFWHT is declared... no
checking whether INADDR_LOOPBACK is declared... yes
checking whether to include debugging symbols (for gdb)... no
checking for strip... strip spamdyke
checking whether to include excessive debugging output... no
checking whether to include some debugging output... yes
checking whether to compile with address sanitizer... no
checking whether to include configuration tests... yes
checking if openssl/ssl.h will include without additional include directories... yes
checking for library containing RSA_sign... -lcrypto
checking for library containing SSL_library_init... -lssl
checking for OpenSSL libraries (for TLS support)... yes
checking for library containing inet_aton... none required
checking for library containing bind... none required
checking for library containing inet_ntoa... none required
checking for library containing getopt_long... none required
checking whether anonymous inner functions are supported by default... yes
checking whether struct option is defined in getopt.h... yes
checking whether GCC diagnostic pragma directives are supported... yes
checking whether pid_t is an unsigned int or an unsigned long... unsigned int checking whether uid_t is an unsigned int or an unsigned long... unsigned int checking whether gid_t is an unsigned int or an unsigned long... unsigned int
checking whether time_t is an int or a long... long
checking whether int64_ts are supported in a test program... yes
checking whether printf()/scanf() uses %ld for 64-bit integers... yes
checking whether __func__ is available... yes
checking whether socklen_t is available... yes
checking whether RLIMIT_AS is available... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating config.h
config.status: config.h is unchanged

~/spamdyke-5.0.1/spamdyke# make
gcc -Wall -O2 -funsigned-char   -c spamdyke.c
gcc -E -Wall -O2 -funsigned-char configuration.c | gcc -Wall -O2 -funsigned-char -x c -c -o configuration.o -
gcc -Wall -O2 -funsigned-char   -c dns.c
gcc -Wall -O2 -funsigned-char   -c environment.c
gcc -Wall -O2 -funsigned-char   -c usage.c
gcc -Wall -O2 -funsigned-char   -c search_fs.c
search_fs.c: In function 'search_file':
search_fs.c:347:15: warning: ignoring return value of 'fscanf', declared with attribute warn_unused_result [-Wunused-result]
        fscanf(tmp_file, "%*1[\r\n]");
              ^
search_fs.c: In function 'search_tcprules_file':
search_fs.c:636:15: warning: ignoring return value of 'fscanf', declared with attribute warn_unused_result [-Wunused-result]
        fscanf(tmp_file, "%*1[\r\n]");
              ^
search_fs.c: In function 'load_resolver_file':
search_fs.c:820:15: warning: ignoring return value of 'fscanf', declared with attribute warn_unused_result [-Wunused-result]
        fscanf(tmp_file, "%*1[\r\n]");
              ^
search_fs.c: In function 'read_file':
search_fs.c:993:15: warning: ignoring return value of 'fscanf', declared with attribute warn_unused_result [-Wunused-result]
        fscanf(tmp_file, "%*1[\r\n]");
              ^
search_fs.c: In function 'search_header_file':
search_fs.c:1225:15: warning: ignoring return value of 'fscanf', declared with attribute warn_unused_result [-Wunused-result]
        fscanf(tmp_file, "%*1[\r\n]");
              ^
gcc -Wall -O2 -funsigned-char   -c exec.c
gcc -Wall -O2 -funsigned-char   -c base64.c
gcc -Wall -O2 -funsigned-char   -c tls.c
gcc -Wall -O2 -funsigned-char   -c log.c
gcc -Wall -O2 -funsigned-char   -c config_test.c
config_test.c: In function 'config_test_file_read':
config_test.c:234:15: warning: ignoring return value of 'fscanf', declared with attribute warn_unused_result [-Wunused-result]
        fscanf(tmp_file, "%" STRINGIFY(MAX_FILE_BUF) "[^\r\n]", tmp_buf);
              ^
config_test.c:235:15: warning: ignoring return value of 'fscanf', declared with attribute warn_unused_result [-Wunused-result]
        fscanf(tmp_file, "%*1[\r\n]");
              ^
config_test.c: In function 'config_test_file_read_write':
config_test.c:332:15: warning: ignoring return value of 'fscanf', declared with attribute warn_unused_result [-Wunused-result]
        fscanf(tmp_file, "%" STRINGIFY(MAX_FILE_BUF) "[^\r\n]", tmp_buf);
              ^
config_test.c:333:15: warning: ignoring return value of 'fscanf', declared with attribute warn_unused_result [-Wunused-result]
        fscanf(tmp_file, "%*1[\r\n]");
              ^
gcc -Wall -O2 -funsigned-char   -c md5.c
gcc -Wall -O2 -funsigned-char   -c filter.c
filter.c: In function 'check_ip_in_rdns_keyword':
filter.c:908:21: warning: ignoring return value of 'fscanf', declared with attribute warn_unused_result [-Wunused-result]
              fscanf(tmp_file, "%*1[\r\n]");
                    ^
gcc -Wall -O2 -funsigned-char   -c cdb.c
gcc -Wall -O2 -funsigned-char -o spamdyke spamdyke.o configuration.o dns.o environment.o usage.o search_fs.o exec.o base64.o tls.o log.o config_test.o md5.o filter.o cdb.o -lssl -lcrypto -lssl
strip spamdyke

Any hints on this issue?

Best regards,
Arne

_______________________________________________
spamdyke-users mailing list
spamdyke-users@spamdyke.org <mailto:spamdyke-users@spamdyke.org>
http://www.spamdyke.org/mailman/listinfo/spamdyke-users



_______________________________________________
spamdyke-users mailing list
spamdyke-users@spamdyke.org
http://www.spamdyke.org/mailman/listinfo/spamdyke-users

_______________________________________________
spamdyke-users mailing list
spamdyke-users@spamdyke.org
http://www.spamdyke.org/mailman/listinfo/spamdyke-users

Reply via email to