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

Stephan Bergmann <sbergman -AT- redhat.com>
Mon, 19 Dec 2016 11:23:40 +0100

On 12/16/2016 10:53 PM, Luke Benes wrote:

When I try to build with MSVC 2015 I get the following error:
checking whether C:/PROGRA~2/MICROS~1.0/VC/bin/amd64/cl.exe has broken static initializer_list 
support... yes
configure: error: working support for static initializer_list needed
Error running configure at ./autogen.sh line 281.

<https://cgit.freedesktop.org/libreoffice/core/commit/?id=86e6d9b62f4d77a6949fdb98c570930a80f6917c>"Make check for broken static initialize_list work with MSVC 2015" fixesthat for me

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.