|
From: | Dimitrios Apostolou |
Subject: | Re: config.status and /bin/sh on Solaris |
Date: | Sat, 28 Jan 2017 17:05:03 +0100 (CET) |
User-agent: | Alpine 2.20 (DEB 67 2015-01-07) |
On Sat, 28 Jan 2017, Bob Friesenhahn wrote:
On Sat, 28 Jan 2017, Dimitrios Apostolou wrote:On Fri, 27 Jan 2017, Bob Friesenhahn wrote:I have been using Solaris 10 daily for Autoconf related development since 2005 and have never seen configure select /bin/sh. One reason is that the system normally has /usr/bin/bash installed.Are you missing /usr/bin/bash on your system?Hi, I have it, the installation is a full-sized one so it comes with all utilities. Can you try running the configure script with this environment:PATH=/opt/csw/bin:/usr/xpg4/bin:/usr/bin /usr/xpg4/bin/sh ./configure Then what's the shebang line on top of config.status?I get the same problem you do. The config.status script starts with "/bin/sh" and it fails to execute properly.If I don't specifically execute configure using /usr/xpg4/bin/sh then the config.status script starts with "/bin/bash" and everything is fine.
Thanks for verifying! I'm now getting a similar (same cause it seems) error on a different software compilation, this time on Solaris 11. The common denominator is the tweaked PATH, putting /usr/xpg4/bin before /usr/bin causes havoc. I'll investigate more and report back.
It seems tweaking the PATH in my build environment was not the best idea. :-)
Dimitris
[Prev in Thread] | Current Thread | [Next in Thread] |