[SERVER-41570] Xcode 11 generates new warnings Created: 06/Jun/19 Updated: 29/Oct/23 Resolved: 11/Jul/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | None |
| Fix Version/s: | 4.2.1, 4.3.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Alya Berciu | Assignee: | Alya Berciu |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Backport Requested: |
v4.2
|
||||
| Sprint: | Dev Tools 2019-07-01, Dev Tools 2019-07-15 | ||||
| Participants: | |||||
| Description |
|
Xcode 11 Clang generates the following warnings, which prevent compilation on macOS: - warning: explicitly defaulted move constructor is implicitly deleted [-Wdefaulted-function-deleted] - warning: explicitly defaulted move assignment operator is implicitly deleted [-Wdefaulted-function-deleted] The locations in code that generate these warnings are:
|
| Comments |
| Comment by Githook User [ 24/Sep/19 ] |
|
Author: {'email': 'andrew.morrow@10gen.com', 'name': 'Andrew Morrow'}Message: (cherry picked from commit d7d9b79ae30cd3a7e35beaae7ce9fdc016e4bd17) |
| Comment by Githook User [ 11/Jul/19 ] |
|
Author: {'name': 'Alya Berciu', 'email': 'alya.berciu@mongodb.com', 'username': 'alyacb'}Message: |
| Comment by Andrew Morrow (Inactive) [ 22/Jun/19 ] |
|
alya.berciu - I'm going to assign this one to you. It should be pretty easy to find where we suppress warnings flags we don't like in the top level SConstruct, and I'm fairly sure that billy.donahue and I agree that this warning is just silly. If we suppress it on master, we should think about backporting to 4.2 as well so that XCode 11 works there when it starts to diffuse out to developer macs. |