The whole 32 bit vs 64 bit thing is a pain. On Windows and Linux you have to load all kinds of unobvious things. On AIX it just works. Code from 1988 (when I lost source code for half a dozen programs) still works on current machines. Why the others make it SO HARD is beyond me. In AIX old code works. One flag – saying you want 64 bit – is all you need to add to the Makefile. Otherwise is just works as always. It took me MONTHS to figure out how to make Linuc work – had to yum 32 bit, 64 bit, a compat set, etc. Nightmare.
Wish people would consider keeping things compatible like IBM does. Ditto on new features. Any new feature you merely need to add a flag, and all is good. Otherwise the old ones keep working. An example is POSIX. With IBM/AIX you could do things the old way, or set a flag for POSIX.
Yes, we have had the same source (with updates, I did do the POSIX updates) since 1988. Never a problem. Partly, I think, because they don’t deprecate ANYTHING. Use the old routines if you like. Or not if you chose.
Your problem is not having ALL of the required libraries! That is it. Finding what you need is the challenge.
Eric
From: stunnel-users [mailto:stunnel-users-bounces@stunnel.org] On Behalf Of Heinsbroek, Peter
Sent: Tuesday, July 09, 2019 6:20 AM
To: stunnel-users@stunnel.org
Subject: [stunnel-users] Error during linking Stunnel 5.55
I tried to build stunnel from the sources.
The compiling goes well ,but the linking gives an error
When comping 32bit I get :
sthreads.obj : error LNK2019: unresolved external symbol _CRYPTO_set_id_callback referenced in function _sthreads_init
..\bin\win32\stunnel.exe : fatal error LNK1120: 1 unresolved externals
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.16.27023\bin\HostX86\x86\link.EXE"' : return code '0x460'
Stop.
Anyone knows how to solve.
Met vriendelijke groet,
| Peter Heinsbroek |
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, Atos’ liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. On all offers and agreements under which Atos Nederland B.V. supplies goods and/or services of whatever nature, the Terms of Delivery from Atos Nederland B.V. exclusively apply. The Terms of Delivery shall be promptly submitted to you on your request.