Re: [PATCH] Revise the diagnostic output produced when config.guess fails.

2024-05-14 Thread Jacob Bachmeyer
Dmitry V. Levin wrote: On Tue, May 14, 2024 at 01:26:03PM -0400, Zack Weinberg wrote: On Tue, May 14, 2024, at 12:31 PM, Dmitry V. Levin wrote: On Tue, May 14, 2024 at 10:34:11AM -0400, Zack Weinberg wrote: --- /dev/null 2024-05-14 09:16:42.181936154 -0400 +++ .htaccess

Re: [PATCH] Revise the diagnostic output produced when config.guess fails.

2024-05-14 Thread Dmitry V. Levin
On Tue, May 14, 2024 at 01:26:03PM -0400, Zack Weinberg wrote: > On Tue, May 14, 2024, at 12:31 PM, Dmitry V. Levin wrote: > >> > On Tue, May 14, 2024 at 10:34:11AM -0400, Zack Weinberg wrote: > >> >> --- /dev/null 2024-05-14 09:16:42.181936154 -0400 > >> >> +++ .htaccess 2024-05-14 09:32:57.06

Re: [PATCH] Revise the diagnostic output produced when config.guess fails.

2024-05-14 Thread Zack Weinberg
On Tue, May 14, 2024, at 12:31 PM, Dmitry V. Levin wrote: >> > On Tue, May 14, 2024 at 10:34:11AM -0400, Zack Weinberg wrote: >> >> --- /dev/null 2024-05-14 09:16:42.181936154 -0400 >> >> +++ .htaccess 2024-05-14 09:32:57.063158152 -0400 >> >> @@ -0,0 +1,4 @@ >> >> +Redirect permanent /soft

Re: [PATCH] Revise the diagnostic output produced when config.guess fails.

2024-05-14 Thread Dmitry V. Levin
On Tue, May 14, 2024 at 10:34:11AM -0400, Zack Weinberg wrote: > On Tue, May 14, 2024, at 9:51 AM, Alyssa Ross wrote: > >> Turns out /software/config is under our control, in the same way that > >> /software/autoconf is. It should be sufficient to apply this patch to the > >> config-web CVS reposi

Re: [PATCH] Revise the diagnostic output produced when config.guess fails.

2024-05-14 Thread Zack Weinberg
On Tue, May 14, 2024, at 9:51 AM, Alyssa Ross wrote: >> Turns out /software/config is under our control, in the same way that >> /software/autoconf is. It should be sufficient to apply this patch to the >> config-web CVS repository (https://savannah.gnu.org/cvs/?group=config): >> >> --- /dev/null

Re: [PATCH] Revise the diagnostic output produced when config.guess fails.

2024-05-14 Thread Alyssa Ross
"Zack Weinberg" writes: > On Mon, May 13, 2024, at 11:33 PM, Jacob Bachmeyer wrote: >> Zack Weinberg wrote: >>> On Thu, Apr 4, 2024, at 6:50 PM, Jacob Bachmeyer wrote: Zack Weinberg wrote: > (N.B. The Savannah URLs look a little too cgit-specific to trust > that they will still be go

Re: [PATCH] Revise the diagnostic output produced when config.guess fails.

2024-05-14 Thread Zack Weinberg
On Mon, May 13, 2024, at 11:33 PM, Jacob Bachmeyer wrote: > Zack Weinberg wrote: >> On Thu, Apr 4, 2024, at 6:50 PM, Jacob Bachmeyer wrote: >>> Zack Weinberg wrote: (N.B. The Savannah URLs look a little too cgit-specific to trust that they will still be good twenty years from now. >>> I w

Re: [PATCH] Revise the diagnostic output produced when config.guess fails.

2024-05-13 Thread Jacob Bachmeyer
Zack Weinberg wrote: On Thu, Apr 4, 2024, at 6:50 PM, Jacob Bachmeyer wrote: Zack Weinberg wrote: [...] (N.B. The Savannah URLs look a little too cgit-specific to trust that they will still be good twenty years from now. Can we maybe get the www.gnu.org admins to make /software/???/con

Re: [PATCH] Revise the diagnostic output produced when config.guess fails.

2024-05-13 Thread Zack Weinberg
On Thu, Apr 4, 2024, at 6:50 PM, Jacob Bachmeyer wrote: > Zack Weinberg wrote: >>The duplicate uname -m/-r/-s/-v output is replaced with >>diagnostics of the availability of uname and a C compiler. > > I would suggest keeping the duplicate uname output; config.guess is > straightforward bu

Re: [PATCH] Revise the diagnostic output produced when config.guess fails.

2024-04-04 Thread Jacob Bachmeyer
Zack Weinberg wrote: From: Zack Weinberg The output now varies based on which of three different situations is detected: 1. If config.guess’s embedded timestamp is more than three years old, we instruct the user to update it from Savannah, and we don’t say anything else. 2. If we tried

Re: [PATCH] Revise the diagnostic output produced when config.guess fails.

2024-04-04 Thread Petr Vorel
> From: Zack Weinberg > The output now varies based on which of three different situations is > detected: > 1. If config.guess’s embedded timestamp is more than three years old, >we instruct the user to update it from Savannah, and we don’t say >anything else. > 2. If we tried to use a

[PATCH] Revise the diagnostic output produced when config.guess fails.

2024-04-04 Thread Zack Weinberg
From: Zack Weinberg The output now varies based on which of three different situations is detected: 1. If config.guess’s embedded timestamp is more than three years old, we instruct the user to update it from Savannah, and we don’t say anything else. 2. If we tried to use a C compiler but