time for Autoconf 2.72 (was: On time64 and Large File Support)

2023-02-02 Thread Paul Eggert

On 2/1/23 22:43, Sam James wrote:

Unfortunately, I think we've missed the Debian freeze I think, but it is what 
it is there
(was hoping to get it in there so we could benefit from the large number of 
people who make dist tarballs on Debian).


Oh well. As you say, it is what it is.

Since there's been no comment about that documentation change I 
installed it in Autoconf master on Savannah. I also installed the result 
of a 'make fetch'.


As far as I know, the next Autoconf release is good to go. Unfortunately 
I can't test Autoconf as well as Zack tested it. However, it appears 
that releasing what we've got would be better than not releasing it so 
I'm hoping that we can release Autoconf 2.72 soon, even if it's not as 
well tested as Autoconf 2.71 was.


Comments welcome.



Re: time for Autoconf 2.72 (was: On time64 and Large File Support)

2023-02-02 Thread Zack Weinberg
Due to a series of crises with my day job, the earliest I can promise to do 
_anything_ Autoconf related is early March. If you have time to make a release 
before then, please do not wait for me.

zw



c.m4: Move C++ comments to use __STDC_VERSION__ as the first test for C99

2023-02-02 Thread Detlef Riekenberg
Using __STDC_VERSION__ as first test for C99 looks better and is similar to the 
C89 and C11 tests.

Resynced to current git

--
Regards, Detlef


From bc14044f81d4ee31e9823e58a06baabae19e10de Mon Sep 17 00:00:00 2001
From: Detlef Riekenberg 
Date: Thu, 2 Feb 2023 23:31:24 +0100
Subject: [PATCH] c.m4: Move C++ comments to use __STDC_VERSION__ as the first test for C99

Using __STDC_VERSION__ as first test for C99 looks better and is similar to the C89 and C11 tests

--
Regards, Detlef

---
 lib/autoconf/c.m4 | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/lib/autoconf/c.m4 b/lib/autoconf/c.m4
index fef6c516d..e02495abf 100644
--- a/lib/autoconf/c.m4
+++ b/lib/autoconf/c.m4
@@ -1200,11 +1200,13 @@ AC_DEFUN([_AC_C_C99_TEST_GLOBALS],
 [m4_divert_text([INIT_PREPARE],
 [[# Test code for whether the C compiler supports C99 (global declarations)
 ac_c_conftest_c99_globals='
-// Does the compiler advertise C99 conformance?
+/* Does the compiler advertise C99 conformance? */
 #if !defined __STDC_VERSION__ || __STDC_VERSION__ < 199901L
 # error "Compiler does not advertise C99 conformance"
 #endif

+// See if C++-style comments work.
+
 #include 
 extern int puts (const char *);
 extern int printf (const char *, ...);
@@ -1260,7 +1262,6 @@ typedef const char *ccp;
 static inline int
 test_restrict (ccp restrict text)
 {
-  // See if C++-style comments work.
   // Iterate through items via the restricted pointer.
   // Also check for declarations in for loops.
   for (unsigned int i = 0; *(text+i) != '\''\0'\''; ++i)
--
2.34.1



Re: time for Autoconf 2.72 (was: On time64 and Large File Support)

2023-02-02 Thread Sam James


> On 2 Feb 2023, at 23:17, Zack Weinberg  wrote:
> 
> Due to a series of crises with my day job, the earliest I can promise to do 
> _anything_ Autoconf related is early March. If you have time to make a 
> release before then, please do not wait for me.
> 

Sorry to hear Zack, hope you're doing ok. I think your input on the issues 
we've been talking about has been enough
for us to each a good position for now.

Paul in particular, please let me know if there's something I can do to help. 
I'm already giving it the standard rounds of usage
in Gentoo. Perhaps we could tag an RC and shove it into the platform-testers 
list? It's non-commital so while I'd like
to move forward before March for the final release, if in the event you didn't 
feel comfortable doing that,
we'd at least have made some progress.

Best,
sa


signature.asc
Description: Message signed with OpenPGP