help-gnutls
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Help-gnutls] Re: gnutls 2.3.4 doesn't copile using MinGW


From: Massimo Gaspari
Subject: [Help-gnutls] Re: gnutls 2.3.4 doesn't copile using MinGW
Date: Mon, 21 Apr 2008 22:17:21 +0200
User-agent: Thunderbird 2.0.0.12 (Windows/20080213)

Simon Josefsson wrote:
But please try latest 2.3.7 instead, it should contain all fixes.
  http://alpha.gnu.org/gnu/gnutls/gnutls-2.3.7.tar.bz2
  ftp://alpha.gnu.org/gnu/gnutls/gnutls-2.3.7.tar.bz2

/Simon

Ok, downloaded and configured as usual. GnuTLS compiles out of the box and make check is successful (no errors!).

I don't want to be a perfectionist but I am listing the few very minor issues.


1) a warning realted to vasprintf (an old friend , isn't it?)

/bin/sh ../libtool --tag=CC --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -DLOCALEDIR=\"/usr/local/share/locale\" -I../lgl -I../lgl -I../includes -I../includes -I./x509 -I../libextra -I../lib/openpgp/ -I/usr/local/include -I./opencdk -I../lib/opencdk -I./min itasn1 -I/usr/local/include -pipe -I/usr/local/include -O2 -Wno-pointer-sign -MT gnutls_str.lo -MD -MP -MF .deps/gnutls_str.Tpo -c -o
gnutls_str.lo gnutls_str.c
libtool: compile: gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -DLOCALEDIR=\"/usr/local/share/locale\" -I../lgl -I../lgl -I../includes -I.. /includes -I./x509 -I../libextra -I../lib/openpgp/ -I/usr/local/include -I./opencdk -I../lib/opencdk -I./minitasn1 -I/usr/local/include -pipe -I/usr/local/include -O2 -Wno-pointer-sign -MT gnutls_str.lo -MD -MP -MF .deps/gnutls_str.Tpo -c gnutls_str.c -o gnutls_str.o
gnutls_str.c: In function '_gnutls_string_append_printf':
gnutls_str.c:238: warning: implicit declaration of function 'vasprintf'


2) A warning related to inet_pton. In a previous e-mail you said

Problem in gnulib, I'll see if I can get these fixed.  I don't think
this is important though.

I usually think that an implicit declaration is always dangerous, but you are the expert!

/bin/sh ../../libtool --tag=CC --mode=compile gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I../../includes -I../../includes -I../../l gl -I../../lgl -I../../gl -I../../gl -I/usr/local/include -pipe -I/usr/local/include -O2 -Wno-pointer-sign -MT tcp.lo -MD -MP -MF .deps
/tcp.Tpo -c -o tcp.lo tcp.c
libtool: compile: gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I../../includes -I../../includes -I../../lgl -I../../lgl -I../../gl -I.. /../gl -I/usr/local/include -pipe -I/usr/local/include -O2 -Wno-pointer-sign -MT tcp.lo -MD -MP -MF .deps/tcp.Tpo -c tcp.c -o tcp.o
tcp.c: In function 'tcp_connect':
tcp.c:41: warning: implicit declaration of function 'inet_pton'

This warnig appears in some other files.

3)  A warning about 'setsockopt'.
In a previous e-mail you said

Probably a buggy system header file, the argument should be 'void*'
which should be castable from any type.

Uhm... in the MSDN documentation the 4th argument is const char* and in MinGW setsockopt is in winsock.h,winsock2.h and ws2spi.h. In all includes the 4th argument is const char*. May be in some other platform is void * but in Windows I think is definitively const char *.

libtool: link: gcc -std=gnu99 -pipe -I/usr/local/include -O2 -Wno-pointer-sign -o ex-serv1.exe ex-serv1.o ./.libs/libexamples.a ../../lib/.libs/libgnutls.a -L/usr/local/lib ../../libextra/.libs/libgnutls-extra.a /home/Massimo/gnutls-2.3.7/lib/.libs/libgnutls.a -lz -lws2_32 ../../gl/.libs/libgnu.a /usr/local/lib/libgcrypt.a /usr/local/lib/libgpg-error.a gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -I../../includes -I../../includes -I../../lgl -I../../lgl -I../../gl -I../../gl -I/usr/local/include -pipe -I/usr/local/include -O2 -Wno-pointer-sign -MT ex-serv-export.o -MD -MP -MF .deps/ex-serv-export.Tpo -c -o ex-serv-export.o ex-serv-export.c
ex-serv-export.c: In function 'main':
ex-serv-export.c:182: warning: passing argument 4 of 'setsockopt' from incompatible pointer type

4) several

libtool: link: warning: `-no-install' is ignored for i686-pc-mingw32
libtool: link: warning: assuming `-no-fast-install' instead

We can ignore those..


Hope this helps

Massimo






reply via email to

[Prev in Thread] Current Thread [Next in Thread]