On 4/13/26 02:43, Paul Eggert wrote:
On 2026-04-12 17:41, Dennis Clarke wrote:

alpha$ ./configure --prefix=/opt/bw --disable-silent-rules \
 > --enable-dependency-tracking --enable-threads=posix \
 > --enable-gcc-warnings=no \
 > --with-libsigsegv --with-libsigsegv-prefix=/opt/bw \
 > --with-libiconv-prefix=/opt/bw --with-gnu-ld \
 > --with-packager='GENUNIX Mon Apr 13 00:30:15 UTC 2026' 2>&1 | tee `pwd`.config.log
configure: 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.
alpha$ ls -la config.log
-rw-r--r--  1 dclarke  devl  62358 Apr 13 00:30 config.log
alpha$

This is bizarre. Are we into some strange autotools hell rat-hole here ?

If that's all the output you saw, there is indeed something funny going on on your platform.


Oh, I agree. You should see the wonderland of problems with GCC :

    https://gcc.gnu.org/pipermail/gcc-help/2026-April/144929.html

However that is a whole other can of ... something.

There is a typo in your script. The output of tee was put into `pwd`.config.log, which is probably not what you want. However, that typo would not explain the output you show.


oops

alpha$
alpha$ /opt/bw/bin/patch --verbose --backup -p1 -i /mnt/users/dclarke/backup/centauri/20260413/grep.diff
Hmm...  Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|diff -ru grep-3.12/configure grep-3.12a/configure
|--- grep-3.12/configure        2025-04-10 09:02:07.000000000 -0700
|+++ grep-3.12a/configure       2026-04-12 10:20:30.446800680 -0700
--------------------------
patching file configure
Hunk #1 succeeded at 8132.
Hunk #2 succeeded at 8266.
Hunk #3 succeeded at 63018.
Hmm...  Ignoring the trailing garbage.
done
alpha$

alpha$
alpha$ date -u
Mon Apr 13 15:45:51 UTC 2026
alpha$ ./configure --prefix=/opt/bw --disable-silent-rules \
> --enable-dependency-tracking --enable-threads=posix \
> --enable-gcc-warnings=no \
> --with-libsigsegv --with-libsigsegv-prefix=/opt/bw \
> --with-libiconv-prefix=/opt/bw --with-gnu-ld \
> --with-packager='GENUNIX Mon Apr 13 15:45:51 UTC 2026'
configure: 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.
alpha$


Try running it without piping the result into "tee". If that doesn't seem to work, try running it with "sh -x ./configure", without any other options.


Well now I get thousands of lines of output that I do need to capture somewhere.

Inside config.log we still see the same message :


## ----------- ##
## Core tests. ##
## ----------- ##

configure:5287: looking for aux files: config.rpath compile config.guess config.sub missing install-sh
configure:5300:  trying ./build-aux/
configure:5329:   ./build-aux/config.rpath found
configure:5329:   ./build-aux/compile found
configure:5329:   ./build-aux/config.guess found
configure:5329:   ./build-aux/config.sub found
configure:5329:   ./build-aux/missing found
configure:5311:   ./build-aux/install-sh found
configure:5466: 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.


I will try to capture those thousands of lines of output.

For the record, if I take GNU grep out of the PATH ( just hide it with
a rename ) then the configure procedure runs fine.  This may even be
a problem with my shell wherein I did compile bash with all the latest
patches and then restricted it to the bare minimal feature set :

$ ../bash-5.3_009/configure --prefix=/opt/bw --enable-minimal-config \
--enable-history --enable-job-control --enable-alias \
--enable-strict-posix-default --enable-xpg-echo-default \
--enable-threads=posix --with-gnu-ld \
--with-libiconv-prefix=/opt/bw --without-libintl-prefix

Which works well enough however that may be a variable in this mess.

I will need to use "tee" to direct the output into `pwd`.config.log
which results in a log file in the parent directory with the correct
name.

alpha$
alpha$ $SHELL -x ./configure --prefix=/opt/bw \
> --disable-silent-rules --enable-dependency-tracking \
> --enable-threads=posix --enable-gcc-warnings=no \
> --with-libsigsegv --with-libsigsegv-prefix=/opt/bw \
> --with-libiconv-prefix=/opt/bw --with-gnu-ld \
> --with-packager='GENUNIX Mon Apr 13 15:45:51 UTC 2026' 2>&1 | tee `pwd`.config.log
.
.
.  many many lines
.

That works like a charm to capture everything into two log files :

alpha$
alpha$ ls -la `pwd`.config.log ./config.log
-rw-r--r--  1 dclarke  devl   62358 Apr 13 16:30 ./config.log
-rw-r--r-- 1 dclarke devl 622228 Apr 13 16:30 /opt/bw/build/grep-3.12_OpenBSD_alpha_21164.007.config.log
alpha$

The config.log in this build dir claims the usual :



## ----------- ##
## Core tests. ##
## ----------- ##

configure:5287: looking for aux files: config.rpath compile config.guess config.sub missing install-sh
configure:5300:  trying ./build-aux/
configure:5329:   ./build-aux/config.rpath found
configure:5329:   ./build-aux/compile found
configure:5329:   ./build-aux/config.guess found
configure:5329:   ./build-aux/config.sub found
configure:5329:   ./build-aux/missing found
configure:5311:   ./build-aux/install-sh found
configure:5466: 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.


However we now have almost 15000 lines of detailed trace stuff :

alpha$ wc -l  /opt/bw/build/grep-3.12_OpenBSD_alpha_21164.007.config.log
   14787 /opt/bw/build/grep-3.12_OpenBSD_alpha_21164.007.config.log
alpha$

Is there anything obvious to look for before I compress all that and
abuse the bug system with yet another massive log file attachment?

$ ls -lAo
total 66
-rw-r--r-- 1 dclarke 10504 Apr 13 16:42 grep-3.12_OpenBSD_alpha_21164.007.config.log.xz -rw-r--r-- 1 dclarke 42000 Apr 13 16:42 grep-3.12_OpenBSD_alpha_21164.007.trace.log.xz
-rw-r--r-- 1 dclarke   891 Apr 13 00:09 grep.diff
-rw-r--r-- 1 dclarke  1394 Apr 13 00:34 readme
$

So there we see a "config.log" as well as a verbose "trace.log".

--
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken

Attachment: grep-3.12_OpenBSD_alpha_21164.007.config.log.xz
Description: application/xz

Attachment: grep-3.12_OpenBSD_alpha_21164.007.trace.log.xz
Description: application/xz

Reply via email to