[CDRIVER-2167] CMake Windows & OpenSSL 1.1.0 incorrect lib names Created: 17/May/17 Updated: 28/Oct/23 Resolved: 18/Jul/17 |
|
| Status: | Closed |
| Project: | C Driver |
| Component/s: | Build, libmongoc, tls |
| Affects Version/s: | None |
| Fix Version/s: | 1.8.0 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Hannes Magnusson | Assignee: | Hannes Magnusson |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Description |
|
See also https://github.com/h2o/h2o/pull/227 && https://mta.openssl.org/pipermail/openssl-dev/2016-August/008340.html OpenSSL renamed the library filenames on Windows in OpenSSL 1.1.0 (to libcrypto and libssl, rather then libeay32.lib & ssleay32.lib). The CMake FindOpenSSL does not seem to have been updated, so now the search passes, but linking fails, since we are attempting to link non-existing libs. |
| Comments |
| Comment by Githook User [ 26/Apr/18 ] |
|
Author: {'email': 'jesse@mongodb.com', 'username': 'ajdavis', 'name': 'A. Jesse Jiryu Davis'}Message: |
| Comment by Hannes Magnusson [ 18/Jul/17 ] |
|
There isn't much we can do other then erroring when we detect older cmake and newer openssl and ask the user to upgrade their cmake install – or configure using secure channel. |
| Comment by Githook User [ 18/Jul/17 ] |
|
Author: {u'username': u'bjori', u'name': u'Hannes Magnusson', u'email': u'bjori@php.net'}Message: |
| Comment by Githook User [ 18/Jul/17 ] |
|
Author: {u'username': u'bjori', u'name': u'Hannes Magnusson', u'email': u'bjori@php.net'}Message: |
| Comment by Hannes Magnusson [ 17/Jul/17 ] |
|
jesse What do you think we should do about this? |