Re: config.sub/config.guess using nonportable $(...) substitutions

2021-03-09 Thread Todd C. Miller
On Tue, 09 Mar 2021 14:11:36 -0700, Warren Young wrote: > That’s the real trick, isn’t it? We have to set *some* threshold for droppin > g support for old platforms. I expect Autoconf isn’t compatible with Ultrix > any more, for instance. That's a good reminder that we've been here before. I

Re: config.sub/config.guess using nonportable $(...) substitutions

2021-03-09 Thread Zack Weinberg
On Tue, Mar 9, 2021 at 5:00 PM Tim Rice wrote: > On Tue, 9 Mar 2021, Warren Young wrote: > > On Mar 9, 2021, at 1:26 PM, Paul Eggert wrote: > > Solaris 10 dates from early 2005. We gave it 16 years of direct support, > > and now it’s on a sort of “extended” support if you point Autoconf > >

Re: config.sub/config.guess using nonportable $(...) substitutions

2021-03-09 Thread Nick Bowler
On 09/03/2021, Warren Young wrote: > On Mar 9, 2021, at 1:26 PM, Paul Eggert wrote: >> >>> 1) There is no actual benefit to using $(...) over `...`. >> >> I disagree with that statement on technical grounds (not merely cosmetic >> grounds), as I've run into real problems in using `...` along

Re: config.sub/config.guess using nonportable $(...) substitutions

2021-03-09 Thread Tim Rice
On Tue, 9 Mar 2021, Warren Young wrote: > On Mar 9, 2021, at 1:26 PM, Paul Eggert wrote: > Solaris 10 dates from early 2005. We gave it 16 years of direct support, and > now it’s on a sort of “extended” support if you point Autoconf configure > scripts at a reasonable shell. The thing is, it

Re: config.sub/config.guess using nonportable $(...) substitutions

2021-03-09 Thread Paul Eggert
On 3/9/21 12:26 PM, Paul Eggert wrote: On 3/9/21 11:09 AM, Karl Berry wrote: I fully disagree. (Along with, it seems, everyone else except you and Ben.) Ben is the main person to convince here, since he's the maintainer. Oh, my mistake. Ben has stepped down, so I should have written that

Re: config.sub/config.guess using nonportable $(...) substitutions

2021-03-09 Thread Warren Young
On Mar 9, 2021, at 1:26 PM, Paul Eggert wrote: > >> 1) There is no actual benefit to using $(...) over `...`. > > I disagree with that statement on technical grounds (not merely cosmetic > grounds), as I've run into real problems in using `...` along with " and \, Me too, plus nesting. The

Re: config.sub/config.guess using nonportable $(...) substitutions

2021-03-09 Thread Paul Eggert
On 3/9/21 11:09 AM, Karl Berry wrote: I fully disagree. (Along with, it seems, everyone else except you and Ben.) Ben is the main person to convince here, since he's the maintainer. I am a bit disenheartened to see that Ben hasn't sent any email to this list since he installed the change in

Re: config.sub/config.guess using nonportable $(...) substitutions

2021-03-09 Thread Paul Eggert
On 3/9/21 5:57 AM, Bob Friesenhahn wrote: It seems that config.guess and Autotools packages are picking winners and losers.  It is not clear where the bar has been set. I prefer to draw the line at systems that are no longer supported by their own suppliers. For Solaris, that means I worry

Re: config.sub/config.guess using nonportable $(...) substitutions

2021-03-09 Thread Karl Berry
At some point, failing to support $(...) is in the same ballpark FWIW, I fully disagree. (Along with, it seems, everyone else except you and Ben.) 1) There is no actual benefit to using $(...) over `...`. It is purely cosmetic. In other scripts, fine. In config.*, no. 2) Using $(...)

Re: config.sub/config.guess using nonportable $(...) substitutions

2021-03-09 Thread Bob Friesenhahn
On Mon, 8 Mar 2021, Paul Eggert wrote: Except maybe for Solaris 10, shells that don't grok $(...) are museum pieces now. And anybody on Solaris 10 (which occasionally includes me, as my department still uses Solaris 10 on some machines) can easily run a better shell like /bin/ksh. It's a bit