Re: Build errors in VS

From: Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>
To: "Lin, Cuiping" <lincuiping(at)cn(dot)fujitsu(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Build errors in VS
Date: 2020-04-17 19:00:15
Message-ID: f4929cf2-2aac-8f66-1466-0560ace9cb25@2ndQuadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 4/17/20 9:56 AM, Andrew Dunstan wrote:
> On 4/17/20 5:18 AM, Lin, Cuiping wrote:
>> Hi all
>>
>> I build postgers with VS in windows, and the following message output
>>
>> “ Unable to determine Visual Studio version: The nmake version could not be determined.”
>>
>> I investigated the VSObjectFactory.pm, and found the match string “if ($output =~ /(\d+)\.(\d+)\.\d+(\.\d+)?$/m)”
>>
>> It works fine when no characters after version number, but if there are characters after the version number, it can not match the VS version.
>>
>> For example , VS in Chinese , nmake /? output “ 14.00.24210.0 版”
>
> Hmm, odd, but I guess we need to cater for it.
>
>
>>
>> May be we can remove the ‘$’ ($output =~ /(\d+)\.(\d+)\.\d+(\.\d+)?$/m)” => ($output =~ /(\d+)\.(\d+)\.\d+(\.\d+)?/m)”
>>
>>
> That will probably be ok. If we do that we should remove the 'm'
> qualifier on the regex too, it would serve no purpose any more.
>
>

Done

cheers

andrew

--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2020-04-17 19:11:52 Split interval (used by nbtree suffix truncation) and posting list tuples
Previous Message Juan José Santamaría Flecha 2020-04-17 18:43:35 Re: PG compilation error with Visual Studio 2015/2017/2019