Hello everyone,

> Am 13.06.2016 um 20:22 schrieb Cody Pritchard (cpritchard) <cpritchard_at_micron.com>:
>
> But, towards the end it lists a bunch of warnings about linking errors to the NSS libraries stating:
> Warning: linker path does not have real file for library -lssl3.
> I have the capability to make that library automatically link in when you link this library. But I can only do this If you have a
> Shared version of the library, which you do not appear to have because I did check the linker path looking for a file starting
> With libssl3 but no candidates were found. (...for file magic test)
>
> It gives this warning for the libraries:
> -lssl3, -lsmime3, -lnss3, -lplds4, -lplc4, -lnspr4
>
> But I have these libraries in / dist/WIN954.0_DBG.OBJ/lib as:
> ssl3.dll, smime3.dll, nss3.dll, plc4.dll, nspr4.dll
>
> So does it need these to all be libssl3.dll, etc? And if so, how do I make that happen?
>
> Then gives the notice:
> Since this library must not contain undefined symbols, because either the platform does not support them
> Or it was explicitely requested with -no-undefined, libtool will only create a static version of it.
>
> After this it continues compiling and goes to build all in c:/BUILD/curl-7.49.0/src and hits an error and fails.

this might be related to the following issue:
http://ricardo.ecn.wfu.edu/~cottrell/cross-gtk/libtool.html <http://ricardo.ecn.wfu.edu/~cottrell/cross-gtk/libtool.html>

I am currently running into similar issues, please check if the described libtool hack helps and report back.

Best regards,
Marc

-------------------------------------------------------------------
List admin: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2016-06-13