[SERVER-22042] If ssl libraries not present, configure fails with a misleading error about boost Created: 20/Dec/15 Updated: 22/Nov/16 Resolved: 05/Jan/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | None |
| Fix Version/s: | 3.0.10, 3.2.3, 3.3.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Andrew Morrow (Inactive) | Assignee: | Jonathan Reams |
| Resolution: | Done | Votes: | 0 |
| Labels: | code-only | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Backport Completed: | |||||
| Sprint: | Platforms E (01/08/16) | ||||
| Participants: | |||||
| Description |
|
We don't do a CheckLib for SSL. We just add ssl and crypto to LIBS. The result is that if the libssl and libcrypto libraries are not present, later TryLink or CheckLib calls fail. This can lead to confusing error messages complaining that, for instance, boost cannot be found, even though the real problem is that the SSL libraries are not available. See https://groups.google.com/forum/#!topic/mongodb-user/qZhskcDOeKY The fix is to add a proper CheckLib for the SSL libraries and error out if they are not found but the user requested SSL support with --ssl. |
| Comments |
| Comment by Githook User [ 22/Feb/16 ] |
|
Author: {u'username': u'acmorrow', u'name': u'Andrew Morrow', u'email': u'acm@mongodb.com'}Message: |
| Comment by Githook User [ 21/Feb/16 ] |
|
Author: {u'name': u'Ramon Fernandez', u'email': u'ramon@mongodb.com'}Message: Revert " This reverts commit 3a5a890e1e1832ea8a45607d01ddef36ac3d76fa, since it's |
| Comment by Githook User [ 20/Feb/16 ] |
|
Author: {u'username': u'acmorrow', u'name': u'Andrew Morrow', u'email': u'acm@mongodb.com'}Message: |
| Comment by Githook User [ 27/Jan/16 ] |
|
Author: {u'username': u'acmorrow', u'name': u'Andrew Morrow', u'email': u'acm@mongodb.com'}Message: (cherry picked from commit 719ac08161e6cff62f518e6f349a634ebcbc3234) |
| Comment by Githook User [ 05/Jan/16 ] |
|
Author: {u'username': u'acmorrow', u'name': u'Andrew Morrow', u'email': u'acm@mongodb.com'}Message: |
| Comment by Andrew Morrow (Inactive) [ 03/Jan/16 ] |
|
ngj783 - You can leave it open for now, and I can close it once the relevant backports are completed with a link to the commit that fixes it - keeps the history more intelligible. |
| Comment by Ivan Mironov [ 03/Jan/16 ] |
|
acm, ok, no problem. Should I close PR? |
| Comment by Andrew Morrow (Inactive) [ 02/Jan/16 ] |
|
ngj783 - I've moved this ticket to the SERVER project. We will fix the issue there as it also affects the main server build, and then backport the approved fix to the legacy C++ driver. |
| Comment by Andrew Morrow (Inactive) [ 02/Jan/16 ] |
|
Requesting backport to 3.0 as well so this can eventually be picked up by the legacy C++ driver. |
| Comment by Ivan Mironov [ 30/Dec/15 ] |