Re: MSVC 2015's broken static initializer_list causing build failure

slacka <lukebenes -AT- hotmail.com>
Sat, 17 Dec 2016 20:03:59 -0700 (MST)

Per your recommendation, I upgrade to 
Microsoft Visual Studio Community 2015
Version 14.0.25431.01 Update 3

After the update, I'm still seeing the same error.

configure: error: working support for static initializer_list needed

-Luke




--
View this message in context: 
http://nabble.documentfoundation.org/MSVC-2015-s-broken-static-initializer-list-causing-build-failure-tp4202928p4203000.html
Sent from the Dev mailing list archive at Nabble.com.

Context

MSVC 2015's broken static initializer_list causing build failure · Luke Benes
- Re: MSVC 2015's broken static initializer_list causing build failure · Noel Grandin
  - Re: MSVC 2015's broken static initializer_list causing build failure · slacka
    - Re: MSVC 2015's broken static initializer_list causing build failure · Noel Grandin
      - Re: MSVC 2015's broken static initializer_list causing build failure · slacka
- Re: MSVC 2015's broken static initializer_list causing build failure · Stephan Bergmann
  - Re: MSVC 2015's broken static initializer_list causing build failure · Matúš Kukan
    - Re: MSVC 2015's broken static initializer_list causing build failure · Stephan Bergmann
      - Re: MSVC 2015's broken static initializer_list causing build failure · slacka
- MSVC 2015 32-bit builds Failing Now · Luke Benes
  - Re: MSVC 2015 32-bit builds Failing Now · Luke Benes

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.