Re: gnulib-tool: new options --add-import, --remove-import

> * NEWS: Mention the change. A NEWS entry is maybe not enough for such a change that will affect many users. I'm adding one more migration aid: 2010-09-04 Bruno Haible gnulib-tool: Help migration from --import to --add-import or --update. * gnulib-tool: Emit a verbose

Re: absolute build directory with spaces

On Saturday 04 September 2010, Jim Meyering wrote: > Stefano Lattarini wrote: > > > > What about instead making the names of the temporaries > > source/build/install directories used by "make distcheck" > > configurable? This will offer more flexibility, and won't > > introduce still another autom

Re: Failing to use gnulib bootstrap in libtool

Eric Blake wrote: > > The contents of gnulib-cache.m4 is an output of the invocation of > > gnulib-tool, > > and therefore a derivative of the parameters that you pass to gnulib-tool. > > But the current documentation says that 'gnulib-cache.m4' is the ONE > output that you SHOULD be keeping in

Re: absolute build directory with spaces

Stefano Lattarini wrote: > On Saturday 04 September 2010, Bruno Haible wrote: >> Hi, >> >> Jim Meyering wrote on bug-gnulib: >> > Coreutils tests with an absolute build directory name that >> > contains a space. Not quoting this directory name caused a >> > failure. * tests/test-vc-list-files-git

Re: absolute build directory with spaces

Bruno Haible wrote: > Jim Meyering wrote on bug-gnulib: >> Coreutils tests with an absolute build directory name that contains >> a space. Not quoting this directory name caused a failure. >> * tests/test-vc-list-files-git.sh: Quote PATH dir name. >> ... >> --- a/tests/test-vc-list-files-git.sh >>

Re: absolute build directory with spaces

On Saturday 04 September 2010, Bruno Haible wrote: > Hi, > > Jim Meyering wrote on bug-gnulib: > > Coreutils tests with an absolute build directory name that > > contains a space. Not quoting this directory name caused a > > failure. * tests/test-vc-list-files-git.sh: Quote PATH dir name. > > ...

Re: gnulib-tool: new options --add-import, --remove-import

Eric Blake wrote: > > I would propose to > >- Rename the current --import option to --add-import, > >- Introduce a new --import option, that is like the previous --import > > option except that it ignores the contents of gnulib-cache.m4, > >- Add a --remove-import option that can b

Re: absolute build directory with spaces

Hi, Jim Meyering wrote on bug-gnulib: > Coreutils tests with an absolute build directory name that contains > a space. Not quoting this directory name caused a failure. > * tests/test-vc-list-files-git.sh: Quote PATH dir name. > ... > --- a/tests/test-vc-list-files-git.sh > +++ b/tests/test-vc-li

Re: isnan/isinf -> LGPL

l...@gnu.org (Ludovic Courtès) writes: > We’d like to use ‘isnan’ and ‘isinf’ in libguile, which is LGPLv3+. > Could you make these two modules LGPL? This is fine with me. I think that you will also need Bruno Haible to agree. -- "A computer is a state machine. Threads are for people who cant

[PATCH] maint.mk: avoid obscure sc_copyright_check failure in coreutils

Today I saw "make syntax-check" fail like this: $ make sc_copyright_check copyright_check grep: b/coreutils-8.5.147-cd8831/lib/version-etc.c: No such file or directory ./tests/torture/taint/a maint.mk: out of date copyright in lib/version-etc.c; update it make: *** [sc_cop

Re: don't augment PATH in TESTS_ENVIRONMENT

Bruno Haible wrote: >> Good catch. Thanks for doing that. >> Your patch looks right > > OK, applied. I've just pushed this correction. Sorry I didn't catch it in review. >From 3389c116ca7f63bcad9f987cdae5774b1ec2 Mon Sep 17 00:00:00 2001 From: Jim Meyering Date: Sat, 4 Sep 2010 17:43:39 +02

Re: isnan/isinf -> LGPL

On Sat, Sep 4, 2010 at 2:55 PM, Ludovic Courtès wrote: > Hello, > > We’d like to use ‘isnan’ and ‘isinf’ in libguile, which is LGPLv3+. > Could you make these two modules LGPL? > > Thanks, > Ludo’. I plan to use it on scientific software, and I will prefer LGPL2+ bastien

isnan/isinf -> LGPL

Hello, We’d like to use ‘isnan’ and ‘isinf’ in libguile, which is LGPLv3+. Could you make these two modules LGPL? Thanks, Ludo’. pgpFaDhnxjeDm.pgp Description: PGP signature

gnulib-tool: don't talk about CVS any more

A small change in terminology: 2010-09-04 Bruno Haible gnulib-tool: Don't talk about CVS any more. * gnulib-tool (func_usage, func_import): Write "version control" instead of CVS. --- gnulib-tool.origSat Sep 4 15:04:38 2010 +++ gnulib-tool Sat Sep 4 15:04:34 201

Re: minimum perl version

Hi Jim, > However, I'd prefer to continue to report the offending version of Perl > and the minimum required version. One way to do that would be > to not suppress stderr. OK, as you like. I'm applying it like this: 2010-09-04 Bruno Haible update-copyright test: Improve output when

Re: don't augment PATH in TESTS_ENVIRONMENT

Hi Jim, > Good catch. Thanks for doing that. > Your patch looks right OK, applied. > The regexp isn't as tight as it could be, but it's > adequate for now Yes, I agree. Bruno

Re: strdup in C++ mode

> > I get a compiler error: > > > > In file included from sysdir.h:34:0, > > from dir-ops.cc:34: > > ../libgnu/dirent.h:380:1: error: '::dirfd' has not been declared > > > > This appeared since the changes to the lib/dirent.in.h > > > > OSX declares dirfd as a macro A similar c

Re: dirfd in C++ mode

Hi, Jarno Rajahalme wrote: > Apparently this was not the case on OSX (my case) or FreeBSD (see > http://savannah.gnu.org/bugs/?30721). > > I get a compiler error: > > In file included from sysdir.h:34:0, > from dir-ops.cc:34: > ../libgnu/dirent.h:380:1: error: '::dirfd' has not

Re: minimum perl version

Bruno Haible wrote: > Hi Jim, > >> diff --git a/tests/test-update-copyright.sh b/tests/test-update-copyright.sh >> index 2d1022a..607928d 100755 >> --- a/tests/test-update-copyright.sh >> +++ b/tests/test-update-copyright.sh >> @@ -16,6 +16,10 @@ >> # You should have received a copy of the GNU Gen

Re: don't augment PATH in TESTS_ENVIRONMENT

Bruno Haible wrote: > It is not possible to portably augment the same environment variable twice > in TESTS_ENVIRONMENT. > > Witness: The shell command >foo=a:$foo foo=b:$foo sh -c 'echo $foo' > prints > b:a: in ksh, OpenBSD /bin/sh > a:b: in Solaris 8 /bin/sh > b:in NetBSD /bin

Re: minimum perl version

Hi Jim, > diff --git a/tests/test-update-copyright.sh b/tests/test-update-copyright.sh > index 2d1022a..607928d 100755 > --- a/tests/test-update-copyright.sh > +++ b/tests/test-update-copyright.sh > @@ -16,6 +16,10 @@ > # You should have received a copy of the GNU General Public License > # alon

don't augment PATH in TESTS_ENVIRONMENT

Hi Jim, It is not possible to portably augment the same environment variable twice in TESTS_ENVIRONMENT. Witness: The shell command foo=a:$foo foo=b:$foo sh -c 'echo $foo' prints b:a: in ksh, OpenBSD /bin/sh a:b: in Solaris 8 /bin/sh b:in NetBSD /bin/sh and dash and in bash 3.2

Re: Failing to use gnulib bootstrap in libtool

On 3 Sep 2010, at 17:03, Bruno Haible wrote: > Hi Gary, Hallo Bruno, Thanks for your comments. > Gary V. Vaughan wrote: >> Is gnulib bootstrap designed for reuse in other projects? >> >> I'm finding it extremely difficult to understand a lot of the code, ... >> ... a lot of questions about the

Re: [PATCH] Set PATH_SEPARATOR the same way autoconf does.

Hi Stefano, > A mostly cosmetic patch. Please, next time, explain why the way autoconf does it is better than the way gnulib-tool does it. I can see two reasons, but they are not obvious without comments: - It works around a problem with the Korn shell, see