[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Starting /bin/sh in output configure file
From: |
R0b0t1 |
Subject: |
Re: Starting /bin/sh in output configure file |
Date: |
Thu, 13 Jul 2017 21:56:20 -0500 |
On Thu, Jul 13, 2017 at 9:46 PM, Paul Eggert <address@hidden> wrote:
> Mohammad Akhlaghi wrote:
>>
>> It would be great if this first line of the configure script would also
>> check for `CONFIG_SHELL'
>
>
> Unfortunately this does not work, as the operating system handles the first
> line before the configure script starts.
>
A hardcoded binary path isn't portable, the correct solution is to use
`env sh`. Typically this is seen as:
#!/usr/bin/env sh
Which technically causes the same problem Mr. Akhlagi was
experiencing, but on most desktop Unixes the location of `env` is more
predictable than the location of various interpreters.
R0b0t1.