[Top][All Lists]

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

Re: /bin/bash ./configure problem with old /bin/sh bourne shell

From: Eric Blake
Subject: Re: /bin/bash ./configure problem with old /bin/sh bourne shell
Date: Wed, 09 Apr 2014 11:51:10 -0600
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0

On 04/09/2014 08:47 AM, Christian Maeder wrote:
> Hi,
> I've sent the following report to address@hidden, but it may well
> be an autoconf problem.

Thanks for the report.

> Calling "/bin/bash ./configure" causes "SHELL" to (wrongly) become
> "/bin/sh" (for https://gmplib.org/download/gmp/gmp-6.0.0a.tar.xz).

Per the INSTALL document shipped by autoconf (and probably copied into
lots of projects verbatim):

Unfortunately, this technique does not work for 'CONFIG_SHELL' due to an
Autoconf limitation.  Until the limitation is lifted, you can use this

     CONFIG_SHELL=/bin/bash ./configure CONFIG_SHELL=/bin/bash

Running ./configure under an alternate shell, with the goal of having
that shell percolate through uses of $SHELL, requires that you set
CONFIG_SHELL for the duration of the configure run.

You're welcome to try and patch autoconf to behave more sanely for the
future, but that won't help all the existing configure scripts created
with current autoconf versions; so even if you patch autoconf, the
recommendation will still be to use CONFIG_SHELL when using a different
shell than /bin/sh and wanting it to stick.

Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

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