Re: CVS autoconf full testsuite failure under Tru64

[Nicolas Joly]

On Wed, Aug 29, 2001 at 01:01:21PM +0200, Akim Demaille wrote:
> 
> | address@hidden [temp/autoconf]> /bin/sh
> | $ echo `cat<<eof
> | > FOOBAR
> | > eof`
> | /tmp/sh936101: cannot open
> | 
> | $ echo `cat<<\eof
> | > FOOBAR
> | > eof`
> | FOOBAR
> 
> OK, this explains the first failure, but not the second.  The culprit
> is:
> 
> cat >&5 <<_CSEOF
> 
> `sed 'h;s/./-/g;s/^.../## /;s/...$/ ##/;p;x;p;x' <<_ASBOX
> ## Running \$as_me. ##
> _ASBOX`
> 
> This file was extended by GNU Autoconf $as_me 2.52c, which was
> generated by GNU Autoconf 2.52c.  Invocation command line was
> 
>   CONFIG_FILES    = $CONFIG_FILES
>   CONFIG_HEADERS  = $CONFIG_HEADERS
>   CONFIG_LINKS    = $CONFIG_LINKS
>   CONFIG_COMMANDS = $CONFIG_COMMANDS
>   $ $@
> on `(hostname || uname -n) 2>/dev/null | sed 1q`
> 
> _CSEOF
> 
> You did spot the first error message, but not the second:
> 
> + sed h;s/./-/g;s/^.../## /;s/...$/ ##/;p;x;p;x 
> ./config.status: /tmp/sh1286373: cannot open
> + sed 1q 
> ./config.status: /tmp/sh1286373: cannot open
> 
> can it be a consequence of the first one?

I think so. The failure seems to be reported by each of the 2
heredocs.

> cat <<EOF
> `cat<<eof
> FOOBAR
> eof
> `
> `echo toto`
> EOF

address@hidden [temp/autoconf]> /bin/sh
$ cat <<EOF
> `cat<<eof
> FOOBAR
> eof
> `
> `echo toto`
> EOF
/tmp/sh1350693: cannot open
/tmp/sh1350693: cannot open
$ 

> and
> 
> cat <<EOF
> `echo toto`
> `cat<<eof
> FOOBAR
> eof
> `
> EOF

$ cat <<EOF
> `echo toto`
> `cat<<eof
> FOOBAR
> eof
> `
> EOF
/tmp/sh1350694: cannot open
/tmp/sh1350694: cannot open
$ 

-- 
Nicolas Joly

Informatique Scientifique
Institut Pasteur, Paris.