Re: BUG #16336: Undefined symbols since upgrade of VS to 2019.5.2, and other issues

On 02.04.20 11:58, PG Bug reporting form wrote:
> The following bug has been logged on the website:
> I've recently upgraded Visual Studio from 2019.3 to 2019.5.2. This broke
> my
> build of PostgreSQL. First I tried 11.5 which fails with the same errors,

Sorry for this, but it seems that PostgreSQL is not (directly) at fault for
this problem. I can now isolate that within some of the Perl methods of the
build, the PATH gets reset to the default Windows PATH. This seems to be
related to the recent update of Visual Studio.

Now this in turn triggers some unfortunate events:
- I ensure that a native Perl is in PATH before any other Perl
- I furthermore set the native Perl path in buildenv.pl
- I start the build from the native Perl
- But this PATH is reset to the default system PATH somewhere in the build
- In the default system PATH, there is Cygwin Perl, which I require for
building a few other packages

Any help would be appreciated. Does someone know where/how the PATH may be
reset in the build? Or are there any efforts to support Cygwin Perl for the
build? I'm under the impression that most native tools support forward
slashes as well as backward slashes. So maybe it would be possible to have
support for Cygwin Perl *and* native Perl?

But I may be misguided here, any help or feedback is appreciated!

All the best,

Mario Emmenlauer