Joseph Brill

I ran in to the same problem and may have found a workaround. There is a gdb patch from October 2020 that appears to address this issue: > _gnulib: Ensure...

You're welcome. Until your response was posted, I didn't realize there was a spelling error for *dependencies* in the patch name and in the *gdb.sh* addition. The corrected patch filename...

Preparing it now. Will issue shortly...

@mwichmann When working on #4174, I ran into docbook issues that were related to a internal lxml global limit that resulted in docbook failures without particularly helpful messages. The root...

Just another note to ourselves. Informational only. This appears to be a known problem that falls through the cracks between the VC++ development team and vswhere. There was an issue...

FYI, the MSVS batch file code for processing the vcvars_ver argument is: ```bat @REM Support the VS 2015 Visual C++ Toolset if "%__VCVARS_VERSION%" == "14.0" ( goto :vcvars140_version ) @REM...

I have not had time to test the following yet. A quick-and-dirty hack would be to add an environment setting (e.g., "MSVC_VCVARS_VER") that will be passed to the vcvarsall batch...

Proof-of-concept code for supporting specific msvc toolset versions is shown below and attached. Testing has been limited. An environment variable "`MSVC_SPECIFIC_VERSION`" is used to choose a specific toolset for a...

Are there legacy issues with existing SConstruct/SConscript files if MSVS_VERSION is resurrected and the definition of MSVC_VERSION changes/expands?

A challenge with the current MSVC_VERSION definition is that "14.2", "14.1" and "14.1Exp" describe an msvs installation rather than an msvc toolset (14.16.27023) which can be present in all three....