Hey Guys,
I'm trying to build stunnel 4.53 binaries for windows on Debian Squeeze x86 using instructions in INSTALL.W32 file. I use the latest openssl-1.0.1c (libssl-dev debian package installed also). At the last step 'make stunnel.exe' returns following error:
# make stunnel.exe i586-mingw32msvc-gcc -c -I/usr/src/openssl-0.9.8s-fips/inc32 -mthreads -fstack-protector -O2 -Wall -Wextra -Wno-long-long -pedantic -o str.obj str.c In file included from str.c:38: common.h:392:33: error: openssl/opensslconf.h: No such file or directory common.h:405:27: error: openssl/lhash.h: No such file or directory common.h:406:25: error: openssl/ssl.h: No such file or directory common.h:407:25: error: openssl/err.h: No such file or directory common.h:408:66: error: openssl/crypto.h: No such file or directory common.h:409:26: error: openssl/rand.h: No such file or directory common.h:411:25: error: openssl/md4.h: No such file or directory common.h:413:25: error: openssl/des.h: No such file or directory common.h:417:28: error: openssl/engine.h: No such file or directory In file included from str.c:38: common.h:449: warning: return type defaults to ‘int’ common.h: In function ‘STACK_OF’: common.h:449: error: expected declaration specifiers before ‘*’ token In file included from str.c:39: prototypes.h:50: error: storage class specified for parameter ‘LOG_MODE’ prototypes.h:61: error: storage class specified for parameter ‘SOCKADDR_UNION’ prototypes.h:64: error: expected specifier-qualifier-list before ‘SOCKADDR_UNION’ prototypes.h:67: warning: struct has no members prototypes.h:67: error: storage class specified for parameter ‘SOCKADDR_LIST’ prototypes.h:72: error: storage class specified for parameter ‘COMP_TYPE’ prototypes.h:78: error: expected specifier-qualifier-list before ‘COMP_TYPE’ prototypes.h:114: warning: struct has no members prototypes.h:114: error: storage class specified for parameter ‘GLOBAL_OPTIONS’ prototypes.h:116: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘global_options’ prototypes.h:124: error: expected specifier-qualifier-list before ‘SSL_CTX’ prototypes.h:222: error: storage class specified for parameter ‘SERVICE_OPTIONS’ prototypes.h:224: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘service_options’ prototypes.h:236: error: storage class specified for parameter ‘VAL_TYPE’ prototypes.h:244: error: storage class specified for parameter ‘OPT_UNION’ prototypes.h:250: error: expected specifier-qualifier-list before ‘VAL_TYPE’ prototypes.h:252: error: storage class specified for parameter ‘SOCK_OPT’ prototypes.h:256: error: storage class specified for parameter ‘CONF_TYPE’ prototypes.h:269: error: storage class specified for parameter ‘s_poll_set’ prototypes.h:278: error: storage class specified for parameter ‘DISK_FILE’ prototypes.h:285: error: storage class specified for parameter ‘FD’ prototypes.h:290: error: storage class specified for parameter ‘max_clients’ prototypes.h:291: error: storage class specified for parameter ‘num_clients’ prototypes.h:327: warning: parameter names (without types) in function declaration prototypes.h:347: error: storage class specified for parameter ‘cli_index’ prototypes.h:347: error: storage class specified for parameter ‘opt_index’ prototypes.h:350: error: expected ‘)’ before ‘*’ token prototypes.h:355: error: expected declaration specifiers or ‘...’ before ‘CONF_TYPE’ prototypes.h:361: error: expected specifier-qualifier-list before ‘SERVICE_OPTIONS’ prototypes.h:363: warning: struct has no members prototypes.h:363: error: storage class specified for parameter ‘UI_DATA’ prototypes.h:365: error: expected ‘)’ before ‘*’ token prototypes.h:370: error: expected ‘)’ before ‘*’ token prototypes.h:374: error: expected declaration specifiers before ‘s_poll_set’ prototypes.h:375: error: expected ‘)’ before ‘*’ token prototypes.h:376: error: expected ‘)’ before ‘*’ token prototypes.h:377: error: expected ‘)’ before ‘*’ token prototypes.h:378: error: expected ‘)’ before ‘*’ token prototypes.h:379: error: expected ‘)’ before ‘*’ token prototypes.h:380: error: expected ‘)’ before ‘*’ token prototypes.h:381: error: expected ‘)’ before ‘*’ token prototypes.h:401: error: expected specifier-qualifier-list before ‘SSL’ prototypes.h:422: error: storage class specified for parameter ‘CLI’ prototypes.h:424: error: expected declaration specifiers before ‘CLI’ prototypes.h:426: error: expected ‘)’ before ‘*’ token prototypes.h:430: error: expected ‘)’ before ‘*’ token prototypes.h:431: error: expected ‘)’ before ‘*’ token prototypes.h:432: error: expected ‘)’ before ‘*’ token prototypes.h:433: error: expected ‘)’ before ‘*’ token prototypes.h:434: error: expected ‘)’ before ‘*’ token prototypes.h:436: error: expected ‘)’ before ‘*’ token prototypes.h:450: error: storage class specified for parameter ‘PROTOCOL_TYPE’ prototypes.h:453: error: expected ‘)’ before ‘*’ token prototypes.h:457: error: expected ‘)’ before ‘*’ token prototypes.h:458: error: expected ‘)’ before ‘*’ token prototypes.h:459: error: expected ‘)’ before ‘*’ token prototypes.h:460: error: expected ‘)’ before ‘*’ token prototypes.h:461: error: expected ‘)’ before ‘*’ token prototypes.h:462: warning: type defaults to ‘int’ in declaration of ‘SOCKADDR_UNION’ prototypes.h:462: error: expected ‘;’, ‘,’ or ‘)’ before ‘*’ token prototypes.h:493: error: storage class specified for parameter ‘SECTION_CODE’ prototypes.h:495: warning: parameter names (without types) in function declaration prototypes.h:496: warning: parameter names (without types) in function declaration prototypes.h:500: error: expected declaration specifiers or ‘...’ before ‘CLI’ prototypes.h:526: error: storage class specified for parameter ‘hwnd’ prototypes.h:530: error: expected ‘)’ before ‘*’ token prototypes.h:535: error: storage class specified for parameter ‘GETADDRINFO’ prototypes.h:536: error: storage class specified for parameter ‘FREEADDRINFO’ prototypes.h:538: error: storage class specified for parameter ‘GETNAMEINFO’ prototypes.h:539: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘s_getaddrinfo’ prototypes.h:540: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘s_freeaddrinfo’ prototypes.h:541: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘s_getnameinfo’ prototypes.h:550: error: expected declaration specifiers before ‘DISK_FILE’ prototypes.h:551: error: expected ‘)’ before ‘*’ token prototypes.h:552: error: expected ‘)’ before ‘*’ token prototypes.h:553: error: expected ‘)’ before ‘*’ token prototypes.h:563: error: expected ‘)’ before ‘*’ token str.c:49: error: storage class specified for parameter ‘canary’ str.c:50: error: storage class specified for parameter ‘canary_initialized’ str.c:50: error: parameter ‘canary_initialized’ is initialized str.c:52: error: storage class specified for parameter ‘ALLOC_LIST’ str.c:55: error: expected specifier-qualifier-list before ‘ALLOC_LIST’ str.c:57: warning: struct has no members str.c:57: error: storage class specified for parameter ‘ALLOC_TLS’ str.c:60: error: expected specifier-qualifier-list before ‘ALLOC_LIST’ str.c:67: warning: struct has no members str.c:59: warning: empty declaration str.c:73: error: expected ‘)’ before ‘*’ token str.c:74: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token str.c:75: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token str.c:77: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token str.c:85: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token str.c:95: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token str.c:175: error: storage class specified for parameter ‘tls_index’ str.c:177: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token str.c:181: error: expected ‘)’ before ‘*’ token str.c:185: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token str.c:191: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token str.c:198: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token str.c:210: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token str.c:228: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token str.c:262: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token str.c:291: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token str.c:315: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘{’ token str.c:326: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘*’ token common.h:449: warning: type of ‘SSL_COMP’ defaults to ‘int’ str.c:175: error: declaration for parameter ‘tls_index’ but no such parameter str.c:57: error: declaration for parameter ‘ALLOC_TLS’ but no such parameter str.c:52: error: declaration for parameter ‘ALLOC_LIST’ but no such parameter str.c:50: error: declaration for parameter ‘canary_initialized’ but no such parameter str.c:49: error: declaration for parameter ‘canary’ but no such parameter prototypes.h:581: error: declaration for parameter ‘str_printf’ but no such parameter prototypes.h:580: error: declaration for parameter ‘str_vprintf’ but no such parameter prototypes.h:579: error: declaration for parameter ‘str_dup’ but no such parameter prototypes.h:577: error: declaration for parameter ‘str_free_debug’ but no such parameter prototypes.h:575: error: declaration for parameter ‘str_detach_debug’ but no such parameter prototypes.h:573: error: declaration for parameter ‘str_realloc_debug’ but no such parameter prototypes.h:571: error: declaration for parameter ‘str_alloc_debug’ but no such parameter prototypes.h:570: error: declaration for parameter ‘str_stats’ but no such parameter prototypes.h:569: error: declaration for parameter ‘str_cleanup’ but no such parameter prototypes.h:568: error: declaration for parameter ‘str_canary_init’ but no such parameter prototypes.h:567: error: declaration for parameter ‘str_init’ but no such parameter prototypes.h:562: error: declaration for parameter ‘libwrap_init’ but no such parameter prototypes.h:557: error: declaration for parameter ‘tstr2str’ but no such parameter prototypes.h:556: error: declaration for parameter ‘str2tstr’ but no such parameter prototypes.h:537: error: declaration for parameter ‘GETNAMEINFO’ but no such parameter prototypes.h:536: error: declaration for parameter ‘FREEADDRINFO’ but no such parameter prototypes.h:534: error: declaration for parameter ‘GETADDRINFO’ but no such parameter prototypes.h:528: error: declaration for parameter ‘passwd_cb’ but no such parameter prototypes.h:526: error: declaration for parameter ‘hwnd’ but no such parameter prototypes.h:500: error: declaration for parameter ‘create_client’ but no such parameter prototypes.h:499: error: declaration for parameter ‘stunnel_thread_id’ but no such parameter prototypes.h:498: error: declaration for parameter ‘stunnel_process_id’ but no such parameter prototypes.h:497: error: declaration for parameter ‘sthreads_init’ but no such parameter prototypes.h:496: error: declaration for parameter ‘leave_critical_section’ but no such parameter prototypes.h:495: error: declaration for parameter ‘enter_critical_section’ but no such parameter prototypes.h:493: error: declaration for parameter ‘SECTION_CODE’ but no such parameter prototypes.h:479: error: declaration for parameter ‘local_getnameinfo’ but no such parameter prototypes.h:463: error: declaration for parameter ‘s_gai_strerror’ but no such parameter prototypes.h:452: error: declaration for parameter ‘find_protocol_id’ but no such parameter prototypes.h:450: error: declaration for parameter ‘PROTOCOL_TYPE’ but no such parameter prototypes.h:425: error: declaration for parameter ‘client_thread’ but no such parameter prototypes.h:422: error: declaration for parameter ‘CLI’ but no such parameter prototypes.h:395: error: declaration for parameter ‘make_sockets’ but no such parameter prototypes.h:394: error: declaration for parameter ‘get_socket_error’ but no such parameter prototypes.h:393: error: declaration for parameter ‘set_socket_options’ but no such parameter prototypes.h:366: error: declaration for parameter ‘sslerror’ but no such parameter prototypes.h:363: error: declaration for parameter ‘UI_DATA’ but no such parameter prototypes.h:356: error: declaration for parameter ‘apply_conf’ but no such parameter prototypes.h:355: error: declaration for parameter ‘parse_conf’ but no such parameter prototypes.h:354: error: declaration for parameter ‘parse_commandline’ but no such parameter prototypes.h:349: error: declaration for parameter ‘ssl_init’ but no such parameter prototypes.h:347: error: declaration for parameter ‘opt_index’ but no such parameter prototypes.h:347: error: declaration for parameter ‘cli_index’ but no such parameter prototypes.h:343: error: declaration for parameter ‘pty_allocate’ but no such parameter prototypes.h:339: error: declaration for parameter ‘s_strerror’ but no such parameter prototypes.h:338: error: declaration for parameter ‘log_error’ but no such parameter prototypes.h:337: error: declaration for parameter ‘sockerror’ but no such parameter prototypes.h:336: error: declaration for parameter ‘ioerror’ but no such parameter prototypes.h:334: error: declaration for parameter ‘fatal_debug’ but no such parameter prototypes.h:328: error: declaration for parameter ‘s_log’ but no such parameter prototypes.h:327: error: declaration for parameter ‘log_flush’ but no such parameter prototypes.h:326: error: declaration for parameter ‘log_close’ but no such parameter prototypes.h:325: error: declaration for parameter ‘log_open’ but no such parameter prototypes.h:317: error: declaration for parameter ‘set_nonblock’ but no such parameter prototypes.h:316: error: declaration for parameter ‘s_accept’ but no such parameter prototypes.h:315: error: declaration for parameter ‘s_socketpair’ but no such parameter prototypes.h:314: error: declaration for parameter ‘s_pipe’ but no such parameter prototypes.h:313: error: declaration for parameter ‘s_socket’ but no such parameter prototypes.h:311: error: declaration for parameter ‘get_limits’ but no such parameter prototypes.h:306: error: declaration for parameter ‘stunnel_info’ but no such parameter prototypes.h:302: error: declaration for parameter ‘signal_post’ but no such parameter prototypes.h:298: error: declaration for parameter ‘bind_ports’ but no such parameter prototypes.h:297: error: declaration for parameter ‘unbind_ports’ but no such parameter prototypes.h:296: error: declaration for parameter ‘daemon_loop’ but no such parameter prototypes.h:295: error: declaration for parameter ‘main_configure’ but no such parameter prototypes.h:294: error: declaration for parameter ‘main_initialize’ but no such parameter prototypes.h:291: error: declaration for parameter ‘num_clients’ but no such parameter prototypes.h:290: error: declaration for parameter ‘max_clients’ but no such parameter prototypes.h:285: error: declaration for parameter ‘FD’ but no such parameter prototypes.h:278: error: declaration for parameter ‘DISK_FILE’ but no such parameter prototypes.h:269: error: declaration for parameter ‘s_poll_set’ but no such parameter prototypes.h:256: error: declaration for parameter ‘CONF_TYPE’ but no such parameter prototypes.h:252: error: declaration for parameter ‘SOCK_OPT’ but no such parameter prototypes.h:244: error: declaration for parameter ‘OPT_UNION’ but no such parameter prototypes.h:236: error: declaration for parameter ‘VAL_TYPE’ but no such parameter prototypes.h:222: error: declaration for parameter ‘SERVICE_OPTIONS’ but no such parameter prototypes.h:114: error: declaration for parameter ‘GLOBAL_OPTIONS’ but no such parameter prototypes.h:72: error: declaration for parameter ‘COMP_TYPE’ but no such parameter prototypes.h:67: error: declaration for parameter ‘SOCKADDR_LIST’ but no such parameter prototypes.h:61: error: declaration for parameter ‘SOCKADDR_UNION’ but no such parameter prototypes.h:50: error: declaration for parameter ‘LOG_MODE’ but no such parameter str.c:342: error: expected ‘{’ at end of input common.h:449: warning: unused parameter ‘SSL_COMP’ str.c:175: warning: unused parameter ‘tls_index’ str.c:57: warning: unused parameter ‘ALLOC_TLS’ str.c:52: warning: unused parameter ‘ALLOC_LIST’ str.c:50: warning: unused parameter ‘canary_initialized’ str.c:49: warning: unused parameter ‘canary’ prototypes.h:581: warning: unused parameter ‘str_printf’ prototypes.h:580: warning: unused parameter ‘str_vprintf’ prototypes.h:579: warning: unused parameter ‘str_dup’ prototypes.h:577: warning: unused parameter ‘str_free_debug’ prototypes.h:575: warning: unused parameter ‘str_detach_debug’ prototypes.h:573: warning: unused parameter ‘str_realloc_debug’ prototypes.h:571: warning: unused parameter ‘str_alloc_debug’ prototypes.h:570: warning: unused parameter ‘str_stats’ prototypes.h:569: warning: unused parameter ‘str_cleanup’ prototypes.h:568: warning: unused parameter ‘str_canary_init’ prototypes.h:567: warning: unused parameter ‘str_init’ prototypes.h:562: warning: unused parameter ‘libwrap_init’ prototypes.h:557: warning: unused parameter ‘tstr2str’ prototypes.h:556: warning: unused parameter ‘str2tstr’ prototypes.h:537: warning: unused parameter ‘GETNAMEINFO’ prototypes.h:536: warning: unused parameter ‘FREEADDRINFO’ prototypes.h:534: warning: unused parameter ‘GETADDRINFO’ prototypes.h:528: warning: unused parameter ‘passwd_cb’ prototypes.h:526: warning: unused parameter ‘hwnd’ prototypes.h:500: warning: unused parameter ‘create_client’ prototypes.h:499: warning: unused parameter ‘stunnel_thread_id’ prototypes.h:498: warning: unused parameter ‘stunnel_process_id’ prototypes.h:497: warning: unused parameter ‘sthreads_init’ prototypes.h:496: warning: unused parameter ‘leave_critical_section’ prototypes.h:495: warning: unused parameter ‘enter_critical_section’ prototypes.h:493: warning: unused parameter ‘SECTION_CODE’ prototypes.h:479: warning: unused parameter ‘local_getnameinfo’ prototypes.h:463: warning: unused parameter ‘s_gai_strerror’ prototypes.h:452: warning: unused parameter ‘find_protocol_id’ prototypes.h:450: warning: unused parameter ‘PROTOCOL_TYPE’ prototypes.h:425: warning: unused parameter ‘client_thread’ prototypes.h:422: warning: unused parameter ‘CLI’ prototypes.h:395: warning: unused parameter ‘make_sockets’ prototypes.h:394: warning: unused parameter ‘get_socket_error’ prototypes.h:393: warning: unused parameter ‘set_socket_options’ prototypes.h:366: warning: unused parameter ‘sslerror’ prototypes.h:363: warning: unused parameter ‘UI_DATA’ prototypes.h:356: warning: unused parameter ‘apply_conf’ prototypes.h:355: warning: unused parameter ‘parse_conf’ prototypes.h:354: warning: unused parameter ‘parse_commandline’ prototypes.h:349: warning: unused parameter ‘ssl_init’ prototypes.h:347: warning: unused parameter ‘opt_index’ prototypes.h:347: warning: unused parameter ‘cli_index’ prototypes.h:343: warning: unused parameter ‘pty_allocate’ prototypes.h:339: warning: unused parameter ‘s_strerror’ prototypes.h:338: warning: unused parameter ‘log_error’ prototypes.h:337: warning: unused parameter ‘sockerror’ prototypes.h:336: warning: unused parameter ‘ioerror’ prototypes.h:334: warning: unused parameter ‘fatal_debug’ prototypes.h:328: warning: unused parameter ‘s_log’ prototypes.h:327: warning: unused parameter ‘log_flush’ prototypes.h:326: warning: unused parameter ‘log_close’ prototypes.h:325: warning: unused parameter ‘log_open’ prototypes.h:317: warning: unused parameter ‘set_nonblock’ prototypes.h:316: warning: unused parameter ‘s_accept’ prototypes.h:315: warning: unused parameter ‘s_socketpair’ prototypes.h:314: warning: unused parameter ‘s_pipe’ prototypes.h:313: warning: unused parameter ‘s_socket’ prototypes.h:311: warning: unused parameter ‘get_limits’ prototypes.h:306: warning: unused parameter ‘stunnel_info’ prototypes.h:302: warning: unused parameter ‘signal_post’ prototypes.h:298: warning: unused parameter ‘bind_ports’ prototypes.h:297: warning: unused parameter ‘unbind_ports’ prototypes.h:296: warning: unused parameter ‘daemon_loop’ prototypes.h:295: warning: unused parameter ‘main_configure’ prototypes.h:294: warning: unused parameter ‘main_initialize’ prototypes.h:291: warning: unused parameter ‘num_clients’ prototypes.h:290: warning: unused parameter ‘max_clients’ prototypes.h:285: warning: unused parameter ‘FD’ prototypes.h:278: warning: unused parameter ‘DISK_FILE’ prototypes.h:269: warning: unused parameter ‘s_poll_set’ prototypes.h:256: warning: unused parameter ‘CONF_TYPE’ prototypes.h:252: warning: unused parameter ‘SOCK_OPT’ prototypes.h:244: warning: unused parameter ‘OPT_UNION’ prototypes.h:236: warning: unused parameter ‘VAL_TYPE’ prototypes.h:222: warning: unused parameter ‘SERVICE_OPTIONS’ prototypes.h:114: warning: unused parameter ‘GLOBAL_OPTIONS’ prototypes.h:72: warning: unused parameter ‘COMP_TYPE’ prototypes.h:67: warning: unused parameter ‘SOCKADDR_LIST’ prototypes.h:61: warning: unused parameter ‘SOCKADDR_UNION’ prototypes.h:50: warning: unused parameter ‘LOG_MODE’ make: *** [str.obj] Error 1
It seems it has hardcoded path to openssl (/usr/src/openssl-0.9.8s-fips). I tried to change this path to the right one in Makefile*, but with no luck - I get the same error.
I also tried to build stunnel with openssl-0.9.8s, but openssl configure command from the instruction doesn't work: root@debian:/usr/src/openssl-0.9.8s-i586# ./Configure --cross-compile-prefix=i586-mingw32msvc- mingw shared zlib-dynamic Usage: Configure [no-<cipher> ...] [enable-<cipher> ...] [experimental-<cipher> ...] [-Dxxx] [-lxxx] [-Lxxx] [-fxxx] [-Kxxx] [no-hw-xxx|no-hw] [[no-]threads] [[no-]shared] [[no-]zlib|zlib-dynamic] [enable-montasm] [no-asm] [no-dso] [no-krb5] [386] [--prefix=DIR] [--openssldir=OPENSSLDIR] [--with-xxx[=vvv]] [--test-sanity] os/compiler[:flags]
Regards, Anton.
Anton,
Ahh... The joys of cross compiling!
You cross compiled your openssl 1.01c for mingw32, right? Or you installed the mingw32 version. Try passing the path of your mingw32 openssl includes and libs to stunnel configure:
--with-openssl*=
Do configure --help to see the exact syntax.
Let us know how it goes. -----Original Message----- From: Anton Tkachev [email protected] Sender: [email protected] Date: Fri, 20 Jul 2012 16:28:57 To: [email protected] Subject: [stunnel-users] Build stunnel 4.53 binaries for windows error
_______________________________________________ stunnel-users mailing list [email protected] http://stunnel.mirt.net/mailman/listinfo/stunnel-users
Hey Jose, Thank you for your response!
You cross compiled your openssl 1.01c for mingw32, right?
Yes, I used ./Configure --cross-compile-prefix=i586-mingw32msvc- mingw shared zlib-dynamic command.
Try passing the path of your mingw32 openssl includes and libs to stunnel
configure:
--with-openssl*=
Do configure --help to see the exact syntax.
Do you mean ./configure --with-ssl=/usr/src/openssl-1.0.1c-i586 --includedir=/usr/i586-mingw32msvc/include --libdir=/usr/i586-mingw32msvc/lib ? Unfortunately 'make stunnel.exe' returns the same error in this case.
2012/7/20 [email protected]
Anton,
Ahh... The joys of cross compiling!
You cross compiled your openssl 1.01c for mingw32, right? Or you installed the mingw32 version. Try passing the path of your mingw32 openssl includes and libs to stunnel configure:
--with-openssl*=
Do configure --help to see the exact syntax.
Let us know how it goes. -----Original Message----- From: Anton Tkachev [email protected] Sender: [email protected] Date: Fri, 20 Jul 2012 16:28:57 To: [email protected] Subject: [stunnel-users] Build stunnel 4.53 binaries for windows error
stunnel-users mailing list [email protected] http://stunnel.mirt.net/mailman/listinfo/stunnel-users
Anton,
Does the ./configure script under stunnel-4.53 finish OK? I also think that you should pass a parameter to force the cross compilation of stunnel. It could be using the default system compiler. Maybe set CC, GCC environment vars to point to the cross compiler path before running ./configure: eg
export CC=/usr/pathtomingwgcc/bin/gcc
Enjoy!
-----Original Message----- From: Anton Tkachev [email protected] Date: Fri, 20 Jul 2012 21:44:09 To: [email protected] Cc: [email protected]; [email protected] Subject: Re: [stunnel-users] Build stunnel 4.53 binaries for windows error
Hey Jose, Thank you for your response!
You cross compiled your openssl 1.01c for mingw32, right?
Yes, I used ./Configure --cross-compile-prefix=i586-mingw32msvc- mingw shared zlib-dynamic command.
Try passing the path of your mingw32 openssl includes and libs to stunnel
configure:
--with-openssl*=
Do configure --help to see the exact syntax.
Do you mean ./configure --with-ssl=/usr/src/openssl-1.0.1c-i586 --includedir=/usr/i586-mingw32msvc/include --libdir=/usr/i586-mingw32msvc/lib ? Unfortunately 'make stunnel.exe' returns the same error in this case.
2012/7/20 [email protected]
Anton,
Ahh... The joys of cross compiling!
You cross compiled your openssl 1.01c for mingw32, right? Or you installed the mingw32 version. Try passing the path of your mingw32 openssl includes and libs to stunnel configure:
--with-openssl*=
Do configure --help to see the exact syntax.
Let us know how it goes. -----Original Message----- From: Anton Tkachev [email protected] Sender: [email protected] Date: Fri, 20 Jul 2012 16:28:57 To: [email protected] Subject: [stunnel-users] Build stunnel 4.53 binaries for windows error
stunnel-users mailing list [email protected] http://stunnel.mirt.net/mailman/listinfo/stunnel-users
Does the ./configure script under stunnel-4.53 finish OK?
Yes. No errors at this step.
I also think that you should pass a parameter to force the cross
compilation of stunnel. It could be using the default system compiler. Maybe set CC, GCC environment vars to point to the cross compiler path before running ./configure: eg
export CC=/usr/pathtomingwgcc/bin/gcc
My mingw installation doesn't have any compiler.
I think the problem in openssl path, because error message is: # make stunnel.exe i586-mingw32msvc-gcc -c -I/usr/src/openssl-1.0.0f-i586/include -mthreads -fstack-protector -O2 -Wall -Wextra -Wno-long-long -pedantic -o str.obj str.c In file included from str.c:38: common.h:392:33: error: openssl/opensslconf.h: No such file or directory common.h:405:27: error: openssl/lhash.h: No such file or directory common.h:406:25: error: openssl/ssl.h: No such file or directory ...
These files exist in /usr/src/openssl-1.0.0f-i586/include/openssl directory, but building doesn't work anyway...
2012/7/20 [email protected]
** Anton,
Does the ./configure script under stunnel-4.53 finish OK? I also think that you should pass a parameter to force the cross compilation of stunnel. It could be using the default system compiler. Maybe set CC, GCC environment vars to point to the cross compiler path before running ./configure: eg
export CC=/usr/pathtomingwgcc/bin/gcc
Enjoy!
*From: * Anton Tkachev [email protected] *Date: *Fri, 20 Jul 2012 21:44:09 +0700 *To: *[email protected] *Cc: *[email protected]; [email protected] *Subject: *Re: [stunnel-users] Build stunnel 4.53 binaries for windows error
Hey Jose, Thank you for your response!
You cross compiled your openssl 1.01c for mingw32, right?
Yes, I used ./Configure --cross-compile-prefix=i586-mingw32msvc- mingw shared zlib-dynamic command.
Try passing the path of your mingw32 openssl includes and libs to
stunnel configure:
--with-openssl*=
Do configure --help to see the exact syntax.
Do you mean ./configure --with-ssl=/usr/src/openssl-1.0.1c-i586 --includedir=/usr/i586-mingw32msvc/include --libdir=/usr/i586-mingw32msvc/lib ? Unfortunately 'make stunnel.exe' returns the same error in this case.
2012/7/20 [email protected]
Anton,
Ahh... The joys of cross compiling!
You cross compiled your openssl 1.01c for mingw32, right? Or you installed the mingw32 version. Try passing the path of your mingw32 openssl includes and libs to stunnel configure:
--with-openssl*=
Do configure --help to see the exact syntax.
Let us know how it goes. -----Original Message----- From: Anton Tkachev [email protected] Sender: [email protected] Date: Fri, 20 Jul 2012 16:28:57 To: [email protected] Subject: [stunnel-users] Build stunnel 4.53 binaries for windows error
stunnel-users mailing list [email protected] http://stunnel.mirt.net/mailman/listinfo/stunnel-users
Anton, I usually compile my stunnel under windows (mingw). I tested with Debian Squeeze installation and I found the same problem. In step 6, ./configure finish fine, but the Make step does not work. I checked and I found the included directories are not th right ones. I will take a look later this week. Mich, Any suggestions?
Regards Jose
________________________________ From: Anton Tkachev [email protected] To: [email protected] Cc: [email protected]; [email protected] Sent: Monday, July 23, 2012 7:11 AM Subject: Re: [stunnel-users] Build stunnel 4.53 binaries for windows error
Does the ./configure script under stunnel-4.53 finish OK?
Yes. No errors at this step.
I also think that you should pass a parameter to force the cross
compilation of stunnel. It could be using the default system compiler. Maybe set CC, GCC environment vars to point to the cross compiler path before running ./configure: eg
export CC=/usr/pathtomingwgcc/bin/gcc
My mingw installation doesn't have any compiler.
I think the problem in openssl path, because error message is: # make stunnel.exe i586-mingw32msvc-gcc -c -I/usr/src/openssl-1.0.0f-i586/include -mthreads -fstack-protector -O2 -Wall -Wextra -Wno-long-long -pedantic -o str.obj str.c In file included from str.c:38: common.h:392:33: error: openssl/opensslconf.h: No such file or directory common.h:405:27: error: openssl/lhash.h: No such file or directory common.h:406:25: error: openssl/ssl.h: No such file or directory ...
These files exist in /usr/src/openssl-1.0.0f-i586/include/openssl directory, but building doesn't work anyway...
2012/7/20 [email protected]
Anton,
Does the ./configure script under stunnel-4.53 finish OK? I also think that you should pass a parameter to force the cross compilation of stunnel. It could be using the default system compiler. Maybe set CC, GCC environment vars to point to the cross compiler path before running ./configure: eg
export CC=/usr/pathtomingwgcc/bin/gcc
Enjoy!
From: Anton Tkachev [email protected] Date: Fri, 20 Jul 2012 21:44:09 +0700 To: [email protected] Cc: [email protected]; [email protected] Subject: Re: [stunnel-users] Build stunnel 4.53 binaries for windows error
Hey Jose, Thank you for your response!
You cross compiled your openssl 1.01c for mingw32, right?
Yes, I used ./Configure --cross-compile-prefix=i586-mingw32msvc- mingw shared zlib-dynamic command.
Try passing the path of your mingw32 openssl includes and libs to stunnel configure:
--with-openssl*=
Do configure --help to see the exact syntax.
Do you mean ./configure --with-ssl=/usr/src/openssl-1.0.1c-i586 --includedir=/usr/i586-mingw32msvc/include --libdir=/usr/i586-mingw32msvc/lib ? Unfortunately 'make stunnel.exe' returns the same error in this case.
2012/7/20 [email protected]
Anton,
Ahh... The joys of cross compiling!
You cross compiled your openssl 1.01c for mingw32, right? Or you installed the mingw32 version. Try passing the path of your mingw32 openssl includes and libs to stunnel configure:
--with-openssl*=
Do configure --help to see the exact syntax.
Let us know how it goes. -----Original Message----- From: Anton Tkachev [email protected] Sender: [email protected] Date: Fri, 20 Jul 2012 16:28:57 To: [email protected] Subject: [stunnel-users] Build stunnel 4.53 binaries for windows error
stunnel-users mailing list [email protected] http://stunnel.mirt.net/mailman/listinfo/stunnel-users
Hey Jose,
Could you just share your build inctructions under windows? If it works, fine - I can use windows too :)
Thank you, Anton.
2012/7/24 Jose Alf. [email protected]
Anton,
I usually compile my stunnel under windows (mingw). I tested with Debian Squeeze installation and I found the same problem. In step 6, ./configure finish fine, but the Make step does not work.
I checked and I found the included directories are not th right ones. I will take a look later this week.
Mich,
Any suggestions? Regards Jose *From:* Anton Tkachev [email protected] *To:* [email protected] *Cc:* [email protected]; [email protected] *Sent:* Monday, July 23, 2012 7:11 AM *Subject:* Re: [stunnel-users] Build stunnel 4.53 binaries for windows error
Does the ./configure script under stunnel-4.53 finish OK?
Yes. No errors at this step.
I also think that you should pass a parameter to force the cross
compilation of stunnel. It could be using the default system compiler. Maybe set CC, GCC environment vars to point to the cross compiler path before running ./configure: eg
export CC=/usr/pathtomingwgcc/bin/gcc
My mingw installation doesn't have any compiler.
I think the problem in openssl path, because error message is: # make stunnel.exe i586-mingw32msvc-gcc -c -I/usr/src/openssl-1.0.0f-i586/include -mthreads -fstack-protector -O2 -Wall -Wextra -Wno-long-long -pedantic -o str.obj str.c In file included from str.c:38: common.h:392:33: error: openssl/opensslconf.h: No such file or directory common.h:405:27: error: openssl/lhash.h: No such file or directory common.h:406:25: error: openssl/ssl.h: No such file or directory ...
These files exist in /usr/src/openssl-1.0.0f-i586/include/openssl directory, but building doesn't work anyway...
2012/7/20 [email protected]
** Anton,
Does the ./configure script under stunnel-4.53 finish OK? I also think that you should pass a parameter to force the cross compilation of stunnel. It could be using the default system compiler. Maybe set CC, GCC environment vars to point to the cross compiler path before running ./configure: eg
export CC=/usr/pathtomingwgcc/bin/gcc
Enjoy! *From: * Anton Tkachev [email protected] *Date: *Fri, 20 Jul 2012 21:44:09 +0700 *To: *[email protected] *Cc: *[email protected]; [email protected] *Subject: *Re: [stunnel-users] Build stunnel 4.53 binaries for windows error
Hey Jose, Thank you for your response!
You cross compiled your openssl 1.01c for mingw32, right?
Yes, I used ./Configure --cross-compile-prefix=i586-mingw32msvc- mingw shared zlib-dynamic command.
Try passing the path of your mingw32 openssl includes and libs to
stunnel configure:
--with-openssl*=
Do configure --help to see the exact syntax.
Do you mean ./configure --with-ssl=/usr/src/openssl-1.0.1c-i586 --includedir=/usr/i586-mingw32msvc/include --libdir=/usr/i586-mingw32msvc/lib ? Unfortunately 'make stunnel.exe' returns the same error in this case.
2012/7/20 [email protected]
Anton,
Ahh... The joys of cross compiling!
You cross compiled your openssl 1.01c for mingw32, right? Or you installed the mingw32 version. Try passing the path of your mingw32 openssl includes and libs to stunnel configure:
--with-openssl*=
Do configure --help to see the exact syntax.
Let us know how it goes. -----Original Message----- From: Anton Tkachev [email protected] Sender: [email protected] Date: Fri, 20 Jul 2012 16:28:57 To: [email protected] Subject: [stunnel-users] Build stunnel 4.53 binaries for windows error
stunnel-users mailing list [email protected] http://stunnel.mirt.net/mailman/listinfo/stunnel-users
Anton, Actually, I managed to compile it under Debian. We were doing it wrong. We must use the same method I use under Windows :) 1. Go to the src directory and edit the file mingw.mak. Set variables CC, RC, RCP as needed. I attach mine for you. 2. From src, execute make -f mingw.mak 3. If everything's fine, you'll find stunnel.exe in bin/MGW32 Time ti update the docs? regards Jose
________________________________ From: Anton Tkachev [email protected] To: Jose Alf. [email protected] Cc: "[email protected]" [email protected]; "[email protected]" [email protected] Sent: Tuesday, July 31, 2012 2:39 AM Subject: Re: [stunnel-users] Build stunnel 4.53 binaries for windows error
Hey Jose,
Could you just share your build inctructions under windows? If it works, fine - I can use windows too :)
Thank you, Anton.
2012/7/24 Jose Alf. [email protected]
Anton,
I usually compile my stunnel under windows (mingw). I tested with Debian Squeeze installation and I found the same problem. In step 6, ./configure finish fine, but the Make step does not work.
I checked and I found the included directories are not th right ones. I will take a look later this week.
Mich,
Any suggestions?
Regards Jose From: Anton Tkachev [email protected] To: [email protected] Cc: [email protected]; [email protected] Sent: Monday, July 23, 2012 7:11 AM Subject: Re: [stunnel-users] Build stunnel 4.53 binaries for windows error
Does the ./configure script under stunnel-4.53 finish OK?
Yes. No errors at this step.
I also think that you should pass a parameter to force the cross
compilation of stunnel. It could be using the default system compiler. Maybe set CC, GCC environment vars to point to the cross compiler path before running ./configure: eg
export CC=/usr/pathtomingwgcc/bin/gcc
My mingw installation doesn't have any compiler.
I think the problem in openssl path, because error message is: # make stunnel.exe i586-mingw32msvc-gcc -c -I/usr/src/openssl-1.0.0f-i586/include -mthreads -fstack-protector -O2 -Wall -Wextra -Wno-long-long -pedantic -o str.obj str.c In file included from str.c:38: common.h:392:33: error: openssl/opensslconf.h: No such file or directory common.h:405:27: error: openssl/lhash.h: No such file or directory common.h:406:25: error: openssl/ssl.h: No such file or directory ...
These files exist in /usr/src/openssl-1.0.0f-i586/include/openssl directory, but building doesn't work anyway...
2012/7/20 [email protected]
Anton,
Does the ./configure script under stunnel-4.53 finish OK? I also think that you should pass a parameter to force the cross compilation of stunnel. It could be using the default system compiler. Maybe set CC, GCC environment vars to point to the cross compiler path before running ./configure: eg
export CC=/usr/pathtomingwgcc/bin/gcc
Enjoy!
From: Anton Tkachev [email protected] Date: Fri, 20 Jul 2012 21:44:09 +0700 To: [email protected] Cc: [email protected]; [email protected] Subject: Re: [stunnel-users] Build stunnel 4.53 binaries for windows error
Hey Jose, Thank you for your response!
You cross compiled your openssl 1.01c for mingw32, right?
Yes, I used ./Configure --cross-compile-prefix=i586-mingw32msvc- mingw shared zlib-dynamic command.
Try passing the path of your mingw32 openssl includes and libs to stunnel configure:
--with-openssl*=
Do configure --help to see the exact syntax.
Do you mean ./configure --with-ssl=/usr/src/openssl-1.0.1c-i586 --includedir=/usr/i586-mingw32msvc/include --libdir=/usr/i586-mingw32msvc/lib ? Unfortunately 'make stunnel.exe' returns the same error in this case.
2012/7/20 [email protected]
Anton,
Ahh... The joys of cross compiling!
You cross compiled your openssl 1.01c for mingw32, right? Or you installed the mingw32 version. Try passing the path of your mingw32 openssl includes and libs to stunnel configure:
--with-openssl*=
Do configure --help to see the exact syntax.
Let us know how it goes. -----Original Message----- From: Anton Tkachev [email protected] Sender: [email protected] Date: Fri, 20 Jul 2012 16:28:57 To: [email protected] Subject: [stunnel-users] Build stunnel 4.53 binaries for windows error
stunnel-users mailing list [email protected] http://stunnel.mirt.net/mailman/listinfo/stunnel-users
I used the same openssl version: 1.0.0h I had to change also CFLAGS in mingw.mak from CFLAGS=-g -O2 -Wall $(DEFINES) -I$(SSLDIR)/inc32 to CFLAGS=-g -O2 -Wall $(DEFINES) -I$(SSLDIR)/include because folder inc32 doesn't exist.
Now when I run make -f mingw.mak I get the following error: # make -f mingw.mak host machine is a linux machine make: [makedirs] Error 1 (ignored) make: [makedirs] Error 1 (ignored) make: [makedirs] Error 1 (ignored) make: [makedirs] Error 1 (ignored) /usr/bin/i586-mingw32msvc-gcc -g -O2 -Wall -D_WIN32_WINNT=0x0501 -I/usr/src/openssl-1.0.0h/include -o../obj/MGW32/stunnel.o -c ../src/stunnel.c ../src/stunnel.c:44: warning: expected [error|warning|ignored] after ‘#pragma GCC diagnostic’ *../src/stunnel.c:47:29: error: openssl/applink.c: No such file or directory * ../src/stunnel.c:49: warning: expected [error|warning|ignored] after ‘#pragma GCC diagnostic’ make: *** [../obj/MGW32/stunnel.o] Error 1
How do you configure openssl and stunnel? ./Configure --cross-compile-prefix=i586-mingw32msvc- mingw shared zlib-dynamic and ./configure --with-ssl=/usr/src/openssl-1.0.0h ?
2012/8/1 Jose Alf. [email protected]
Anton,
Actually, I managed to compile it under Debian. We were doing it wrong. We must use the same method I use under Windows :)
- Go to the src directory and edit the file mingw.mak. Set variables CC,
RC, RCP as needed. I attach mine for you. 2. From src, execute make -f mingw.mak 3. If everything's fine, you'll find stunnel.exe in bin/MGW32
Time ti update the docs? regards Jose
*From:* Anton Tkachev [email protected] *To:* Jose Alf. [email protected] *Cc:* "[email protected]" < [email protected]>; "[email protected]" < [email protected]> *Sent:* Tuesday, July 31, 2012 2:39 AM *Subject:* Re: [stunnel-users] Build stunnel 4.53 binaries for windows error
Hey Jose,
Could you just share your build inctructions under windows? If it works, fine - I can use windows too :)
Thank you, Anton.
2012/7/24 Jose Alf. [email protected]
Anton,
I usually compile my stunnel under windows (mingw). I tested with Debian Squeeze installation and I found the same problem. In step 6, ./configure finish fine, but the Make step does not work.
I checked and I found the included directories are not th right ones. I will take a look later this week.
Mich,
Any suggestions? Regards Jose *From:* Anton Tkachev [email protected] *To:* [email protected] *Cc:* [email protected]; [email protected] *Sent:* Monday, July 23, 2012 7:11 AM *Subject:* Re: [stunnel-users] Build stunnel 4.53 binaries for windows error
Does the ./configure script under stunnel-4.53 finish OK?
Yes. No errors at this step.
I also think that you should pass a parameter to force the cross
compilation of stunnel. It could be using the default system compiler. Maybe set CC, GCC environment vars to point to the cross compiler path before running ./configure: eg
export CC=/usr/pathtomingwgcc/bin/gcc
My mingw installation doesn't have any compiler.
I think the problem in openssl path, because error message is: # make stunnel.exe i586-mingw32msvc-gcc -c -I/usr/src/openssl-1.0.0f-i586/include -mthreads -fstack-protector -O2 -Wall -Wextra -Wno-long-long -pedantic -o str.obj str.c In file included from str.c:38: common.h:392:33: error: openssl/opensslconf.h: No such file or directory common.h:405:27: error: openssl/lhash.h: No such file or directory common.h:406:25: error: openssl/ssl.h: No such file or directory ...
These files exist in /usr/src/openssl-1.0.0f-i586/include/openssl directory, but building doesn't work anyway...
2012/7/20 [email protected]
** Anton,
Does the ./configure script under stunnel-4.53 finish OK? I also think that you should pass a parameter to force the cross compilation of stunnel. It could be using the default system compiler. Maybe set CC, GCC environment vars to point to the cross compiler path before running ./configure: eg
export CC=/usr/pathtomingwgcc/bin/gcc
Enjoy! *From: * Anton Tkachev [email protected] *Date: *Fri, 20 Jul 2012 21:44:09 +0700 *To: *[email protected] *Cc: *[email protected]; [email protected] *Subject: *Re: [stunnel-users] Build stunnel 4.53 binaries for windows error
Hey Jose, Thank you for your response!
You cross compiled your openssl 1.01c for mingw32, right?
Yes, I used ./Configure --cross-compile-prefix=i586-mingw32msvc- mingw shared zlib-dynamic command.
Try passing the path of your mingw32 openssl includes and libs to
stunnel configure:
--with-openssl*=
Do configure --help to see the exact syntax.
Do you mean ./configure --with-ssl=/usr/src/openssl-1.0.1c-i586 --includedir=/usr/i586-mingw32msvc/include --libdir=/usr/i586-mingw32msvc/lib ? Unfortunately 'make stunnel.exe' returns the same error in this case.
2012/7/20 [email protected]
Anton,
Ahh... The joys of cross compiling!
You cross compiled your openssl 1.01c for mingw32, right? Or you installed the mingw32 version. Try passing the path of your mingw32 openssl includes and libs to stunnel configure:
--with-openssl*=
Do configure --help to see the exact syntax.
Let us know how it goes. -----Original Message----- From: Anton Tkachev [email protected] Sender: [email protected] Date: Fri, 20 Jul 2012 16:28:57 To: [email protected] Subject: [stunnel-users] Build stunnel 4.53 binaries for windows error
stunnel-users mailing list [email protected] http://stunnel.mirt.net/mailman/listinfo/stunnel-users
Anton,
Do not run configure stunnel. Not required. After your openssl is compiled, Just edit mingw.mak. You also need to set the SSLDIR (I guess you did ;) ... And just comment the line that includes applink.c in stunnel.c
Regards,
Jose -----Original Message----- From: Anton Tkachev [email protected] Date: Wed, 1 Aug 2012 15:54:45 To: Jose Alf.[email protected] Cc: [email protected][email protected]; [email protected][email protected] Subject: Re: [stunnel-users] Build stunnel 4.53 binaries for windows error
I used the same openssl version: 1.0.0h I had to change also CFLAGS in mingw.mak from CFLAGS=-g -O2 -Wall $(DEFINES) -I$(SSLDIR)/inc32 to CFLAGS=-g -O2 -Wall $(DEFINES) -I$(SSLDIR)/include because folder inc32 doesn't exist.
Now when I run make -f mingw.mak I get the following error: # make -f mingw.mak host machine is a linux machine make: [makedirs] Error 1 (ignored) make: [makedirs] Error 1 (ignored) make: [makedirs] Error 1 (ignored) make: [makedirs] Error 1 (ignored) /usr/bin/i586-mingw32msvc-gcc -g -O2 -Wall -D_WIN32_WINNT=0x0501 -I/usr/src/openssl-1.0.0h/include -o../obj/MGW32/stunnel.o -c ../src/stunnel.c ../src/stunnel.c:44: warning: expected [error|warning|ignored] after ‘#pragma GCC diagnostic’ *../src/stunnel.c:47:29: error: openssl/applink.c: No such file or directory * ../src/stunnel.c:49: warning: expected [error|warning|ignored] after ‘#pragma GCC diagnostic’ make: *** [../obj/MGW32/stunnel.o] Error 1
How do you configure openssl and stunnel? ./Configure --cross-compile-prefix=i586-mingw32msvc- mingw shared zlib-dynamic and ./configure --with-ssl=/usr/src/openssl-1.0.0h ?
2012/8/1 Jose Alf. [email protected]
Anton,
Actually, I managed to compile it under Debian. We were doing it wrong. We must use the same method I use under Windows :)
- Go to the src directory and edit the file mingw.mak. Set variables CC,
RC, RCP as needed. I attach mine for you. 2. From src, execute make -f mingw.mak 3. If everything's fine, you'll find stunnel.exe in bin/MGW32
Time ti update the docs? regards Jose
*From:* Anton Tkachev [email protected] *To:* Jose Alf. [email protected] *Cc:* "[email protected]" < [email protected]>; "[email protected]" < [email protected]> *Sent:* Tuesday, July 31, 2012 2:39 AM *Subject:* Re: [stunnel-users] Build stunnel 4.53 binaries for windows error
Hey Jose,
Could you just share your build inctructions under windows? If it works, fine - I can use windows too :)
Thank you, Anton.
2012/7/24 Jose Alf. [email protected]
Anton,
I usually compile my stunnel under windows (mingw). I tested with Debian Squeeze installation and I found the same problem. In step 6, ./configure finish fine, but the Make step does not work.
I checked and I found the included directories are not th right ones. I will take a look later this week.
Mich,
Any suggestions? Regards Jose *From:* Anton Tkachev [email protected] *To:* [email protected] *Cc:* [email protected]; [email protected] *Sent:* Monday, July 23, 2012 7:11 AM *Subject:* Re: [stunnel-users] Build stunnel 4.53 binaries for windows error
Does the ./configure script under stunnel-4.53 finish OK?
Yes. No errors at this step.
I also think that you should pass a parameter to force the cross
compilation of stunnel. It could be using the default system compiler. Maybe set CC, GCC environment vars to point to the cross compiler path before running ./configure: eg
export CC=/usr/pathtomingwgcc/bin/gcc
My mingw installation doesn't have any compiler.
I think the problem in openssl path, because error message is: # make stunnel.exe i586-mingw32msvc-gcc -c -I/usr/src/openssl-1.0.0f-i586/include -mthreads -fstack-protector -O2 -Wall -Wextra -Wno-long-long -pedantic -o str.obj str.c In file included from str.c:38: common.h:392:33: error: openssl/opensslconf.h: No such file or directory common.h:405:27: error: openssl/lhash.h: No such file or directory common.h:406:25: error: openssl/ssl.h: No such file or directory ...
These files exist in /usr/src/openssl-1.0.0f-i586/include/openssl directory, but building doesn't work anyway...
2012/7/20 [email protected]
** Anton,
Does the ./configure script under stunnel-4.53 finish OK? I also think that you should pass a parameter to force the cross compilation of stunnel. It could be using the default system compiler. Maybe set CC, GCC environment vars to point to the cross compiler path before running ./configure: eg
export CC=/usr/pathtomingwgcc/bin/gcc
Enjoy! *From: * Anton Tkachev [email protected] *Date: *Fri, 20 Jul 2012 21:44:09 +0700 *To: *[email protected] *Cc: *[email protected]; [email protected] *Subject: *Re: [stunnel-users] Build stunnel 4.53 binaries for windows error
Hey Jose, Thank you for your response!
You cross compiled your openssl 1.01c for mingw32, right?
Yes, I used ./Configure --cross-compile-prefix=i586-mingw32msvc- mingw shared zlib-dynamic command.
Try passing the path of your mingw32 openssl includes and libs to
stunnel configure:
--with-openssl*=
Do configure --help to see the exact syntax.
Do you mean ./configure --with-ssl=/usr/src/openssl-1.0.1c-i586 --includedir=/usr/i586-mingw32msvc/include --libdir=/usr/i586-mingw32msvc/lib ? Unfortunately 'make stunnel.exe' returns the same error in this case.
2012/7/20 [email protected]
Anton,
Ahh... The joys of cross compiling!
You cross compiled your openssl 1.01c for mingw32, right? Or you installed the mingw32 version. Try passing the path of your mingw32 openssl includes and libs to stunnel configure:
--with-openssl*=
Do configure --help to see the exact syntax.
Let us know how it goes. -----Original Message----- From: Anton Tkachev [email protected] Sender: [email protected] Date: Fri, 20 Jul 2012 16:28:57 To: [email protected] Subject: [stunnel-users] Build stunnel 4.53 binaries for windows error
stunnel-users mailing list [email protected] http://stunnel.mirt.net/mailman/listinfo/stunnel-users
And just comment the line that includes applink.c in stunnel.c
That was not obvious :)
Thank you Jose, it finally works!!!
2012/8/1 [email protected]
** Anton,
Do not run configure stunnel. Not required. After your openssl is compiled, Just edit mingw.mak. You also need to set the SSLDIR (I guess you did ;) ... And just comment the line that includes applink.c in stunnel.c
Regards,
Jose
*From: * Anton Tkachev [email protected] *Date: *Wed, 1 Aug 2012 15:54:45 +0700 *To: *Jose Alf.[email protected] *Cc: *[email protected][email protected]; [email protected][email protected] *Subject: *Re: [stunnel-users] Build stunnel 4.53 binaries for windows error
I used the same openssl version: 1.0.0h I had to change also CFLAGS in mingw.mak from CFLAGS=-g -O2 -Wall $(DEFINES) -I$(SSLDIR)/inc32 to CFLAGS=-g -O2 -Wall $(DEFINES) -I$(SSLDIR)/include because folder inc32 doesn't exist.
Now when I run make -f mingw.mak I get the following error: # make -f mingw.mak host machine is a linux machine make: [makedirs] Error 1 (ignored) make: [makedirs] Error 1 (ignored) make: [makedirs] Error 1 (ignored) make: [makedirs] Error 1 (ignored) /usr/bin/i586-mingw32msvc-gcc -g -O2 -Wall -D_WIN32_WINNT=0x0501 -I/usr/src/openssl-1.0.0h/include -o../obj/MGW32/stunnel.o -c ../src/stunnel.c ../src/stunnel.c:44: warning: expected [error|warning|ignored] after ‘#pragma GCC diagnostic’ *../src/stunnel.c:47:29: error: openssl/applink.c: No such file or directory* ../src/stunnel.c:49: warning: expected [error|warning|ignored] after ‘#pragma GCC diagnostic’ make: *** [../obj/MGW32/stunnel.o] Error 1
How do you configure openssl and stunnel? ./Configure --cross-compile-prefix=i586-mingw32msvc- mingw shared zlib-dynamic and ./configure --with-ssl=/usr/src/openssl-1.0.0h ?
2012/8/1 Jose Alf. [email protected]
Anton,
Actually, I managed to compile it under Debian. We were doing it wrong. We must use the same method I use under Windows :)
- Go to the src directory and edit the file mingw.mak. Set variables CC,
RC, RCP as needed. I attach mine for you. 2. From src, execute make -f mingw.mak 3. If everything's fine, you'll find stunnel.exe in bin/MGW32
Time ti update the docs? regards Jose
*From:* Anton Tkachev [email protected] *To:* Jose Alf. [email protected] *Cc:* "[email protected]" < [email protected]>; "[email protected]" < [email protected]> *Sent:* Tuesday, July 31, 2012 2:39 AM *Subject:* Re: [stunnel-users] Build stunnel 4.53 binaries for windows error
Hey Jose,
Could you just share your build inctructions under windows? If it works, fine - I can use windows too :)
Thank you, Anton.
2012/7/24 Jose Alf. [email protected]
Anton,
I usually compile my stunnel under windows (mingw). I tested with Debian Squeeze installation and I found the same problem. In step 6, ./configure finish fine, but the Make step does not work.
I checked and I found the included directories are not th right ones. I will take a look later this week.
Mich,
Any suggestions? Regards Jose *From:* Anton Tkachev [email protected] *To:* [email protected] *Cc:* [email protected]; [email protected] *Sent:* Monday, July 23, 2012 7:11 AM *Subject:* Re: [stunnel-users] Build stunnel 4.53 binaries for windows error
Does the ./configure script under stunnel-4.53 finish OK?
Yes. No errors at this step.
I also think that you should pass a parameter to force the cross
compilation of stunnel. It could be using the default system compiler. Maybe set CC, GCC environment vars to point to the cross compiler path before running ./configure: eg
export CC=/usr/pathtomingwgcc/bin/gcc
My mingw installation doesn't have any compiler.
I think the problem in openssl path, because error message is: # make stunnel.exe i586-mingw32msvc-gcc -c -I/usr/src/openssl-1.0.0f-i586/include -mthreads -fstack-protector -O2 -Wall -Wextra -Wno-long-long -pedantic -o str.obj str.c In file included from str.c:38: common.h:392:33: error: openssl/opensslconf.h: No such file or directory common.h:405:27: error: openssl/lhash.h: No such file or directory common.h:406:25: error: openssl/ssl.h: No such file or directory ...
These files exist in /usr/src/openssl-1.0.0f-i586/include/openssl directory, but building doesn't work anyway...
2012/7/20 [email protected]
** Anton,
Does the ./configure script under stunnel-4.53 finish OK? I also think that you should pass a parameter to force the cross compilation of stunnel. It could be using the default system compiler. Maybe set CC, GCC environment vars to point to the cross compiler path before running ./configure: eg
export CC=/usr/pathtomingwgcc/bin/gcc
Enjoy! *From: * Anton Tkachev [email protected] *Date: *Fri, 20 Jul 2012 21:44:09 +0700 *To: *[email protected] *Cc: *[email protected]; [email protected] *Subject: *Re: [stunnel-users] Build stunnel 4.53 binaries for windows error
Hey Jose, Thank you for your response!
You cross compiled your openssl 1.01c for mingw32, right?
Yes, I used ./Configure --cross-compile-prefix=i586-mingw32msvc- mingw shared zlib-dynamic command.
Try passing the path of your mingw32 openssl includes and libs to
stunnel configure:
--with-openssl*=
Do configure --help to see the exact syntax.
Do you mean ./configure --with-ssl=/usr/src/openssl-1.0.1c-i586 --includedir=/usr/i586-mingw32msvc/include --libdir=/usr/i586-mingw32msvc/lib ? Unfortunately 'make stunnel.exe' returns the same error in this case.
2012/7/20 [email protected]
Anton,
Ahh... The joys of cross compiling!
You cross compiled your openssl 1.01c for mingw32, right? Or you installed the mingw32 version. Try passing the path of your mingw32 openssl includes and libs to stunnel configure:
--with-openssl*=
Do configure --help to see the exact syntax.
Let us know how it goes. -----Original Message----- From: Anton Tkachev [email protected] Sender: [email protected] Date: Fri, 20 Jul 2012 16:28:57 To: [email protected] Subject: [stunnel-users] Build stunnel 4.53 binaries for windows error
stunnel-users mailing list [email protected] http://stunnel.mirt.net/mailman/listinfo/stunnel-users
Anton,
I'm glad. I guess the binary works too ;)
-----Original Message----- From: Anton Tkachev [email protected] Date: Wed, 1 Aug 2012 18:08:25 To: [email protected] Cc: [email protected][email protected]; [email protected][email protected] Subject: Re: [stunnel-users] Build stunnel 4.53 binaries for windows error
And just comment the line that includes applink.c in stunnel.c
That was not obvious :)
Thank you Jose, it finally works!!!
2012/8/1 [email protected]
** Anton,
Do not run configure stunnel. Not required. After your openssl is compiled, Just edit mingw.mak. You also need to set the SSLDIR (I guess you did ;) ... And just comment the line that includes applink.c in stunnel.c
Regards,
Jose
*From: * Anton Tkachev [email protected] *Date: *Wed, 1 Aug 2012 15:54:45 +0700 *To: *Jose Alf.[email protected] *Cc: *[email protected][email protected]; [email protected][email protected] *Subject: *Re: [stunnel-users] Build stunnel 4.53 binaries for windows error
I used the same openssl version: 1.0.0h I had to change also CFLAGS in mingw.mak from CFLAGS=-g -O2 -Wall $(DEFINES) -I$(SSLDIR)/inc32 to CFLAGS=-g -O2 -Wall $(DEFINES) -I$(SSLDIR)/include because folder inc32 doesn't exist.
Now when I run make -f mingw.mak I get the following error: # make -f mingw.mak host machine is a linux machine make: [makedirs] Error 1 (ignored) make: [makedirs] Error 1 (ignored) make: [makedirs] Error 1 (ignored) make: [makedirs] Error 1 (ignored) /usr/bin/i586-mingw32msvc-gcc -g -O2 -Wall -D_WIN32_WINNT=0x0501 -I/usr/src/openssl-1.0.0h/include -o../obj/MGW32/stunnel.o -c ../src/stunnel.c ../src/stunnel.c:44: warning: expected [error|warning|ignored] after ‘#pragma GCC diagnostic’ *../src/stunnel.c:47:29: error: openssl/applink.c: No such file or directory* ../src/stunnel.c:49: warning: expected [error|warning|ignored] after ‘#pragma GCC diagnostic’ make: *** [../obj/MGW32/stunnel.o] Error 1
How do you configure openssl and stunnel? ./Configure --cross-compile-prefix=i586-mingw32msvc- mingw shared zlib-dynamic and ./configure --with-ssl=/usr/src/openssl-1.0.0h ?
2012/8/1 Jose Alf. [email protected]
Anton,
Actually, I managed to compile it under Debian. We were doing it wrong. We must use the same method I use under Windows :)
- Go to the src directory and edit the file mingw.mak. Set variables CC,
RC, RCP as needed. I attach mine for you. 2. From src, execute make -f mingw.mak 3. If everything's fine, you'll find stunnel.exe in bin/MGW32
Time ti update the docs? regards Jose
*From:* Anton Tkachev [email protected] *To:* Jose Alf. [email protected] *Cc:* "[email protected]" < [email protected]>; "[email protected]" < [email protected]> *Sent:* Tuesday, July 31, 2012 2:39 AM *Subject:* Re: [stunnel-users] Build stunnel 4.53 binaries for windows error
Hey Jose,
Could you just share your build inctructions under windows? If it works, fine - I can use windows too :)
Thank you, Anton.
2012/7/24 Jose Alf. [email protected]
Anton,
I usually compile my stunnel under windows (mingw). I tested with Debian Squeeze installation and I found the same problem. In step 6, ./configure finish fine, but the Make step does not work.
I checked and I found the included directories are not th right ones. I will take a look later this week.
Mich,
Any suggestions? Regards Jose *From:* Anton Tkachev [email protected] *To:* [email protected] *Cc:* [email protected]; [email protected] *Sent:* Monday, July 23, 2012 7:11 AM *Subject:* Re: [stunnel-users] Build stunnel 4.53 binaries for windows error
Does the ./configure script under stunnel-4.53 finish OK?
Yes. No errors at this step.
I also think that you should pass a parameter to force the cross
compilation of stunnel. It could be using the default system compiler. Maybe set CC, GCC environment vars to point to the cross compiler path before running ./configure: eg
export CC=/usr/pathtomingwgcc/bin/gcc
My mingw installation doesn't have any compiler.
I think the problem in openssl path, because error message is: # make stunnel.exe i586-mingw32msvc-gcc -c -I/usr/src/openssl-1.0.0f-i586/include -mthreads -fstack-protector -O2 -Wall -Wextra -Wno-long-long -pedantic -o str.obj str.c In file included from str.c:38: common.h:392:33: error: openssl/opensslconf.h: No such file or directory common.h:405:27: error: openssl/lhash.h: No such file or directory common.h:406:25: error: openssl/ssl.h: No such file or directory ...
These files exist in /usr/src/openssl-1.0.0f-i586/include/openssl directory, but building doesn't work anyway...
2012/7/20 [email protected]
** Anton,
Does the ./configure script under stunnel-4.53 finish OK? I also think that you should pass a parameter to force the cross compilation of stunnel. It could be using the default system compiler. Maybe set CC, GCC environment vars to point to the cross compiler path before running ./configure: eg
export CC=/usr/pathtomingwgcc/bin/gcc
Enjoy! *From: * Anton Tkachev [email protected] *Date: *Fri, 20 Jul 2012 21:44:09 +0700 *To: *[email protected] *Cc: *[email protected]; [email protected] *Subject: *Re: [stunnel-users] Build stunnel 4.53 binaries for windows error
Hey Jose, Thank you for your response!
You cross compiled your openssl 1.01c for mingw32, right?
Yes, I used ./Configure --cross-compile-prefix=i586-mingw32msvc- mingw shared zlib-dynamic command.
Try passing the path of your mingw32 openssl includes and libs to
stunnel configure:
--with-openssl*=
Do configure --help to see the exact syntax.
Do you mean ./configure --with-ssl=/usr/src/openssl-1.0.1c-i586 --includedir=/usr/i586-mingw32msvc/include --libdir=/usr/i586-mingw32msvc/lib ? Unfortunately 'make stunnel.exe' returns the same error in this case.
2012/7/20 [email protected]
Anton,
Ahh... The joys of cross compiling!
You cross compiled your openssl 1.01c for mingw32, right? Or you installed the mingw32 version. Try passing the path of your mingw32 openssl includes and libs to stunnel configure:
--with-openssl*=
Do configure --help to see the exact syntax.
Let us know how it goes. -----Original Message----- From: Anton Tkachev [email protected] Sender: [email protected] Date: Fri, 20 Jul 2012 16:28:57 To: [email protected] Subject: [stunnel-users] Build stunnel 4.53 binaries for windows error
stunnel-users mailing list [email protected] http://stunnel.mirt.net/mailman/listinfo/stunnel-users
-
Anton Tkachev -
Jose Alf. -
josealf＠rocketmail.com