Re: non portable sed scripts

[Tim Rice]

On Fri, 19 May 2006, Ralf Wildenhues wrote:

> Hi Tim,
> 
> * Tim Rice wrote on Fri, May 19, 2006 at 06:57:48PM CEST:
> > 
> > Autoconf version 2.59c
> > 
> > I had an opportunity to run a configure script generated with 2.59c
> > (ftp://ftp.gnu.org/gnu/coreutils/coreutils-5.95.tar.gz) and found
> > that it failed.
> 
> > config.status: creating config.h
> > UX:sed: ERROR: Command garbled: HAVE_DECL_STRNDUP\)[         
> > (].*$,\1define\2 0 ,
> 
> I'm pretty sure the syntax of the sed script is ok.  It's probably that
> your sed has a length restriction.  We check the 99 commands limit, but
> not the 2000 characters limit any more...  :-/
> 
> This particular sed script seems to have around 7200 characters before
> the failing line though.  So what's the limit on your system?

You may well be right.
Unknown, I don't have source. :-(

> 
> To get at the individual sed scripts for config.h:
> - in config.status, search for lines
>     sed -f "$tmp/defines.sed" "$tmp/out..." >"$tmp/out..."
>   and rename the file "$tmp/defines.sed" afterwards, so it's not
>   overwritten by the next file.
> 
> - Then, watch
>     sh -x ./config.status -d

Hmm, "sh -x ./config.status -d" generates a good config.h
The config.h generated at configure time had just the first line.

>   and look at the sed scripts.

They look fine.

[hours and much testing later]

It must be some obscure shell bug.
If I "ksh configure" it works fine.

To answer Paul's question, This is UnixWare 7.1.1
I don't see the problem on my UnixWare 7.1.4 box.
Even my old UnixWare 2.03 box does OK.

I'd say it's not a bug. Sorry for the noise.
 
> Boy, I hope this isn't so difficult to fix, with all that reworking done
> to the config.status code.
> 
> Cheers, and thanks for reporting this!
> Ralf
> 

-- 
Tim Rice                                Multitalents    (707) 887-1469
address@hidden