Apologies if this is a known issue or expected behaviour. When I run configure with "--enable-gcc-warnings" and then do a make, I get the following compilation errors for search.c:
CC search.o cc1: warnings being treated as errors search.c: In function 'Pexecute': search.c:774: error: function might be possible candidate for attribute 'noreturn' [-Wmissing-noreturn] No problems with make or make check if I don't use --enable-gcc-warnings. Here is what I have for build tools: gcc 4.3.4 GNU Make 3.81 Thanks, Shiva On Thu, Mar 18, 2010 at 8:49 AM, Jim Meyering <[email protected]> wrote: > I would like to release grep-2.6 soon, so please try out this > snapshot and let us know if it passes the "make check" tests > on your favorite (or not so favorite) system. We appreciate > hearing about successful builds/tests as well as failing ones. > > This upcoming release fixes an unexpectedly large number of flaws, > from outright bugs (surprisingly many, considering this is "grep") > to some occasionally debilitating performance problems. > Special thanks to Paolo Bonzini for doing most of the heavy lifting. > > http://git.sv.gnu.org/gitweb/?p=grep.git > > We now have an autobuilder (thanks to Rob Vermeer), > http://hydra.nixos.org/jobset/gnu/grep-master > which shows there are a few test failures on Cygwin, > but that otherwise, all of its builds and tests succeed. > If someone can diagnose (or even fix!) those we'd appreciate it. > > ========================================================= > Here are the sources: > > grep snapshot: (.gz files are here, too) > http://meyering.net/grep-ss.tar.xz 792 KB > http://meyering.net/grep-ss.tar.xz.sig > http://meyering.net/grep-2.5.4.183-9159.tar.xz > > There are .gz and .sig files here, too: > http://people.redhat.com/meyering/grep-ss.tar.xz > http://people.redhat.com/meyering/grep-2.5.4.183-9159.tar.xz > > ========================================================= > Here are the additions to NEWS for the upcoming release: > > ** Speed improvements > > grep is much faster on multibyte character sets, especially (but not > limited to) UTF-8 character sets. The speed improvement is also very > pronounced with case-insensitive matches. > > ** Bug fixes > > Character classes would malfunction in multi-byte locales when using grep > -i. > Examples which would print nothing for LC_ALL=en_US.UTF-8 include: > - for ranges, echo Z | grep -i '[a-z]' > - for single characters, echo Y | grep -i '[y]' > - for character types, echo Y | grep -i '[[:lower:]]' > > grep -i -o would fail to report some matches; grep -i --color, while not > missing any line containing a match, would fail to color some matches. > > grep would fail to report a match in a multibyte character set other than > UTF-8, if another match occurred earlier in the line but started in the > middle of a multibyte character. > > Various bugs in grep -P, caused by expressions such as [^b] or \S matching > newlines, were fixed. grep -P also supports the special sequences \Z and > \z, and can be combined with the command-line option -z to perform > searches > on NUL-separated records. > > grep would mistakenly exit with status 1 upon error, rather than 2, > as it is documented to do. > > Using options like -1 -2 or -1 -v -2 results in two lines of > context (the last value that appears on the command line) instead > twelve (the concatenation of all the values). This is consistent > with the behavior of options -A/-B/-C. > > Two new command-line options, --group-separator=ARGUMENT and > --no-group-separator, enable further customization of the output > when -A, -B or -C is being used. > > >
