|
From: | Paul Eggert |
Subject: | Re: Error compiling bison 3.4.2 on Solaris |
Date: | Fri, 18 Oct 2019 11:51:50 -0700 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.1.1 |
On 10/17/19 11:34 PM, Akim Demaille wrote:
Bison no longer compiles cleanly (i.e., many warnings) on macOS with GCC 7, 8, 9. Clang is ok though. And there are similar failures on the CI with older versions of GCC. https://travis-ci.org/akimd/bison/builds/599470491
First, I suggest telling Travis not to use --enable-gcc-warnings. That option is intended mainly for developers, and it's not suitable for simply building and testing Bison because it generates too many false alarms (as is the case here).
Second, the diagnostics in the above URL are all false alarms. If they are affecting you, does the attached patch silence them? This patch is the sort of thing we do for other GNU projects (e.g., coreutils, Emacs), because back when we were configuring these warning options the latest GCC (the one used by developers) generated too many false alarms. -Wno-type-limits doesn't seem to be needed with recent GCC so I suppose they fixed some GCC bugs in this area.
0001-port-to-picky-older-GCC.patch
Description: Text Data
[Prev in Thread] | Current Thread | [Next in Thread] |