No errors on RHEL7+autoconf2.71
Puzzling. Can you easily try RHEL8 or one of its derivatives?
It surprises me that that is the culprit, but it seems possible.
I'm using autoconf-2.71, make-4.3, etc., compiled from source, but am
using the OS-provided coreutils. I think I'll try compiling that
On Thu, Oct 6, 2022, at 1:04 PM, Zack Weinberg wrote:
> On 2022-10-04 6:58 PM, Karl Berry wrote:
>> Perhaps easier to debug: there are two targets to be run before making a
>> release, check-no-trailing-backslash-in-recipes and check-cc-no-c-o,
>> to try to ensure no reversion wrt these features. A
On 2022-10-04 6:58 PM, Karl Berry wrote:
With Zack's latest Python fixes, I was hoping to move towards an
Automake release, but I find myself stymied by apparently random and
unreproducible test failures. I haven't exhausted every conceivable
avenue yet, but I thought I would write in hopes that
> On 4 Oct 2022, at 23:58, Karl Berry wrote:
>
> With Zack's latest Python fixes, I was hoping to move towards an
> Automake release, but I find myself stymied by apparently random and
> unreproducible test failures. I haven't exhausted every conceivable
> avenue yet, but I thought I would writ
On Wed, 2022-10-05 at 15:24 -0600, Karl Berry wrote:
> What troubles me most is that there's no obvious way to debug any
> test failure involving parallelism, since they go away with serial
> execution. Any ideas about how to determine what is going wrong in
> the parallel make? Any way to make p
