New C2220: warning treated as error (MSVC 2015 build failure)

Luke Benes <lukebenes -AT- hotmail.com>
Thu, 30 Jun 2016 10:46:54 -0700

Ever since 
https://cgit.freedesktop.org/libreoffice/core/commit/?id=62c047ffb397802c09df9070492e70725928cadf
Author: Markus Mohrhard <markus.mohrhard@googlemail.com>Date:   Mon Jun 20 09:02:47 2016 +0200
    switch to EHs on windows
I'm getting the following build error with MSVC 2015 (32-bit MSVC 2013 still works). 
[build CXX] svl/source/undo/undo.cxxc:\lode\dev\core\svl\source\undo\undo.cxx(390) : error C2220: 
warning treated as error - no 'object' file generatedc:\lode\dev\core\svl\source\undo\undo.cxx(390) 
: warning C4702: unreachable codeC:/lode/dev/core/solenv/gbuild/LinkTarget.mk:189: recipe for 
target 'C:/lode/dev/core/workdir/CxxObject/svl/source/undo/undo.o' failedmake[1]: *** 
[C:/lode/dev/core/workdir/CxxObject/svl/source/undo/undo.o] Error 2make[1]: *** Waiting for 
unfinished jobs....Makefile:258: recipe for target 'build' failedmake: *** [build] Error 2

Context

New C2220: warning treated as error (MSVC 2015 build failure) · Luke Benes
- Re: New C2220: warning treated as error (MSVC 2015 build failure) · Markus Mohrhard
  - Re: New C2220: warning treated as error (MSVC 2015 build failure) · Stephan Bergmann
    - Re: New C2220: warning treated as error (MSVC 2015 build failure) · slacka
- Re: New MSVC 2015 build failure · Luke Benes
  - Re: New MSVC 2015 build failure · Michael Stahl
    - Re: New MSVC 2015 build failure · slacka

Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.