Re: tinderboxes don't need to upgrade bison anymore

Stephan Bergmann <sbergman -AT- redhat.com>
Thu, 11 Jul 2013 08:48:24 +0200

On 07/10/2013 06:24 PM, Lionel Elie Mamane wrote:

As to the warnings like "defined, but not used", well warnings in
automatically generated code are not something we can/should tackle
"locally" / not worth forcing non-Apple provided bison on our MacOS X
build. I'd suggest forcing -Wno-error on this file; possibly
conditional on the known-problematic bison version(s).

Note that C/C++ files generated from flex/bison sources are alreadycompiled without -Werror, so it could only beconnectivity/source/parse/sqlnode.cxx including the generatedsqlbison.hxx that could cause problems wrt -Werror here.


Stephan

Context

tinderboxes please upgrade bison · Lionel Elie Mamane
- Re: tinderboxes please upgrade bison · Lubos Lunak
- Re: tinderboxes please upgrade bison · Norbert Thiebaud
  - Re: tinderboxes please upgrade bison · Lionel Elie Mamane
- Re: tinderboxes please upgrade bison · Tor Lillqvist
  - Re: tinderboxes please upgrade bison · Lionel Elie Mamane
    - tinderboxes don't need to upgrade bison anymore · Lionel Elie Mamane
      - Re: tinderboxes don't need to upgrade bison anymore · Norbert Thiebaud
        
        Re: tinderboxes don't need to upgrade bison anymore · Lubos Lunak
      - Re: tinderboxes don't need to upgrade bison anymore · Stephan Bergmann
    - Re: tinderboxes please upgrade bison · Norbert Thiebaud

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.