2009-03-17 16:12:22 C. Michael Pilato napisał(a):
> Arfrever Frehtes Taifersar Arahesis wrote:
> > 2009-03-17 15:02 C. Michael Pilato <cmpilato_at_collab.net> napisał(a):
> >> I think Kamesh determined the problem. (Kamesh, please correct me if I'm
> >> wrong.)
> >>
> >> configure looks for a "suitable grep", but the criteria is simply "supports
> >> long lines" and "supports the -e argument". Our buildstuffs expect grep to
> >> have support for the -o argument, too, though. Our Solaris build
> >> environment has both Solaris grep and GNU grep, but Solaris grep (which
> >> doesn't support -o) was getting chosen by configure.
> >
> > You can try:
> > GREP=/path/to/GNU/grep ./configure ${OPTIONS}
> > or
> > EGREP=/path/to/GNU/grep ./configure ${OPTIONS}
>
> Sure you can. But isn't it better to make configure do what's supposed to
> do: detect what the build needs?
I committed ugly workaround in r36741.
You can nominate it for backport to the 1.6.x branch, if you want.
--
Arfrever Frehtes Taifersar Arahesis
Received on 2009-03-21 21:29:35 CET