Re: Windows build broken starting at da9b580d89903fee871cf54845ffa2b26bda2e11

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Mark Dilger <hornschnorter(at)gmail(dot)com>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Hao Lee <mixtrue(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Andrew Dunstan <andrew(at)dunslane(dot)net>
Subject: Re: Windows build broken starting at da9b580d89903fee871cf54845ffa2b26bda2e11
Date: 2018-05-15 17:29:24
Message-ID: 27616.1526405364@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Mark Dilger <hornschnorter(at)gmail(dot)com> writes:
>> On May 15, 2018, at 10:20 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Hm. I'm not sure what our nominal support range for Visual Studio is.
>> I see that mastodon (running VS2005) and currawong (running VS2008)
>> haven't reported on HEAD lately, and I think they may have been shut
>> down intentionally due to desupport? But if your build still works
>> then it seems like we could continue to support VS2008.

> I don't have a strong opinion on that. I could also look to upgrade
> to a newer version. Generally, I try to build using the oldest
> supported version rather than the newest. What is the next oldest
> working test machine you have?

thrips is described as running VS2010, though I'm not sure how to verify
that it's not been updated. The make log shows

c:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\AMD64\CL.exe

but is "10.0" the same thing as "2010"?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2018-05-15 17:44:58 Re: Make description of heap records more talkative for flags
Previous Message Mark Dilger 2018-05-15 17:22:11 Re: Windows build broken starting at da9b580d89903fee871cf54845ffa2b26bda2e11