[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: SunOS 4.1.4 configure failure

From: Paul Eggert
Subject: Re: SunOS 4.1.4 configure failure
Date: 23 Oct 2003 10:45:26 -0700
User-agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3

Roland Roberts <address@hidden> writes:

> Upgrading bash is *maybe* an option; I'm exploring that.  

That would be the easiest for all concerned, I suspect.

However, if you want Autoconf-generated scripts to be portable to
ancient Bash versions, you'll need to supply a simple and cheap test
case that illustrates the Bash bug on your host.  We can fold that
test case into Autoconf so that when it searches for a suitable shell,
it rejects shells that have the bug.  You'll have to help us test the
result, too, as nobody runs Bash 1.14.3 any more (outside of museums,
zoos and insane asylums :-).

> I've attempted to run configure via
>     /bin/sh -c "CONFIG_SHELL=/bin/sh configure"
> which produces numerous errors like so
>     configure: /tmp/sh257515: No such file or directory

It looks like you're being bitten by one or more of the following Sun

1123136 /bin/sh uses wrong PID for name of the temporary file created by cat << 
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

You should be able to work around the problem by using SunOS 4.1.1
/bin/sh (it should work just fine in later SunOS versions), or by
using some other shell like pdksh or a fixed 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

reply via email to

[Prev in Thread] Current Thread [Next in Thread]