Hi - @R_K -
I’m able to reproduce this when using SCons 4.2.0, but not when using the vendored SCons that comes with the MongoDB sources (currently 3.1.2 + mongodb patches). Would you please file an issue in the SERVER project of the MongoDB JIRA referring back to this discussion?
Meanwhile, as a workaround, you can use the built-in SCons by invoking buildscripts/scons.py and you should no longer experience this issue.
We plan to upgrade to SCons 4.2 sometime in the near future, per SERVER-49324, so fixing this will be a prerequisite. Thanks for letting us know about the issue.
Thanks,
Andrew