[SERVER-42604] MongoDB third_party\boost failed due to "error C2039: 'value': is not a member of 'boost::proto'" under /permissive- + MSVC Created: 02/Aug/19 Updated: 14/Aug/19 Resolved: 14/Aug/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | QuellaZhang [X] | Assignee: | Andrew Morrow (Inactive) |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Sprint: | Dev Tools 2019-08-12, Dev Tools 2019-08-26 |
| Participants: |
| Description |
|
Hi All, MongoDB third_party\boost failed due to "error C2039: 'value': is not a member of 'boost::proto'" under /permissive- mode when built on MSVC. Could you please help take a look at this? Thanks in advance! Related to Boost/proto PR: https://github.com/boostorg/proto/pull/2. Verified if removed the Boost workaround for MSVC, MongoDB can build successfully too. You can repro this issue as the steps below: Error info:
|
| Comments |
| Comment by Andrew Morrow (Inactive) [ 14/Aug/19 ] |
|
QuellaZhang - I'm closing this issue, since I'm unable to reproduce this (our build uses permissive- and works), and haven't heard any additional details from you. Please feel free to follow up with additional information that will help us understand the issue if you would like us to take another look. |
| Comment by Andrew Morrow (Inactive) [ 12/Aug/19 ] |
|
QuellaZhang - Do you have any follow-up information per my prior comments? |
| Comment by Andrew Morrow (Inactive) [ 08/Aug/19 ] |
|
QuellaZhang - Thank you for the report. I'm a little puzzled by your repro instructions because a few things don't entirely fit together for me.
Of course, we are very interested in any situation where MongoDB does not correctly build with the Microsoft toolchain. If you could please provide additional context we are happy to help figure out what is causing this breakage and work to find a resolution. |
| Comment by Danny Hatcher (Inactive) [ 05/Aug/19 ] |
|
Thanks for reporting this issue. We'll look into it. |