Re: Support new and discontinue old compilers

2017-02-15 Thread David Ostrovsky
On Wed, 2017-02-15 at 15:39 +0200, marius adrian popa wrote: > I will check the issue with Firebird > > http://paste.openstack.org/show/594333/ > Not needed, the failure above was outdated, the recent firebird failure is: [1], which was trivial to fix: [2]. As a good open source citizen, I

Re: Support new and discontinue old compilers

2017-02-15 Thread Stephan Bergmann
On 02/15/2017 04:22 PM, Stephan Bergmann wrote: On 02/15/2017 02:39 PM, marius adrian popa wrote: I will check the issue with Firebird http://paste.openstack.org/show/594333/ I at least don't see that problem with a build of recent LO master against MSVC 2015. Building external/firebird

Re: Support new and discontinue old compilers

2017-02-15 Thread Stephan Bergmann
On 02/15/2017 02:39 PM, marius adrian popa wrote: I will check the issue with Firebird http://paste.openstack.org/show/594333/ I at least don't see that problem with a build of recent LO master against MSVC 2015. Building external/firebird works fine for me.

Re: Support new and discontinue old compilers

2017-02-15 Thread marius adrian popa
I will check the issue with Firebird http://paste.openstack.org/show/594333/ On Wed, Feb 15, 2017 at 10:26 AM, David Ostrovsky wrote: > > I'm pleased to share with you, that MSVC 15 (aka VS 2017) is up > and running on master: [1]. > > After fixing the VC++ runtime merge

Support new and discontinue old compilers

2017-02-15 Thread David Ostrovsky
I'm pleased to share with you, that MSVC 15 (aka VS 2017) is up and running on master: [1]. After fixing the VC++ runtime merge module merging problem in resulted MSI in MSVC 14.0 and MSVC 15.0, the produced MSI can not only be installed, but the LO can actually run after the installation. The