Hello, Lars! I don't object against installing your patch as a temporary measure. Ideally, config.status should check one thing - that it's run by the same shell and on the same machine as configure - everything else must be hardcoded. But I realize that we have limited resources now, and that cleanups must stop at some point to give way to small fixes, if we are going to release 2.50 at all. > : Sorry, I meant concurrency. > > Configure-test concurrency will be introduced in Autoconf 3.0 :) Expect > a lot of sub-shelling and here-doc scripts... Very good point. 2.50 is not the last version and we cannot do everything right now. Regards, Pavel Roskin
- [patch] remove config.status race condition Lars J. Aas
- Re: [patch] remove config.status race condition Pavel Roskin
- Re: [patch] remove config.status race condition Lars J. Aas
- Re: [patch] remove config.status race condition Alexandre Oliva
- Re: [patch] remove config.status race condition Pavel Roskin
- Re: [patch] remove config.status race condition Alexandre Oliva
- Re: [patch] remove config.status race condition Pavel Roskin
- Re: [patch] remove config.status race condition Lars J. Aas
- Re: [patch] remove config.status race condition Pavel Roskin
- Re: [patch] remove config.status race condition Alexandre Oliva
- Re: [patch] remove config.status race condition Akim Demaille
- Re: [patch] remove config.status race condition Lars J. Aas
- Re: [patch] remove config.status race condition Pavel Roskin
- Re: [patch] remove config.status race condition Akim Demaille
- RE: [patch] remove config.status race condition Tim Van Holder
- Re: [patch] remove config.status race condition Pavel Roskin
- Re: [patch] remove config.status race condition akim
- Re: [patch] remove config.status race condition Akim Demaille
- Re: [patch] remove config.status race condition Pavel Roskin