Re: possible grep bug: -i switch with character class

[Chris Jerdonek]

On Wed, Nov 4, 2009 at 12:50 AM, Bob Proulx <address@hidden> wrote:

> Alternatively I would grab the latest stable grep sources and compile
> them yourself.  Grep compiles easy and shouldn't be a problem to
> compile from source.

I had trouble compiling directly from source by following the INSTALL
file.  For example, I got the following error when running "make":

search.c:44:19: error: pcre.h: No such file or directory

What I did instead was get the latest version v2.5.4 using MacPorts (
http://www.macports.org/ ), which seems to have supplanted
DarwinPorts.

I'm not seeing the issue in v2.5.4 even with the UTF8 locale, which is
good.  You can see more info I posted in a follow-up to my bug report.

> Also posting to bug-gnu-utils for grep is okay.  It is a generic
> catchall for all things gnu.  You will have people like me here
> helping.  But for grep there is a specific mailing list just for grep
> bugs.  For more follow-up you would reach the grep maintainers
> directly at address@hidden instead of here.  That is the bug
> reporting address listed in the grep --help output.

I apologize for posting here instead of to the greps bug list.  The
man page listed this e-mail address (though the man page dates to
2002).  I did learn a lot from you though, so I appreciate all your
help.

All of this makes me wonder how Apple decides what version of software
to include in its Mac OS X versions.  Let me know if you have any
insight!

Thanks again!
--Chris