Dmitry V. Levin wrote:
>On Tue, Dec 01, 2020 at 04:40:07PM -0700, Karl Berry wrote:
>>
>> It's time to join the 1990s and replace the backtick substitutions in
>> config.guess and config.sub with the $(..) command substitution
>>
>> I admit I don't understand the reason behind this last cha
Hi Karl,
I'm Cc'ing Ben who is the author of this change in hope he would be able
to comment.
On Wed, Dec 02, 2020 at 04:19:10PM -0700, Karl Berry wrote:
> Solaris 10
>
> Well, it is true that Solaris 10 /bin/sh does not understand $(...).
>
> "Configure scripts will automatically locat
Solaris 10
Well, it is true that Solaris 10 /bin/sh does not understand $(...).
"Configure scripts will automatically locate a shell that supports
Yes, I saw that too. Which is fine for autoconf's configure scripts (and
I'm very glad they're doing it), but what about when config.{guess,s
Hi Karl,
On Tue, Dec 01, 2020 at 04:40:07PM -0700, Karl Berry wrote:
> Hi Dmitry,
>
> It's time to join the 1990s and replace the backtick substitutions in
> config.guess and config.sub with the $(..) command substitution
>
> I admit I don't understand the reason behind this last change
Hi Dmitry,
It's time to join the 1990s and replace the backtick substitutions in
config.guess and config.sub with the $(..) command substitution
I admit I don't understand the reason behind this last change that Ben did.
What's wrong with `...`?
No question $(...) is nicer in principle,
It's time to join the 1990s and replace the backtick substitutions in
config.guess and config.sub with the $(..) command substitution
syntax. This will mean that from now on, config.guess/.sub will
require a POSIX shell. If there are any systems still running that
want to use a contemporary version
