[SERVER-16957] Permit specification of boost library suffix search preference Created: 20/Jan/15  Updated: 23/Jan/15  Resolved: 21/Jan/15

Status: Closed
Project: Core Server
Component/s: Build
Affects Version/s: None
Fix Version/s: 3.0.0-rc6

Type: New Feature Priority: Major - P3
Reporter: Andrew Morrow (Inactive) Assignee: Andrew Morrow (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by CXX-284 Build fall back to environment boost ... Closed
Backwards Compatibility: Fully Compatible
Participants:

 Description   

We currently only search -mt and the empty string for boost suffixes when building with --use-system-boost.

This may not be sufficient on some systems where a user has boost installed to a non-system-searched path and has configured boost to not add the "-mt" adornment to the libraries, despite their having thread support.

When this setup is used, and we search for boost_system, for example, we will first look for boost_system-mt. The users search path (presumably configured with --extrapath or similar) will be examined for libboost_system-mt, which will not be found. We will then search the system boost installation, which does offer it. So we will choose the -mt adorned version of boost_system, and link against the library in the default search path, rather than in the users custom boost installation.

We should make it possible to specify the list of suffixes to search (including the empty suffix), as well as suppress all searches, which may be unnecessary on some platforms, like Windows, with autolib linking.



 Comments   
Comment by Githook User [ 21/Jan/15 ]

Author:

{u'username': u'acmorrow', u'name': u'Andrew Morrow', u'email': u'acm@mongodb.com'}

Message: SERVER-16957 Permit user specifiable list of boost search suffixes
Branch: master
https://github.com/mongodb/mongo/commit/91959b89ac64321955573c53298c566d4e69a3a1

Generated at Thu Feb 08 03:42:49 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.