On Mon, Jun 13, 2016 at 6:32 PM, Dan S wrote:
> So I had a suggestion to verify the correct linking by renaming the libssl
> and libcrypto built locally to something else, and linking to them- turns
> out that was the problem, apparently adding the search path in xcode does
So I had a suggestion to verify the correct linking by renaming the libssl
and libcrypto built locally to something else, and linking to them- turns
out that was the problem, apparently adding the search path in xcode does
not take priority :( and it was still linking with the distributed old open
sorry forgot to mantion that after linking with all the paths set it
produces the single error (one from before: Symbol(s) not found
_TLS1_2_method referenced from _main in main.o
On Mon, Jun 13, 2016 at 1:14 PM, Dan S wrote:
> I did this step at a time to see what
I did this step at a time to see what happens and here are the results:
With no paths modified, just bare code produces compile error
('TLSv1_2_method' was not declared at this scope) as expected because
openssl that comes osx 10.6 is older without such method - ok so far
Adding header paths to
> Le 9 juin 2016 à 02:29, Dan S a écrit :
>
> Hello, I've compiled openssl.1.0.2h on osx (32bit) and linked staticly my
> project with libcrypto.a and libssl/a, but I get 2 linking errors with
> "Symbol(s) not found":
>
> _TLSv1_2_method, referenced from ...
> and
> _BIO_test_flags, referenced
I've also tried 1.0.2g and same problem on osx. Little more details: on pc
the expected symbol (_TLSv1_2_method) is in the ssleay32.lib as expected
on mac (and this is specifically on 10.5 and 10.6 Darwin i386) it builds
two libs:
libcrypto.a and libssl.a (the undefined symbol is showing up in
Hello, I've compiled openssl.1.0.2h on osx (32bit) and linked staticly my
project with libcrypto.a and libssl/a, but I get 2 linking errors with
"Symbol(s) not found":
_TLSv1_2_method, referenced from ...
and
_BIO_test_flags, referenced from ...
Why would this be happening?
ps: (same code