On 2015/11/11 19:07, Gleydson Soares wrote:
> ping... anyone?
> as usual, comments, tests, oks are welcome. // gsoares

there are a bunch of these during build on amd64:

/usr/obj/ports/stunnel-5.26/stunnel-5.26/src/client.c:251: warning: expected 
[error|warning|ignored] after '#pragma GCC diagnostic'
/usr/obj/ports/stunnel-5.26/stunnel-5.26/src/client.c: In function 'ssl_start':
/usr/obj/ports/stunnel-5.26/stunnel-5.26/src/client.c:381: warning: passing 
argument 3 of 'SSL_ctrl' with different width due to prototype
/usr/obj/ports/stunnel-5.26/stunnel-5.26/src/client.c:467: warning: passing 
argument 3 of 'SSL_ctrl' with different width due to prototype
/usr/obj/ports/stunnel-5.26/stunnel-5.26/src/client.c:469: warning: passing 
argument 3 of 'SSL_ctrl' with different width due to prototype
/usr/obj/ports/stunnel-5.26/stunnel-5.26/src/client.c: In function 'new_chain':
/usr/obj/ports/stunnel-5.26/stunnel-5.26/src/client.c:523: warning: passing 
argument 3 of 'BIO_ctrl' with different width due to prototype
/usr/obj/ports/stunnel-5.26/stunnel-5.26/src/client.c: In function 
'connect_local':
/usr/obj/ports/stunnel-5.26/stunnel-5.26/src/client.c:1157: warning: passing 
argument 2 of 'set_nonblock' with different width due to prototype
/usr/obj/ports/stunnel-5.26/stunnel-5.26/src/client.c: In function 'env_alloc':
/usr/obj/ports/stunnel-5.26/stunnel-5.26/src/client.c:1207: warning: passing 
argument 4 of 'getnameinfo' with different width due to prototype
/usr/obj/ports/stunnel-5.26/stunnel-5.26/src/client.c:1207: warning: passing 
argument 6 of 'getnameinfo' with different width due to prototype
/usr/obj/ports/stunnel-5.26/stunnel-5.26/src/client.c: In function 
'connect_index':
/usr/obj/ports/stunnel-5.26/stunnel-5.26/src/client.c:1337: warning: passing 
argument 3 of 'SSL_ctrl' with different width due to prototype
/usr/obj/ports/stunnel-5.26/stunnel-5.26/src/client.c: In function 'reset':

They're present in the old version too so I don't see a reason not to
update it, but it would be nice to figure out what's going on.

Reply via email to