On 2024-08-04 13:44, Bob Friesenhahn wrote:
The lines appear exactly as you provided.
Exactly what byte offset in the 'configure' script contains the offending text? That is, if the 'configure' text looks like this:
as_write_fail=0 cat >$CONFIG_STATUS <<_ASEOF || as_write_fail=1 #! $SHELL # Generated by $as_me. # Run this file to recreate the current configuration. # Compiler output produced by configure, useful for debugging # configure, is in config.log if it exists. debug=false ac_cs_recheck=false ac_cs_silent=false SHELL=\${CONFIG_SHELL-$SHELL} export SHELL _ASEOF cat >>$CONFIG_STATUS <<\_ASEOF || as_write_fail=1 ## -------------------- ## ## M4sh Initialization. ## ## -------------------- ##
... and the "export SHELL" line ends at byte offset 4096, then I'd guess it's a buffering bug in the shell. If the shell is actually ksh93 I wouldn't be surprised.
That also would explain why an older GraphicsMagick doesn't see the problem: the line in question happens to not appear exactly at a buffer boundary.
Of course I'm just guessing. You might try running 'bash ./configure' instead of './configure'.
