Re: config.log for sunos

[Paul Eggert]

I went back and look at the original bug report as forwarded in
<http://mail.gnu.org/pipermail/bug-autoconf/2002-October/001909.html>
and noticed lines like this that could well be explaining the problem:

> + cat 
> ./configure: /tmp/sh295665: No such file or directory

That bug report didn't mention the SunOS version, but that "No such
file or directory" message looks very much like he's being bitten by
the following Sun bugids:

1123136 /bin/sh uses wrong PID for name of the temporary file created by cat << 
EOF
1134744 in-line input redirection into awk after exec of stdin and stdout
1170383 "here documents" within "command substitutions" fail much of the time 
in 4.1.x

The bug is reportedly not present in the SunOS 4.1.1 /bin/sh, or in
the SunOS 4.1.4 /bin/sh.  If you're running SunOS 4.1.2 or 4.1.3, you
should be able to work around the problem by using SunOS 4.1.1 /bin/sh
(if you can get a copy off your backup tapes, it should work just fine
in SunOS 4.1.2 and 4.1.3), or by using some other shell like pdksh or
bash.

For more on this subject, please see the thread that starts here:

Suspected bug with Autoconf built configures and SunOS 4.1.3_U1
http://mail.gnu.org/pipermail/autoconf/2002-August/013796.html


> Date: Thu, 24 Oct 2002 17:41:05 -0700 (PDT)
> From: Scott Deifik <address@hidden>
>
> I believe that my PATH at the time was:
> PATH=/usr/openwin/bin:.:/usr/ucb:/bin:/usr/bin:/usr/etc:/usr/local/bin:/usr/bin/X11:/usr/lib/X11/bin

I vaguely recall having problems with /usr/ucb/cc on SunOS 4.1.x, but
it was long ago so I don't remember the details.  I suggest using
/usr/bin/cc instead.  But I think this is a separate issue.