GNU bug report logs - #51504
grep not building for me with gcc 11.2

Previous Next

Package: grep;

Reported by: Duncan Roe <duncan_roe <at> optusnet.com.au>

Date: Sat, 30 Oct 2021 10:17:03 UTC

Severity: normal

Done: Paul Eggert <eggert <at> cs.ucla.edu>

Bug is archived. No further changes may be made.

Full log


Message #10 received at 51504-done <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Duncan Roe <duncan_roe <at> optusnet.com.au>
Cc: duncan.roe2 <at> gmail.com, 51504-done <at> debbugs.gnu.org
Subject: Re: bug#51504: grep not building for me with gcc 11.2
Date: Sat, 30 Oct 2021 17:41:13 -0700
On 10/30/21 01:40, Duncan Roe wrote:
> To stop other folks running into this, configure.ac needs to be fixed to not
> --enable-gcc-warnings of its own accord.

configure.ac enables GCC warnings by default only you're building from a 
Git repository. If you had built from the latest grep release tarball 
you wouldn't have run into this problem.

This should be documented better in README-hacking. I installed a patch 
to GNU grep to try to do that. See:

https://git.savannah.gnu.org/cgit/grep.git/commit/?id=1ba972edec7867c1592083363dc9fadfebf77e2e


> Should I report these to the gcc team?

I wouldn't bother. The grep sources are tuned for --enable-gcc-warnings 
with -O2 and no other optimization-relevant options.




This bug report was last modified 3 years and 205 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.