Re: AC_TYPE_LONG_LONG_INT busted in current Autoconf

3a813b3b2f9f3a8ec0df95e444b6fb54267775a9 Mon Sep 17 00:00:00 2001 From: Paul Eggert Date: Tue, 16 Jan 2024 21:19:31 -0800 Subject: [PATCH] Fix typo in previous patch --- lib/autoconf/types.m4 | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/lib/autoconf/types.m4 b/lib/autoconf

Re: cannot make gcc report undeclared builtins

On 1/31/24 03:23, Simon Josefsson via Bug reports for autoconf wrote: https://buildd.debian.org/status/fetch.php?pkg=libidn2&arch=loong64&ver=2.3.7-1&stamp=1706360630&raw=0 Here's the crucial part of that log: configure:15961: checking for size_t configure:15961: gcc -c -g -O2 -ffile-prefix

Re: `cp -l` doesn't work correctly on some macOS versions

On 2/2/24 12:20, Russ Allbery wrote: I thought ln || ln -s was the standard recipe here Yes, "cp -l" isn't required by POSIX and is not portable in general. For example, on AIX 7.1: $ cp -l a b cp: Not a recognized flag: l Usage: cp [-fhipHILPU][-d|-e] [-r|-R] [-E{force|ignore|warn

Re: `cp -l` doesn't work correctly on some macOS versions

ble, as there are so many (and they proliferate), the manual could be better about what *is* portable and I installed the attached. From 163dade069be64df7cce5c6d48fdcb56188a6f60 Mon Sep 17 00:00:00 2001 From: Paul Eggert Date: Sat, 3 Feb 2024 21:37:49 -0800 Subject: [PATCH] =?UTF-8?q?Document=2

[sr #111044] autoconf should assert existence of all subsidiary tools at startup

Follow-up Comment #3, sr #111044 (group autoconf): [comment #2 comment #2:] > neither `diff` nor `awk` (and arguably not even `sed`) should be an implicit dependency. Not sure I'd go that far. The [https://www.gnu.org/prep/standards/html_node/Utilities-in-Makefiles.html GNU Coding Standards for u

Re: Suggestion for improving an error message

undefined or overquoted macro". Since the diagnostic can be caused by misspelled macro names, which do occur, I thought it wise to retain a mention of that in the diagnostic. I installed the attached patch.From 7a6347d1d785ee26f205154fdadf7f6f81797f92 Mon Sep 17 00:00:00 2001 From: Paul Eggert D

Re: autoreconf --force seemingly does not forcibly update everything

On 4/10/24 13:36, Simon Josefsson via Gnulib discussion list wrote: Is bootstrap intended to be reliable from within a tarball? I thought the bootstrap script was not included in tarballs because it wasn't designed to be ran that way, and the way it is designed may not give expected results. I

[sr #110983] AC_SYS_LARGEFILE doesn't honor AC_LANG setting

Update of sr #110983 (group autoconf): Status: Confirmed => Done ___ Follow-up Comment #6: I installed [https://git.savannah.gnu.org/cgit/autoconf.git/commit/?id=b71143738516017f0e0d347a40

Re: ac_cv_sys_largefile_opts undocumented?

On 2024-04-27 14:06, dmitrii.pasech...@cs.ox.ac.uk wrote: Thus I got questions whether a patch for a build system I submitted for a project is OK, as it uses an undocumented variable (thus, perhaps, unstable). Although it's poorly designed and not documented and not stable, the patch may be go

Re: ac_cv_sys_largefile_opts undocumented?

On 2024-04-27 15:39, dmitrii.pasech...@cs.ox.ac.uk wrote: It's for nauty, a well-known program to deal with graph isomorphisms etc. I've made a Gentoo patch herehttps://bugs.gentoo.org/921138 and I wanted to upstream it. Oh my, that is indeed in an undocumented/hacky part of autoconf, one that

[sr #111054] Typo in texi file breaks build

Update of sr #111054 (group autoconf): Status:None => Done Open/Closed:Open => Closed ___ Follow-up Comment #1: Thanks for reporting

Re: Improve Autoconf MSVC support

Thanks for your helpful comments. Would you be up to writing and testing Autoconf patches to support MSVC better? I don't use MSVC and so would not be good for that. Thanks.

[sr #111072] "[[]] attributes are a C23 extension warning" with clang

Update of sr #111072 (group autoconf): Status:None => Invalid Open/Closed:Open => Closed ___ Follow-up Comment #1: The problems you men

Re: make AC_PROG_OBJC work out-of-the-box on RHEL 9 and compatible systems

Thanks, I installed that.

[sr #111102] ksh93 oddity w.r.t. ${1+"$@"} on AIX (for section "Portable Shell"?)

Update of sr #02 (group autoconf): Status:None => Done Open/Closed:Open => Closed ___ Follow-up Comment #1: Thanks for reporting

[sr #111102] ksh93 oddity w.r.t. ${1+"$@"} on AIX (for section "Portable Shell"?)

Follow-up Comment #3, sr #02 (group autoconf): Thanks, I fixed the doc typos you flagged. I didn't find more-general flaws, though I was testing AIX 7.1 (also ksh93 Version M 93t+ 2009-05-01). ___ Reply to this item at:

[sr #111111] AC_SYS_LARGEFILE system wide control and autoconf releases

Follow-up Comment #1, sr #11 (group autoconf): The cache variables for AC_SYS_LARGEFILE aren't documented, so they aren't part of the stable API. In Autoconf 2.71 they were ac_cv_sys_largefile_CC, ac_cv_sys_file_offset_bits, ac_cv_sys_large_files. In bleeding-edge Autoconf things are simpler:

[sr #111111] AC_SYS_LARGEFILE system wide control and autoconf releases

Follow-up Comment #3, sr #11 (group autoconf): [comment #2:] > ac_cv_sys_largefile_opts='none needed' > ac_cv_sys_file_offset_bits=no That should work. I'd go with that rather than anything more complicated. Still not sure it's worth documenting, but there are no plans to change it. ___

<    1   2   3   4   5   6