Thanks for the logs. I think I see the bug now. I installed the attached
patch. Please give it a try, or (this may be simpler) a workaround is to
make sure that GREP and EGREP are not set in your environment (if you
need a better grep, put it in your PATH instead).From 14a41a9e700ad8a87d55a95c0dfdf25bf2f8d474 Mon Sep 17 00:00:00 2001
From: Paul Eggert <[email protected]>
Date: Mon, 13 Apr 2026 10:16:05 -0700
Subject: [PATCH] build: fix GREP/EGREP envvar glitch
* configure.ac (GREP, EGREP): Remove misguided attempt to
advise people installing on Solaris. This attempt failed
when people set GREP or EGREP to useful values.
Problem reported by Dennis Clarke (Bug#80774).
---
configure.ac | 9 ---------
1 file changed, 9 deletions(-)
diff --git a/configure.ac b/configure.ac
index e14f4aa..ac15aea 100644
--- a/configure.ac
+++ b/configure.ac
@@ -22,15 +22,6 @@ AC_INIT([GNU grep],
m4_esyscmd([build-aux/git-version-gen .tarball-version]),
[[email protected]])
-if test -n "$GREP" || test -n "$EGREP"; then
- AC_MSG_ERROR(
- [no working 'grep' found
- A working 'grep' command is needed to build GNU Grep.
- This 'grep' should support -e and long lines.
- On Solaris 10, install the package SUNWggrp or SUNWxcu4.
- On Solaris 11, install the package text/gnu-grep or system/xopen/xcu4.])
-fi
-
AC_CONFIG_AUX_DIR([build-aux])
AC_CONFIG_SRCDIR([src/grep.c])
AC_DEFINE([GREP], 1, [We are building grep])
--
2.51.0
