Re: update fetch

2008-02-08 Thread Jim Meyering
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

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

2008-03-02 Thread Jim Meyering
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: [PATCH] Don't infloop upon "make dist".

2008-03-02 Thread Jim Meyering
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&

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

2008-03-02 Thread Jim Meyering
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".

2008-03-02 Thread Jim Meyering
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".

2008-03-02 Thread Jim Meyering
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".

2008-03-02 Thread Jim Meyering
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".

2008-03-02 Thread Jim Meyering
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

[PATCH] Generalize GNUmakefile, ...

2008-03-12 Thread Jim Meyering
... ...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] Generalize GNUmakefile, ...

2008-03-12 Thread Jim Meyering
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

Re: [PATCH] Generalize GNUmakefile, ...

2008-03-12 Thread Jim Meyering
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, ...

2008-03-13 Thread Jim Meyering
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, ...

2008-03-20 Thread Jim Meyering
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

[PATCH] Fix texinfo syntax error.

2008-03-26 Thread Jim Meyering
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

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

2008-04-05 Thread Jim Meyering
\\\' ' '` # 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

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

2008-04-05 Thread Jim Meyering
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

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

2008-04-05 Thread Jim Meyering
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

2008-04-05 Thread Jim Meyering
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

2008-04-05 Thread Jim Meyering
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

2008-04-05 Thread Jim Meyering
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

2008-04-05 Thread Jim Meyering
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

2008-04-05 Thread Jim Meyering
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: >> >> >> >

interrupt causes parse error in configure script

2008-08-18 Thread Jim Meyering
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: interrupt causes parse error in configure script

2008-08-18 Thread Jim Meyering
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

Re: interrupt causes parse error in configure script

2008-08-18 Thread Jim Meyering
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

2008-08-18 Thread Jim Meyering
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

2008-08-18 Thread Jim Meyering
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

2008-08-19 Thread Jim Meyering
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: getgroups: test: =: unary operator expected

2008-10-22 Thread Jim Meyering
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: getgroups: test: =: unary operator expected

2008-10-23 Thread Jim Meyering
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

2008-10-24 Thread Jim Meyering
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

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

2008-12-10 Thread Jim Meyering
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:

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

2009-03-17 Thread Jim Meyering
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

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

2009-05-14 Thread Jim Meyering
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] Fix syntax errors in autoconf.texi.

2009-05-28 Thread Jim Meyering
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

three tiny doc-only patches

2009-06-06 Thread Jim Meyering
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

Re: three tiny doc-only patches

2009-06-06 Thread Jim Meyering
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

Re: three tiny doc-only patches

2009-06-06 Thread Jim Meyering
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: [PATCH 2/5] New FAQ node: Debugging.

2009-09-13 Thread Jim Meyering
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

[PATCH] AC_INIT: Use correct value for PACKAGE_TARNAME

2009-09-15 Thread Jim Meyering
[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] tests: don't silently skip the sort-version tests

2010-01-13 Thread Jim Meyering
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] README-hacking: fix typo

2011-03-26 Thread Jim Meyering
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 |

[PATCH] docs: improve the prose describing _AC_CHECK_TYPE_NEW_BODY

2011-09-01 Thread Jim Meyering
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] avoid new warning about undefined $ARGV[0]

2012-01-15 Thread Jim Meyering
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

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

2012-01-15 Thread Jim Meyering
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

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

2012-01-15 Thread Jim Meyering
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]

2012-01-15 Thread Jim Meyering
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] avoid new warning about undefined $ARGV[0]

2012-01-15 Thread Jim Meyering
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

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

2012-01-17 Thread Jim Meyering
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)

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

2012-01-17 Thread Jim Meyering
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

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

2012-01-17 Thread Jim Meyering
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

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

2012-01-21 Thread Jim Meyering
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 2/2] maint: sync files from gnulib

2012-01-21 Thread Jim Meyering
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

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

2012-01-21 Thread Jim Meyering
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 ++--

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

2012-01-21 Thread Jim Meyering
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

2012-01-21 Thread Jim Meyering
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 6/7] maint: also sync maint.mk and useless-if-before-free from gnulib

2012-01-21 Thread Jim Meyering
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

2012-01-21 Thread Jim Meyering
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 2/7] maint: remove empty lines at EOF

2012-01-21 Thread Jim Meyering
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 4/7] maint: placate syntax-check rules: exempt some false positives

2012-01-21 Thread Jim Meyering
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

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

2012-01-21 Thread Jim Meyering
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

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

2012-01-21 Thread Jim Meyering
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 4/7] maint: placate syntax-check rules: exempt some false positives

2012-01-21 Thread Jim Meyering
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 7/7] maint: fix or disable failing syntax-check rules

2012-01-21 Thread Jim Meyering
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

2012-01-21 Thread Jim Meyering
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 4/7] maint: placate syntax-check rules: exempt some false positives

2012-01-23 Thread Jim Meyering
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] INSTALL: convert to '' quoting, drop blank line at end

2012-01-23 Thread Jim Meyering
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

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

2012-01-28 Thread Jim Meyering
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

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

2012-04-11 Thread Jim Meyering
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: fix typos in old ChangeLog files

2012-05-29 Thread Jim Meyering
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

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

2012-07-21 Thread Jim Meyering
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

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

2012-07-21 Thread Jim Meyering
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

[PATCH] maint: avoid new syntax-check failure

2012-07-22 Thread Jim Meyering
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] maint: avoid new syntax-check failure

2012-07-23 Thread Jim Meyering
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

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

2012-09-21 Thread Jim Meyering
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] AC_PROG_CC_C11: new macro, which AC_PROG_CC_STDC now defaults to

2012-09-21 Thread Jim Meyering
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] AC_PROG_CC_C11: new macro, which AC_PROG_CC_STDC now defaults to

2012-09-22 Thread Jim Meyering
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] doc: detail inconsistencies in sed word boundary handling

2016-10-31 Thread Jim Meyering
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 0/3] RFC: automated bootstrap script

2021-02-06 Thread Jim Meyering
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: time for Autoconf 2.72 (was: On time64 and Large File Support)

2023-03-17 Thread Jim Meyering
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: time for Autoconf 2.72 (was: On time64 and Large File Support)

2023-03-18 Thread Jim Meyering
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: new snapshot available: grep-3.9.4-c83f

2023-03-21 Thread Jim Meyering
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: `#error' vs string literal

2006-03-15 Thread Jim Meyering
consistently in gnulib (unlike Autoconf). > I remember that `#error' does not provoke failure everywhere, but don't > remember the offending compiler/system. > > But there is even a patch to the contrary in gnulib, from coreutils: > > | 2005-08-27 Jim Meyering <[EMAIL

AC_FUNC_LSTAT_FOLLOWS_SLASHED_SYMLINK was reversed

2006-05-23 Thread Jim Meyering
I've just checked in the following change. It made it so coreutils-5.96 uses the lib/lstat.c wrapper when it shouldn't (e.g., w/linux) and doesn't when it should. 2006-05-23 Jim Meyering <[EMAIL PROTECTED]> * lib/autoconf/functions.m4 (AC_FUNC_LSTAT_FO

Re: AC_FUNC_LSTAT_FOLLOWS_SLASHED_SYMLINK was reversed

2006-05-23 Thread Jim Meyering
I wrote: > I've just checked in the following change. > It made it so coreutils-5.96 uses the lib/lstat.c wrapper > when it shouldn't (e.g., w/linux) and doesn't when it should. > > 2006-05-23 Jim Meyering <[EMAIL PROTECTED]> &

Re: AC_FUNC_LSTAT_FOLLOWS_SLASHED_SYMLINK was reversed

2006-05-23 Thread Jim Meyering
Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > * Jim Meyering wrote on Wed, May 24, 2006 at 12:54:43AM CEST: >> >> How about a new test release, autoconf-2.59e, so >> I can require that rather than providing a replacement >> AC_FUNC_LSTAT_FOLLOWS_SLASHED_SYMLINK

Re: coreutils-6.4 build feedback

2006-10-25 Thread Jim Meyering
Paul Eggert <[EMAIL PROTECTED]> wrote: > Jim Meyering <[EMAIL PROTECTED]> writes: > >> Now we just need to fix the autoconf check >> not to define HAVE_FSEEKO, but that's where I stopped. >> I have a hard time getting motivated for such crufty old sy

FYI: doc grammar nits

2007-03-17 Thread Jim Meyering
I've just fixed these grammar nits: * doc/autoconf.texi: Adjust grammar around use of "heuristics". Index: doc/autoconf.texi === RCS file: /sources/autoconf/autoconf/doc/autoconf.texi,v retrieving revision 1.1135 diff -u -p -

using grep with \> is not portable

2007-03-17 Thread Jim Meyering
One more small doc change, below. FYI, it was prompted by the coreutils buildbot failures last night. Fixed by today's changes to bootstrap: -grep '^[]*AM_GNU_GETTEXT_VERSION\>' configure.ac >/dev/null || \ +grep '^[]*AM_GNU_GETTEXT_VERSION(' configure.ac >/dev/null || \ *

FYI: tiny comment addition

2007-09-22 Thread Jim Meyering
Converting things to git, I found and applied/pushed this old, trivial patch: Add a comment. * lib/autoconf/headers.m4 (HAVE_STDBOOL_H): Document the 2004-05-31 change also with a comment in the code. Signed-off-by: Jim Meyering <[EMAIL PROTECTED]> --- Cha

another old patch: use the vertical bar as sed delimiter

2007-09-22 Thread Jim Meyering
ny shell use that? If no one objects, I'll commit this on Monday. >From 8e07cb1112fe34c58cd1fa8b595c8b39843b79e3 Mon Sep 17 00:00:00 2001 From: Jim Meyering <[EMAIL PROTECTED]> Date: Sat, 22 Sep 2007 14:04:51 +0200 Subject: [PATCH] Whenever possible, use the vertical bar as sed

Re: another old patch: use the vertical bar as sed delimiter

2007-09-23 Thread Jim Meyering
Paul Eggert <[EMAIL PROTECTED]> wrote: > Jim Meyering <[EMAIL PROTECTED]> writes: > >> Is the concern that "|" might be used as a path separator? >> Does any shell use that? > > The concern was that someone might put "|" in a directory name

Re: vc-dwim and git

2007-10-10 Thread Jim Meyering
Eric Blake <[EMAIL PROTECTED]> wrote: > According to Paul Eggert on 10/10/2007 12:46 AM: >> Eric Blake <[EMAIL PROTECTED]> writes: >> >>> Thanks for doing this. But please remember to separate the summary line >>> from the rest of the details in the git commit text. >> >> This is starting to get a

remove generated files

2007-10-27 Thread Jim Meyering
FYI, I've just pushed the following. I've omitted the diffs that merely reflect file removals. diff --git a/ChangeLog b/ChangeLog index b0411e1..f0c4469 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,12 @@ +2007-10-27 Jim Meyering <[EMAIL PROTECTED]> + + Remove all gene

don't fail test #132

2007-10-27 Thread Jim Meyering
ure ... to this: /bin/sh ./configure ... but then it'd be identical to the preceding line, so this patch simply removes the offending test. Jim diff --git a/ChangeLog b/ChangeLog index 2a26dc0..5c7ff83 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,5 +1,9 @@ 2007-10-27 Jim Meyerin

Re: don't fail test #132

2007-10-27 Thread Jim Meyering
Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > Ah, ok, I hadn't thought of that. Then we should put "." early in PATH, > so that this false failure won't happen. Does this patch fix the test > failure for you? Of course :-) > with this setting in ~/.ctags (for exuberant ctags): > > --langdef=m4 >

[PATCH] Make inter-release --version output more useful.

2007-10-27 Thread Jim Meyering
git a/ChangeLog b/ChangeLog index 18c9fe4..608c8f0 100644 --- a/ChangeLog +++ b/ChangeLog @@ -6,6 +6,26 @@ 2007-10-27 Jim Meyering <[EMAIL PROTECTED]> + Make inter-release --version output more useful. + Now, each unofficial build has a version "number" like 2.61a-1

Re: [PATCH] Make inter-release --version output more useful.

2007-10-27 Thread Jim Meyering
Eric Blake <[EMAIL PROTECTED]> wrote: > According to Jim Meyering on 10/27/2007 11:38 AM: >> Now that the generated files are no longer version-controlled, >> this patch is possible. FYI, using the resulting version of autoconf >> to build configure for coreutils, I

Re: remove generated files

2007-10-27 Thread Jim Meyering
Ralf Wildenhues <[EMAIL PROTECTED]> wrote: >> +We've opted to keep only the highest-level sources in the GIT repository. >> +This eases our maintenance burden, (fewer merges etc.), but imposes more >> +requirements on anyone wishing to build from the just-checked-out sources. >> +For example, you h

Re: [PATCH] Make inter-release --version output more useful.

2007-10-27 Thread Jim Meyering
Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > * Jim Meyering wrote on Sat, Oct 27, 2007 at 07:38:23PM CEST: > [...git-version-gen...] >> +COREUTILS-[0-9]*) v=`echo "$v" | sed 's/^COREUTILS-//;s/_/./g'` ;; > > Does that need adjustment for Autocon

  1   2   >