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:20:05 |
Message-ID: | 27032.1526404805@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:
>>> If none of the animals
>>> are configured to detect this bug, perhaps the community needs another
>>> Windows animal configured along the lines of the build machine I am using?
>> +1. How do you have yours configured, anyway?
> I mostly develop on mac and linux and don't look at the windows system
> too much:
> Windows Server 2008 R2 Standard
> Service Pack 1
> Microsoft Visual Studio 2008 Beta2 x64 cross tools
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.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Dilger | 2018-05-15 17:22:11 | Re: Windows build broken starting at da9b580d89903fee871cf54845ffa2b26bda2e11 |
Previous Message | Mark Dilger | 2018-05-15 17:08:24 | Re: Windows build broken starting at da9b580d89903fee871cf54845ffa2b26bda2e11 |