Re: Build errors in VS - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Build errors in VS
Date
Msg-id f4929cf2-2aac-8f66-1466-0560ace9cb25@2ndQuadrant.com
Whole thread Raw
In response to Re: Build errors in VS  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
List 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
notmatch 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




pgsql-hackers by date:

Previous
From: Juan José Santamaría Flecha
Date:
Subject: Re: PG compilation error with Visual Studio 2015/2017/2019
Next
From: Peter Geoghegan
Date:
Subject: Split interval (used by nbtree suffix truncation) and posting list tuples