buggrep - Bugs: bug #22818, grep installation requires grep


You are not allowed to post comments on this tracker with your current authentication level.

bug #22818: grep installation requires grep

Submitted by:  Olli Savia <ops>
Submitted on:  Thu 03 Apr 2008 08:09:20 AM UTC  
Category:  None Severity:  3 - Normal
Item Group:  None Status:  Fixed
Privacy:  Public Assigned to:  Stepan Kasal <kasal>
Open/Closed:  Closed

Tue 28 Jun 2011 08:40:57 AM UTC, comment #5: 

This was fixed in 2.8 by commit 21de5e0 (configure: remove dependency on grep that supports long lines and -e, 2010-11-14).

Thank you for the bug report. This bug has been fixed in the
latest release of grep. You may download it from

Paolo Bonzini <bonzini>
Thu 03 Jul 2008 08:15:08 PM UTC, comment #4: 

Sounds good to me. I can give it a test run when it is implemented.

Olli Savia <ops>
Tue 27 May 2008 12:33:41 PM UTC, comment #3: 

Ralf suggested on the Autoconf list to add a loosened check for grep to GNU grep's configure.ac and set GREP, before AC_PROG_GREP comes in.
I believe this is the way to go.

Stepan Kasal <kasal>
Project MemberIn charge of this item.
Thu 03 Apr 2008 10:20:10 AM UTC, comment #2: 

OOPS, correction:
I do not think this should be reported to the Autoconf team.
In order to check for some C headers, configure wants to grep them.
To perform this reliably, it needs checks for a "reasonable" grep.

For this, it calls AC_PROG_GREP, which ensures that the grep binary can handle multiple -e options.  It is possible that this feature is not needed in this particulat configure script, but it is generally a good idea to include that property in the definition of a "reasonable" grep implementation.

The workaround is not that difficult, after all.  Bootstrapping on a weird platform is often difficult...

Please feel free to submit the problem to bug-autoconf yourself, if you are not satisfied with the above explanation.

Stepan Kasal <kasal>
Project MemberIn charge of this item.
Thu 03 Apr 2008 10:04:05 AM UTC, comment #1: 

  thank you for your bug report;
  as a workaround, try calling

./configure GREP=/usr/xpg4/bin/grep
  (or whereever your best grep lives)

I'm reporting this to bug-autoconf mail list.

Stepan Kasal <kasal>
Project MemberIn charge of this item.
Thu 03 Apr 2008 08:09:20 AM UTC, original submission:  

I'm trying to install grep-2.5.3 on LynxOS but configure thinks that grep provided by LynxOS is not good enough. Is there workaround for this?

ops@lynxppc01 ~/tmp/grep-2.5.3 $ ./configure
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
/users/osa/tmp/grep-2.5.3/missing: /users/osa/tmp/grep-2.5.3/missing: No such file or directory
configure: WARNING: `missing' script is too old or missing
checking for a thread-safe mkdir -p... ./install-sh -c -d
checking for gawk... gawk


checking for grep that handles long lines and -e... configure: error: no acceptable grep could be found in /users/osa/bin:/usr/X11R6/bin:/usr/local/bin:/bin:/etc:/net:/usr/bin:/usr/local/bin:/bin/radstone:.:/bin/radstone:.:/usr/xpg4/bin


Olli Savia <ops>


No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by bonzini (Posted a comment)
  • -email is unavailable- added by kasal (Posted a comment)
  • -email is unavailable- added by ops (Submitted the item)

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.




    Follow 5 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2011-06-28 bonzini StatusConfirmed => Fixed
        Open/ClosedOpen => Closed
    2008-05-27 kasal StatusWont Fix => Confirmed
    2008-04-03 kasal StatusNone => Wont Fix
        Assigned toNone => kasal

    Back to the top

    Powered by Savane 3.6