Re: new snapshot available: grep-3.9.4-c83f

On Tue, Mar 21, 2023 at 1:50 PM Bruno Haible wrote: > Jim Meyering wrote: > > this snapshot really was built with > > the very latest autoconf from master. Compare with grep-3.9, which > > was bootstrapped using a version of autoconf from October. > > ... >

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

On Fri, Mar 17, 2023 at 7:52 PM Paul Eggert wrote: > On 3/17/23 19:08, Jim Meyering wrote: > > Can someone see if there's some small/safe set of changes that are > > essential? > > If none (or few/easy), I might have time to make a snapshot soon. > > As far as I k

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

On Fri, Mar 17, 2023 at 6:00 PM Paul Eggert wrote: > On 3/17/23 16:47, Sam James wrote: > > Clang 16 was released today. Unfortunately, all released versions of > > autoconf still generate configure scripts which are incompatible with it. > > Presumably "./configure CC='clang -std=gnu17" is a work

Re: [PATCH 0/3] RFC: automated bootstrap script

On Fri, Feb 5, 2021 at 7:42 AM Zack Weinberg wrote: > The procedure for building Autoconf from a git checkout is a little > awkward, involving building it once, then using the just-built > autoconf to regenerate the configure script in the source directory, > then throwing away the entire first bu

Re: [PATCH] doc: detail inconsistencies in sed word boundary handling

On Sun, Oct 30, 2016 at 12:01 PM, Pádraig Brady wrote: > * doc/autoconf.texi (Limitations of usual tools): Display a > table showing where the various syntaxes for word boundaries > are supported. ... > +Portable scripts should be aware of the inconsistencies and > +options for handling word bound

Re: [PATCH] AC_PROG_CC_C11: new macro, which AC_PROG_CC_STDC now defaults to

Paul Eggert wrote: ... > Yes, on further thought I'm inclined to agree. Also, it's a lot > simpler. Also, it fixes Jim's bug. There's a lot to like. > Please see the patch below, which I've pushed. Further > comments welcome. > >>From f7fe375b26f39d0a6624ad9a6c532d9361a3226b Mon Sep 17 00:00:00

Re: [PATCH] AC_PROG_CC_C11: new macro, which AC_PROG_CC_STDC now defaults to

Paul Eggert wrote: > I pushed this. I did only C11, not C++11, since I'm not a > C++ guru. > > * NEWS: > * doc/autoconf.texi (C Compiler): Document this. > (Gnulib, Function Portability, Particular Functions) > (Header Portability, Particular Headers, Defining Symbols) > (Printing Messages, Limita

Re: [PATCH] scripts: quote `like this', not 'like this'

Stefano Lattarini wrote: > As per updated GCS recommendations. > > * bin/autoconf.as, bin/autoreconf.in, bin/autoscan.in, ifnames.in, > bin/autoupdate.in: Throughout these files. > * bin/autoheader.in, bin/autom4te.in: Likewise. Also, remove some > useless escaping of the "'" single-quote characte

Re: [PATCH] maint: avoid new syntax-check failure

Eric Blake wrote: > On 07/22/2012 02:51 PM, Jim Meyering wrote: >> I suggest to update maint.mk soon to the latest from gnulib, >> mainly for its new check for the CVE-2012-3386 (make distcheck) bug. >> Once you do that, you see a new "make syntax-check" failure, &g

[PATCH] maint: avoid new syntax-check failure

ined HAVE_DECL_MALLOC && !HAVE_DECL_MALLOC void *malloc (size_t *s); #endif @end example Here's a fix for that that should be pushed first. This probably counts as trivial, but I'll wait for an ACK. >From 32d938eaa7e1cb756997a665cb1669ef6dca3110 Mon Sep 17 00:00:00 2001 From:

Re: [PATCH] tests: use configure.ac, not configure.in, with aclocal/automake involved

Stefano Lattarini wrote: > On 07/21/2012 05:51 PM, Jim Meyering wrote: >> Stefano Lattarini wrote: >> >>> Do so because future automake and aclocal versions (starting from 1.13) >>> won't support 'configure.in' anymore as the name of the Autoconf i

Re: [PATCH] tests: use configure.ac, not configure.in, with aclocal/automake involved

Stefano Lattarini wrote: > Do so because future automake and aclocal versions (starting from 1.13) > won't support 'configure.in' anymore as the name of the Autoconf input > file. Without this patch, the Autoconf testsuite experience some > spurious failures when run with the development version

[PATCH] maint: fix typos in old ChangeLog files

FYI, >From b29e5e79d5203400c4366c61d998bd9cdf30ef0d Mon Sep 17 00:00:00 2001 From: Jim Meyering Date: Tue, 29 May 2012 12:33:46 +0200 Subject: [PATCH] maint: fix typos in old ChangeLog files Culprits identified and fixed automatically using these commands: git ls-files | misspellings -f - |g

[PATCH] maint: avoid "make syntax-check" failure

I was surprised to find that "make syntax-check" was failing. Here's the trivial fix: (I'll push it later today) >From eaa96cb8bd6dca5317329b6682df91dfda286d06 Mon Sep 17 00:00:00 2001 From: Jim Meyering Date: Wed, 11 Apr 2012 12:05:38 +0200 Subject: [PATCH] maint: a

[PATCH] maint: avoid "make syntax-check" failure

FYI, >From a1a00a9768e6206feb8ca768d2aa66cdf3408c5c Mon Sep 17 00:00:00 2001 From: Jim Meyering Date: Sat, 28 Jan 2012 15:19:38 +0100 Subject: [PATCH] maint: avoid "make syntax-check" failure * Makefile.am ($(srcdir)/INSTALL): Remove spurious space-before-TAB. --- Makefile.am

Re: [PATCH] INSTALL: convert to '' quoting, drop blank line at end

Eric Blake wrote: > This is allowed by recent GNU Coding Standards changes, and > mirrors recent gnulib changes: > https://lists.gnu.org/archive/html/bug-gnulib/2012-01/msg00267.html > https://lists.gnu.org/archive/html/bug-gnulib/2012-01/msg00298.html > > I've confirmed that after these changes, t

Re: [PATCH 4/7] maint: placate syntax-check rules: exempt some false positives

Eric Blake wrote: ... >> Subject: [PATCH] maint: convert .x-sc_* into exclude_file_name_regexp--sc_* >> exemptions >> >> Many of the .x-sc_* exemptions were no long necessary. Remove those >> files and instead, provide exemptions via variable definitions in >> cfg.mk to address the few remaining

Re: [PATCH 4/7] maint: placate syntax-check rules: exempt some false positives

Jim Meyering wrote: > Eric Blake wrote: ... >> Incomplete. I'd rather see this patch nuke all of the .x-sc files and >> convert them into exclude_file_name_regexp entries. > > That will be an improvement, but it does not belong in this series. > This series is addr

Re: [PATCH 7/7] maint: fix or disable failing syntax-check rules

Eric Blake wrote: > On 01/21/2012 04:14 AM, Jim Meyering wrote: >> From: Jim Meyering >> >> * cfg.mk (local-checks-to-skip): List failing tests, so we skip >> them, for now. >> (old_NEWS_hash): Update. >> (exclude_file_name_regexp--sc_file_system): Exemp

Re: [PATCH 4/7] maint: placate syntax-check rules: exempt some false positives

Eric Blake wrote: > On 01/21/2012 04:14 AM, Jim Meyering wrote: >> From: Jim Meyering >> > > No ChangeLog entry? Added, now. * cfg.mk: Exempt maint.mk from the "undesirable word seq" check. Exempt maint.mk and autoconf.texi from the test_minus_ao c

Re: [PATCH 5/7] maint.mk: update from gnulib

Eric Blake wrote: > On 01/21/2012 04:14 AM, Jim Meyering wrote: >> From: Jim Meyering >> > > No ChangeLog? Thanks. That was an oversight. Added. >> --- >> maint.mk | 1526 >> +++--- >> 1 fil

Re: [PATCH 2/7] maint: remove empty lines at EOF

Eric Blake wrote: > On 01/21/2012 04:14 AM, Jim Meyering wrote: >> From: Jim Meyering >> >> * man/autoconf.x: Remove empty line at EOF. >> * man/autoheader.x: Likewise. >> * man/autoscan.x: Likewise. >> * man/autoupdate.x: Likewise. >> * man/ifnames

[PATCH 4/7] maint: placate syntax-check rules: exempt some false positives

From: Jim Meyering --- cfg.mk |4 1 files changed, 4 insertions(+), 0 deletions(-) diff --git a/cfg.mk b/cfg.mk index a66c247..5c2e5e5 100644 --- a/cfg.mk +++ b/cfg.mk @@ -116,3 +116,7 @@ update-copyright-env = \ # Prevent incorrect NEWS edits. old_NEWS_hash

[PATCH 2/7] maint: remove empty lines at EOF

From: Jim Meyering * man/autoconf.x: Remove empty line at EOF. * man/autoheader.x: Likewise. * man/autoscan.x: Likewise. * man/autoupdate.x: Likewise. * man/ifnames.x: Likewise. * tests/compile.at: Likewise. * doc/fdl.texi: Likewise. --- doc/fdl.texi |1 - man/autoconf.x |1 - man

[PATCH 6/7] maint: also sync maint.mk and useless-if-before-free from gnulib

From: Jim Meyering * cfg.mk (gnulib-update): Add them to the list. * maint.mk: Update from gnulib. * build-aux/gitlog-to-changelog: Likewise. * build-aux/useless-if-before-free: New file, from gnulib. --- build-aux/gitlog-to-changelog| 24 +++-- build-aux/useless-if-before-free | 207

update maint.mk; fix syntax-check failures

I noticed that autoconf's maint.mk was out of date wrt gnulib's, so updated it. Also, even before the update, "make syntax-check" was failing numerous tests. With the update, even more (added tests) rules were failing. With this series, I've addressed some of the issues and arranged to skip the

[PATCH 3/7] maint: tweak to avoid triggering space-tab-prohibiting syntax-check

From: Jim Meyering * tests/m4sh.at (nargs): Use TAB-SP, not SP-TAB in abusive file name, to avoid triggering the space-tab-prohibiting syntax-check. --- tests/m4sh.at |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/tests/m4sh.at b/tests/m4sh.at index 01b0e72..e9da403

[PATCH 1/7] doc: fix grammar/doubled-word errors

From: Jim Meyering * doc/autoconf.texi: Remove/fix doubled-word errors. Also, s/can not/cannot/. * lib/m4sugar/m4sh.m4: Reword "if IF" comment to avoid triggering the doubled-word warning. --- doc/autoconf.texi |8 lib/m4sugar/m4sh.m4 |2 +- 2 files changed, 5

[PATCH 7/7] maint: fix or disable failing syntax-check rules

From: Jim Meyering * cfg.mk (local-checks-to-skip): List failing tests, so we skip them, for now. (old_NEWS_hash): Update. (exclude_file_name_regexp--sc_file_system): Exempt doc/autoconf.texi for it's uses of "Filesystem Hierarchy Standard". --- cfg.mk | 16 ++--

Re: [PATCH 2/2] maint: sync files from gnulib

Stefano Lattarini wrote: > * GNUmakefile: Sync from gnulib. > * build-aux/announce-gen: Likewise. > * build-aux/config.guess: Likewise. > * build-aux/config.sub: Likewise. > * build-aux/git-version-gen: Likewise. > * build-aux/gnupload: Likewise. > * build-aux/move-if-change: Likewise. > * build-au

Re: [PATCH 1/2] maint: make position of gnulib checkout configurable

Stefano Lattarini wrote: > Some gnulib-related tools (most prominently, the gnulib-provided > 'bootstrap' script) allow the user to define the position of his > gnulib's repository checkout through the use of the 'GNULIB_SRCDIR' > environment variable. We should do the same, for consistency and >

Re: [PATCH] maint: generate ChangeLog from git log

Stefano Lattarini wrote: > Following the practice set by various other GNU projects, we start > to automatically generate the ChangeLog file from the git commit > messages. This will avoid duplication (as the ChangeLog entries > were always inserted both in the git commit message and in the > vers

[PATCH] tests: avoid spurious failure for each gnu-fortran-using test

Surprised to see all fortran-running tests fail, I investigated... >From 905b85a2060f600dbc21e262262f77c8074f7db1 Mon Sep 17 00:00:00 2001 From: Jim Meyering Date: Tue, 17 Jan 2012 12:22:59 +0100 Subject: [PATCH] tests: avoid spurious failure for each gnu-fortran-using test The tests comp

[PATCH] maint: remove ChangeLog from version control; now we generate it

df5ffcaf59b9 Mon Sep 17 00:00:00 2001 From: Jim Meyering Date: Tue, 17 Jan 2012 11:18:08 +0100 Subject: [PATCH] maint: remove ChangeLog from version control; now we generate it Instead, generate it from git commit logs and insert it into each distribution tarball. * Makefile.am (EXTRA_DIST)

Re: [PATCH] avoid new warning about undefined $ARGV[0]

Stefano Lattarini wrote: > On 01/15/2012 05:58 PM, Jim Meyering wrote: >> >> [SNIP] >> >> Stefano Lattarini wrote: >> >>> Yes, awaiting review. For projects where I only contribute >>> minimally, I want to >>> wait for an explicit A

Re: [PATCH] avoid new warning about undefined $ARGV[0]

Stefano Lattarini wrote: > On 01/15/2012 05:33 PM, Jim Meyering wrote: >> Stefano Lattarini wrote: >> >>> Hi Jim. >>> >>> On 01/15/2012 05:22 PM, Jim Meyering wrote: >>>> Without this change, numerous tests would fail. >>>> E.g.,

Re: [PATCH] getopt: fix diagnostic for missing mandatory option argument

Stefano Lattarini wrote: > On 01/15/2012 09:35 AM, Stefano Lattarini wrote: >> On 01/15/2012 09:18 AM, Stefano Lattarini wrote: >>> On 01/15/2012 06:59 AM, Paul Eggert wrote: Thanks, that patch looks good to me; please install. >>> Done. >>> >> And introduced a new bug in doing so, sigh.

Re: [PATCH] avoid new warning about undefined $ARGV[0]

Stefano Lattarini wrote: > Hi Jim. > > On 01/15/2012 05:22 PM, Jim Meyering wrote: >> Without this change, numerous tests would fail. >> E.g., on a Fedora 16 system, running autoreconf would print this warning: >> >> Use of uninitialized value $ARGV[0] in pat

[PATCH] avoid new warning about undefined $ARGV[0]

Mon Sep 17 00:00:00 2001 From: Jim Meyering Date: Sun, 15 Jan 2012 17:16:52 +0100 Subject: [PATCH] avoid new warning about undefined $ARGV[0] * lib/Autom4te/General.pm (getopt): Avoid warning induced by yesterday's change: $ARGV[0] may not be defined, e.g., when invoked via autoreconf. --- C

[PATCH] docs: improve the prose describing _AC_CHECK_TYPE_NEW_BODY

FYI, While looking at a config.log file, I noticed a diagnostic that was due to the code below, and found it suspicious enough that I went to read the macro definition. >From 7a615729c9c56a3608ec0224a67f21d23ea6b3ad Mon Sep 17 00:00:00 2001 From: Jim Meyering Date: Sun, 24 Jul 2011 15:50

[PATCH] README-hacking: fix typo

Here's a tiny fix: >From 5941d6d14017f0bcf638b6d61dbb9374f81c3e6f Mon Sep 17 00:00:00 2001 From: Jim Meyering Date: Sat, 26 Mar 2011 21:50:43 +0100 Subject: [PATCH] README-hacking: fix typo * README-hacking: s/just build/just built/. --- ChangeLog |5 + README-hacking |

Re: [PATCH] tests: don't silently skip the sort-version tests

Eric Blake wrote: > According to Jim Meyering on 1/13/2010 2:26 AM: >> The behavior of bash via /bin/sh (same for zsh and dash, though without >> the warning) is probably POSIX-conforming, but this example illustrates >> why it would be better to emulate openBSD's /bin/s

[PATCH] AC_INIT: Use correct value for PACKAGE_TARNAME

[Exit 2] That's using m4-1.4.12. Here's the direct culprit. Note the stray hyphens: $ grep PACKAGE_TARNAME configure PACKAGE_TARNAME='-autoconf-' ... But how did that get there? Surprised there's no test that notices the failure? I was. I haven't dug into the

Re: [PATCH 2/5] New FAQ node: Debugging.

Ralf Wildenhues wrote: ... > +...@node Debugging > +...@section Debugging @command{configure} scripts Nice tips! I've proposed an addition to one of your lists and made a few very subjective style suggestions: > +While in general, @command{configure} scripts generated by Autoconf > +strive to be

Re: three tiny doc-only patches

Eric Blake wrote: > According to Jim Meyering on 6/6/2009 10:47 AM: >> >> Thanks for the quick feedback. >> How about this: >> >> -directories relatively to the top level of this distribution. E.g., >> +directories relative to the top level of this dist

Re: three tiny doc-only patches

Eric Blake wrote: > According to Jim Meyering on 6/6/2009 9:49 AM: >> I found an old branch with these on it. >> Any objection or suggestion? >> >> >>$ $[0] AUTOTEST_PATH=bin >> >> -possibly amounts into >> +is equivalent to this, when run fro

three tiny doc-only patches

I found an old branch with these on it. Any objection or suggestion? >From a84e707c3d1acb712f6fc84e57dbd0e0cb8a8c82 Mon Sep 17 00:00:00 2001 From: Jim Meyering Date: Wed, 10 Dec 2008 09:57:30 +0100 Subject: [PATCH 1/3] * lib/autotest/general.m4: Correct the example in ./testsuite --h

[PATCH] Fix syntax errors in autoconf.texi.

a Mon Sep 17 00:00:00 2001 From: Jim Meyering Date: Thu, 28 May 2009 19:08:20 +0200 Subject: [PATCH] Fix syntax errors in autoconf.texi. * doc/autoconf.texi (Erlang Libraries): @-escape curly braces in example code. --- ChangeLog |6 ++ doc/autoconf.texi | 10 +- 2

Re: test fails when no C++ compiler is available

Ralf Wildenhues wrote: > [ dropping bug-automake, adding autoconf-patches ] > > Hi Jim, Eric, > > * Jim Meyering wrote on Tue, May 12, 2009 at 11:30:40AM CEST: >> > I've just built automake-from-git on a newly-installed system >> > that lacked a C++ comp

[PATCH] * lib/m4sugar/m4sh.m4: fix grammar: s/are/is/ => "there is no indirection"

Barely worth mentioning... I'll wait a couple of hours before pushing. (and I will add the ChangeLog entry) >From e329d5af15adb18b3143f75654fe9f73f411e9e0 Mon Sep 17 00:00:00 2001 From: Jim Meyering Date: Mon, 18 Aug 2008 11:08:14 +0200 Subject: [PATCH] * lib/m4sugar/m4sh.m4: fix gramma

AC_HEADER_ASSERT: don't say assertions are disabled when they're not

clearer that it's a two-test use of AS_IF. If no one objects, I'll push in a few hours: [gnulib's gl_ASSERT will get a similar change, included below] >From 27d44bf831cdf696049e2d6a96173d8ea0fa40eb Mon Sep 17 00:00:00 2001 From: Jim Meyering <[EMAIL PROTECTED]> Date:

Re: getgroups: test: =: unary operator expected

Eric Blake <[EMAIL PROTECTED]> wrote: > According to Jim Meyering on 10/22/2008 9:32 AM: >> To autoconf folks, I've attached the obvious patch below, >> and will push it some time tomorrow if no one objects. >> >> * lib/autoconf/functions.m4 (AC_FUNC_GETGROUPS

Re: getgroups: test: =: unary operator expected

Eric Blake <[EMAIL PROTECTED]> wrote: > Jim Meyering meyering.net> writes: >> To autoconf folks, I've attached the obvious patch below, >> and will push it some time tomorrow if no one objects. >> >> From: Jim Meyering redhat.com> >> Date:

Re: getgroups: test: =: unary operator expected

ler warning > diff --git a/m4/getgroups.m4 b/m4/getgroups.m4 > index edc2bde..0364752 100644 > --- a/m4/getgroups.m4 > +++ b/m4/getgroups.m4 > @@ -1,9 +1,9 @@ > -#serial 10 > +#serial 11 > > dnl From Jim Meyering. > dnl A wrapper around AC_FUNC_GETGROUPS. &

Re: interrupt causes parse error in configure script

Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > * Jim Meyering wrote on Mon, Aug 18, 2008 at 11:57:45PM CEST: >> Ralf Wildenhues <[EMAIL PROTECTED]> wrote: >> >> I think we can factor it into a simpler testcase. I just tried this: >> >> >> >>

Re: interrupt causes parse error in configure script

Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > Hello again, > > first, sorry for being a bit blunt earlier. No apology needed ;-) ... >> It appears that what Jim is seeing is that the shell (which one?) >> catches the Ctrl-C, aborts the subshell, but then proceeds with >> execution of the builtin t

Re: interrupt causes parse error in configure script

Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > * Jim Meyering wrote on Mon, Aug 18, 2008 at 03:59:18PM CEST: >> Ralf Wildenhues <[EMAIL PROTECTED]> wrote: >> >> > Maybe all you want to prevent is errors from inside the trap code? >> >> No, I want t

Re: interrupt causes parse error in configure script

Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > * Jim Meyering wrote on Mon, Aug 18, 2008 at 12:12:29PM CEST: >> Ralf Wildenhues <[EMAIL PROTECTED]> wrote: >> > >> > Doesn't this patch hide potential typos otherwise exposed by the `test' >>

Re: interrupt causes parse error in configure script

Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > Hi Jim, > > * Jim Meyering wrote on Mon, Aug 18, 2008 at 11:23:01AM CEST: >> I admit that this not a big deal, but even when I interrupt a configure >> script, I prefer to see it die cleanly. Otherwise, I have to wonder &g

interrupt causes parse error in configure script

an-up trap code also fails to run. Comments, suggestions ? >From a1c0ac7453b663d6886c96970dbf3161f0046c0c Mon Sep 17 00:00:00 2001 From: Jim Meyering <[EMAIL PROTECTED]> Date: Sun, 15 Jun 2008 17:56:37 +0200 Subject: [PATCH] AC_VAR_YES: new function, to handle an unusual failure Pr

Re: carriage return line endings vs. literal ^M in status.m4

Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > * Jim Meyering wrote on Sat, Apr 05, 2008 at 03:26:28PM CEST: >> Ralf Wildenhues <[EMAIL PROTECTED]> wrote: >> > * Jim Meyering wrote on Sat, Apr 05, 2008 at 03:08:24PM CEST: >> >> >> >

Re: carriage return line endings vs. literal ^M in status.m4

Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > * Jim Meyering wrote on Sat, Apr 05, 2008 at 03:08:24PM CEST: >> Ralf Wildenhues <[EMAIL PROTECTED]> wrote: >> >> >> >> I prefer yours and almost went that way myself, but wonder if it's >> >

Re: carriage return line endings vs. literal ^M in status.m4

Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > * Jim Meyering wrote on Sat, Apr 05, 2008 at 02:54:37PM CEST: >> Ralf Wildenhues <[EMAIL PROTECTED]> wrote: >> > >> > How about this slightly simpler patch instead? If you don't like it, >> > then I

Re: carriage return line endings vs. literal ^M in status.m4

Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > * Jim Meyering wrote on Sat, Apr 05, 2008 at 02:26:40PM CEST: >> >> Complete patch below. >> I'll point Elbert at a coreutils snapshot to test this. > > How about this slightly simpler patch instead? If you don&#

Re: carriage return line endings vs. literal ^M in status.m4

Eric Blake <[EMAIL PROTECTED]> wrote: ... > | +dnl See if CR is the EOL marker. If not, remove any EOL-related > | +dnl ^M bytes and escape any remaining ones. If so, just use mv. > > If CR is _not_ the EOL marker, then how would CR appear at the end of the > line? Where are we doing input into

Re: carriage return line endings vs. literal ^M in status.m4

Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > * Jim Meyering wrote on Sat, Apr 05, 2008 at 01:14:30PM CEST: >> >> Just got a clarification (stale Subject was misleading). >> This is for OS/2 (www.ecomstation.com Ecs v2 rc4), not Maemo/OS2008. > > Thanks. > >

Re: carriage return line endings vs. literal ^M in status.m4

Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > Hello Jim, > > * Jim Meyering wrote on Sat, Apr 05, 2008 at 11:48:49AM CEST: >> >> I've been working through some odd problems related to a user's >> attempt to build recent coreutils snapshots on a Maemo/OS20

carriage return line endings vs. literal ^M in status.m4

\\\' ' '` # Remove any trailing space. no_install_progs_default=`echo "$t"|sed 's/ $//'` -- 1.5.5.rc3.1.gaece Here's the proposed autoconf patch: >From 98629eebc4cd905af0484ca8275390f94f3a0da3 Mon Sep 17 00:00:00 2001 From: Jim Meyering <[EMAIL PROTECT

[PATCH] Fix texinfo syntax error.

FYI: Fix texinfo syntax error. * doc/autoconf.texi (Limitations of Usual Tools): s/@kbd {/@kbd{/ diff --git a/doc/autoconf.texi b/doc/autoconf.texi index 991a714..5ebf0be 100644 --- a/doc/autoconf.texi +++ b/doc/autoconf.texi @@ -15398,9 +15398,9 @@ an empty regular expression; th

Re: [PATCH] Generalize GNUmakefile, ...

Eric Blake <[EMAIL PROTECTED]> wrote: > According to Jim Meyering on 3/13/2008 4:44 PM: > | If consensus is for maint.mk, I'm happy to switch to that, > | assuming it's not too disruptive, otherwise. > | Far better to have only one such file name. > > Here's

Re: [PATCH] Generalize GNUmakefile, ...

Eric Blake <[EMAIL PROTECTED]> wrote: > [adding gnulib] > > According to Jim Meyering on 3/12/2008 5:39 AM: > | Hi, > > Hi Jim, Simon, others, > > | > | I'm planing to make the following change in coreutils > | so that autoconf can then use the exact same

Re: [PATCH] Generalize GNUmakefile, ...

Eric Blake <[EMAIL PROTECTED]> wrote: > According to Jim Meyering on 3/12/2008 6:20 AM: > | > | Here it is: > | (NB: here I've changed the -include line to specify > | "$(srcdir)/GNUmakefile.cfg", for VPATH builds) > > $(srcdir) isn't defined un

Re: [PATCH] Generalize GNUmakefile, ...

Jim Meyering <[EMAIL PROTECTED]> wrote: > I'm planing to make the following change in coreutils > so that autoconf can then use the exact same GNUmakefile. > > The only difference for autoconf would be that it would > also require a new file, GNUmakef

[PATCH] Generalize GNUmakefile, ...

... ...so that it can be used unmodified by autoconf. * GNUmakefile: Include optional file, GNUmakefile.cfg. Autoconf will use this to override _autoreconf and to export PATH. (_autoreconf): Define. (_dummy): cd to $(srcdir) before removing autom4te.cache. Si

Re: [PATCH] Don't infloop upon "make dist".

Eric Blake <[EMAIL PROTECTED]> wrote: > According to Jim Meyering on 3/2/2008 2:39 PM: > | You should never have to create .tarball-version manually. > | > |> 'make major' when using GNUMakefile (since 'make major' is run before the > |> tag is cre

Re: [PATCH] Don't infloop upon "make dist".

Eric Blake <[EMAIL PROTECTED]> wrote: > According to Jim Meyering on 3/2/2008 9:39 AM: > | I noticed that "make dist" would infloop. > | This change fixes that and syncs the pieces > | from coreutils and gnulib: > | > | Don't infloop upon "m

Re: [PATCH] Don't infloop upon "make dist".

Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > The patch is ok with this change: The _curr-ver computation needs to be ... Thanks again for the review. I've pushed the result to autoconf.git. Your fix is now in coreutils.git, too: http://git.sv.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=b2

Re: [PATCH] Don't infloop upon "make dist".

Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > * Jim Meyering wrote on Sun, Mar 02, 2008 at 10:06:04PM CET: >> Ralf Wildenhues <[EMAIL PROTECTED]> wrote: >> ... >> > The patch is ok with this change: The _curr-ver computation needs to be >> > >>

Re: [PATCH] Don't infloop upon "make dist".

Ralf Wildenhues <[EMAIL PROTECTED]> wrote: ... > The patch is ok with this change: The _curr-ver computation needs to be > > _curr-ver := $(shell cd $(srcdir) && ./build-aux/git-version-gen \ >.tarball-version) > > because otherwise it won't work with a VPATH build. Good c

Re: [PATCH] Don't infloop upon "make dist".

Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > * Jim Meyering wrote on Sun, Mar 02, 2008 at 05:39:07PM CET: >> I noticed that "make dist" would infloop. >> This change fixes that and syncs the pieces >> from coreutils and gnulib: >> >> Don&

[PATCH] Don't infloop upon "make dist".

all, not .version. * configure.ac (AC_INIT): Use .tarball-version, not .version. * build-aux/git-version-gen: Update from gnulib. Ok to commit? Signed-off-by: Jim Meyering <[EMAIL PROTECTED]> --- ChangeLog |8 GNUmakefile | 17

Re: update fetch

Eric Blake <[EMAIL PROTECTED]> wrote: > [and adding coreutils] > > According to Ralf Wildenhues on 1/22/2008 1:59 PM: > | Hello, > | > | I've started to convert the release rules to git. I'm pretty sure they > | don't work right yet (with Automake I ended up typing them manually), > | but this pat

Re: [SCM] GNU Autoconf source repository branch, master, updated. v2.61a-341-g4380a86

Benoit Sigoure <[EMAIL PROTECTED]> wrote: > Off topic: How did you hack the script git/contrib/hooks/post-receive- > email so that it uses the email of the person who pushed in the From > field? Hi Benoit, Here is the definition of the variable used to expand "From: $committer": (from an earlier

Re: AC_PROG_INSTALL: require installation of multiple files.

Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > the `make install' rules generated by Automake can benefit greatly from > being able to install multiple files at once. The GNU Coding Standards > have been changed to allow this, but Autoconf's AC_PROG_INSTALL needs to > detect this, too: otherwise, it

Re: Automake wants your INSTALL file

Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > Autoconf git does not store the INSTALL file in git any more. This > breaks Automake's fetch rule. > > Can somebody suggest something nicer than manual copying out of a > checked-out tree? Alternatively, may I put INSTALL back in git? > > FWIW, this is

Re: [PATCH 0/10] Whitespace robustness patch series

Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > Done and pushed now. Thanks again!

Re: [PATCH 0/10] Whitespace robustness patch series

Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > Anyway, I'd appreciate review, and of course also comments along the > lines of "may review in 2 weeks, please don't apply yet" or whatever > else you think. Hi Ralf, Thanks for doing this! I've looked through about 1/3 of the changes, and so far it lo

Re: [PATCH 10/10] * tests/torture.at (srcdir): Fix quoting.

Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > This test actually calls configure with an absolute path, > so in a tree with whitespace we need to quote (just like > most of the code under autoconf/lib does, too). > > diff --git a/tests/torture.at b/tests/torture.at > index 11c619d..0f6d0ef 100644 >

WORDS_BIGENDIAN not defined on sparc Solaris 10!

This is a nasty bug. I noticed failures of coreutils' md5 and sha*-related tests on sparc/Solaris systems. It came down to the fact that config.hin does the following (in config.h this bit is identical on the system in question): /* Define WORDS_BIGENDIAN to 1 if your processor stores words with

Re: [PATCH] Indentation fixups.

Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > * lib/autotest/general.m4 (AT_INIT) : Fix > indentation. > (_AT_CHECK): Use less indentation, to save space. > --- > > Hello, > > This patch is one of the "do you mind if I do this?" kind. > It shaves 30kB off of autoconf's testsuite, and, IMVHO, > does

Re: Diagnose write errors in config.status

Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > Plowing my way through Bruno's bug reports and suggestions from: > . > Let's make write errors fail config.status. > > First off, writing a test that exercises all possible code paths

[PATCH] Clean up the rule to create "expr".

This fixes another redirect-directly-to-target nit: diff --git a/ChangeLog b/ChangeLog index 79c6cc1..86cccd2 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,10 @@ +2007-11-13 Jim Meyering <[EMAIL PROTECTED]> + + Clean up the rule to create "expr". + * tests/M

accurate dependencies

|9 + GNUmakefile |3 --- lib/m4sugar/Makefile.am |5 +++-- 3 files changed, 12 insertions(+), 5 deletions(-) diff --git a/ChangeLog b/ChangeLog index 1426278..cc23b5a 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,12 @@ +2007-11-13 Jim Meyering <[EMAIL PROTECTED]&g

Re: Accommodate non-srcdir build-from-checkout.

Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > Hello Jim, > > * Jim Meyering wrote on Sun, Nov 11, 2007 at 08:10:53PM CET: >> This is for you, Ralf :-) >> I'll push tomorrow. Hi Ralf, I've pushed those four from yesterday, plus one more:

Re: Generate package.m4 in build-dir, not srcdir.

Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > That looks about right, thanks. Hi Ralf, > FWIW, an explicit `make clean' does look to me like papering over things > more than anything else. It simply means dependencies are not true, no? > ;-) Touché :-) Yes. However, from the beginning, I always

Re: Remove the autoreconf-provided INSTALL, so that we regenerate it.

Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > * Jim Meyering wrote on Sun, Nov 11, 2007 at 09:16:46PM CET: >> >> Remove the autoreconf-provided INSTALL, so that we regenerate it. >> * GNUmakefile (dummy): Remove INSTALL. > > Thanks. > >&

Re: Accommodate non-srcdir build-from-checkout.

Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > * Jim Meyering wrote on Sun, Nov 11, 2007 at 08:10:53PM CET: >> This is for you, Ralf :-) >> I'll push tomorrow. > > Thanks. But GNUmakefile still isn't seen from a `make' in the build > tree, so I still n

Remove the autoreconf-provided INSTALL, so that we regenerate it.

Jim Meyering <[EMAIL PROTECTED]> wrote: > Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > > Hi Ralf, > >> * Jim Meyering wrote on Sat, Nov 10, 2007 at 10:28:42PM CET: >>> I was surprised to see diffs after running make with one of >>> the clean targe

Remove racy commands to build scripts in bin/ and tests/.

|6 ++ man/Makefile.am | 13 ++--- 2 files changed, 8 insertions(+), 11 deletions(-) diff --git a/ChangeLog b/ChangeLog index b5c04b7..c0d6b7c 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,5 +1,11 @@ 2007-11-11 Jim Meyering <[EMAIL PROTECTED]> + Remove racy commands to

Accommodate non-srcdir build-from-checkout.

-- configure.ac |2 +- 4 files changed, 18 insertions(+), 10 deletions(-) diff --git a/ChangeLog b/ChangeLog index f9aacad..b5c04b7 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,5 +1,12 @@ 2007-11-11 Jim Meyering <[EMAIL PROTECTED]> + Accommodate non-srcdir build-from-checkou

  1   2   >