Re: Problems building coreutils HEAD against gnulib HEAD

Hello, * Eric Blake wrote on Tue, Feb 19, 2008 at 02:28:35PM CET: > [adding bug-automake] > > According to Jim Meyering on 2/19/2008 4:33 AM: > |> But I am, having seen it myself. It happens when you have a stale symlink > |> from an older copy of gnulib, but which now points nowhere because the

Re: GNUmakefile and VPATH

Hi Eric, * Eric Blake wrote on Tue, Mar 04, 2008 at 02:57:51PM CET: > According to Jim Meyering on 3/4/2008 4:37 AM: > |>> + [AC_CONFIG_LINKS([GNUmakefile:GNUmakefile])]) > |> Until Automake is fixed, this will cause > |> ./configure && make distclean > |> > |> to bogusly remove GNUmakefile

Re: new coreutils snapshot available

Hi Jim, * Jim Meyering wrote on Thu, Mar 20, 2008 at 06:49:35PM CET: > -dist_man_MANS = $(MAN) > +# We must include at least one literal name here, so that > +# automake-1.10.1 emits the required install-man* rules. > +dist_man_MANS = rm.1 $(MAN) You can instead also just s/dist_man_MANS/dist_man

Re: [PATCH] Generalize GNUmakefile, ...

Hi Jim, * Jim Meyering wrote on Thu, Mar 20, 2008 at 02:58:17PM CET: > > Thanks! Almost perfect. It's lacking $(srcdir) in a few places. Oh well, I suppose since nobody except me uses VPATH builds it I get to fix it (eventually) ... Cheers, Ralf _

Re: avoid mkdir/selinux failure when mknod is a shell built-in

Hi Eric, * Eric Blake wrote on Wed, Apr 16, 2008 at 03:07:42PM CEST: > According to Jim Meyering on 4/16/2008 6:57 AM: > | $ PATH=. /bin/sh -c 'exec mknod --version'|head -1 > | /bin/sh: mknod: --: unknown option > > Ouch - this looks like a POSIX compliance bug in exec; I'm adding > bug-autoc

Re: avoid mkdir/selinux failure when mknod is a shell built-in

[ re-added bug-autoconf ] * Eric Blake wrote on Wed, Apr 16, 2008 at 08:04:23PM CEST: > Subject: [PATCH] Document pdksh exec behavior. > > * doc/autoconf.texi (Limitations of Builtins) : New > subsection. > Discovered by Jim Meyering. This looks good to me, thanks. Cheers, Ralf __

b5_9x branch in git?

Hello there, Trying to dig some weird behavior with tee 6.10 (apparently seems to lose data when handling lots of it; details when available), I tried to dig in history. NEWS states: | * Major changes in release 5.97 (2006-06-24) [stable] | * Major changes in release 5.96 (2006-05-22) [stable] |

Re: b5_9x branch in git?

* Jim Meyering wrote on Wed, Jun 11, 2008 at 02:23:02PM CEST: > Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > > > > Trying to dig some weird behavior with tee 6.10 (apparently seems to > > lose data when handling lots of it; details when available), Scratch that, pr

coreutils.texi: Drop leading blanks.

Hi Jim, this patch removes a couple of ugly extra spaces from the info file (script to find them posted here: <http://gcc.gnu.org/ml/gcc-patches/2008-06/msg00920.html>). Cheers, Ralf 2008-06-16 Ralf Wildenhues <[EMAIL PROTECTED]> * doc/coreutils.texi (join invocation):

finding misplaced changes with git

Hi Jim, all, in a recent commit you write | * HACKING: describe how to find a misplaced change-set | --- a/HACKING | +++ b/HACKING | @@ -360,6 +360,22 @@ Miscellaneous useful git commands |you an interface with which you can reorder and modify arbitrary |change sets on that b

[PATCH] Again, do not change the mode of all directories below $HOME.

* tests/CuTmpdir.pm (chmod_tree): Do not run chmod on undefined argument, can happen when the build path contains spaces. --- Hi Jim, this fixes a regression of "make check" when source and build tree live in a directory with spaces in the name. The regression was introduced some time after I po

Re: [PATCH] Again, do not change the mode of all directories below $HOME.

Hi Jim, * Jim Meyering wrote on Tue, Jul 22, 2008 at 01:17:20PM CEST: > Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > > this fixes a regression of "make check" when source and build tree live > > in a directory with spaces in the name. The regression was introduced

Re: compiling error

Jeph Cowan ucar.edu> writes: > > Making all in man > > cd .. && make am--refresh > > make: 1254-002 Cannot find a rule to create target \.x from dependencies. > > Stop. > > make: 1254-004 The error code from the last command is 1. Try using GNU make instead of the native one. The $(NO_I

[PATCH] * bootstrap: Fix unportable expr usage.

--- Hi Jim, This fixes a bootstrap failure on FreeBSD due to: $ expr --gnulib-srcdir=foo : '--gnulib-srcdir=\(.*\)' expr: illegal option -- - usage: expr [-e] expression Cheers, Ralf bootstrap |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/bootstrap b/bootstrap index

Re: compiling error

* Jim Meyering wrote on Fri, Aug 01, 2008 at 11:11:37AM CEST: > Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > > Jeph Cowan ucar.edu> writes: > >> > Making all in man > >> > cd .. && make am--refresh > >> > make: 1254

Re: [PATCH] Again, do not change the mode of all directories below $HOME.

Hi Jim, and sorry for the delay, * Jim Meyering wrote on Tue, Jul 22, 2008 at 09:42:30PM CEST: > Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > > > >> But seriously, considering the potential for damage and mischief, > >> perhaps it's time to add infrastruct

[PATCH] Fix build-aux/check.mk for non-GNU make.

* build-aux/check.mk ($(TEST_LOGS)) [!GNU_MAKE]: Check for a $(TESTS) test in the build dir, before one in srcdir. --- In gnulib-tests, 'make check' causes non-GNU make to try to update and execute $srcdir/test-EOVERFLOW: $ pmake check [...] pmake check-TESTS gcc -std=gnu99 -g -O2 -Wl,--as-need

[PATCH] Fix build-aux/check.mk for non-GNU make.

* build-aux/check.mk ($(TEST_LOGS)) [!GNU_MAKE]: Check for a $(TESTS) test in the build dir, before one in srcdir. --- Hmpf. First, this updated patch fixes the alignment of backslash newline. Second, I should note that this whole shenanigan only works well because automake inserts an '$(MAKE) .

test failures on AIX 5.3: misc/sort-merge, test-copy-acl.sh

Hi Jim, I'm getting the following test failures on AIX 5.3. They are using current git coreutils and gnulib, and gettext 0.16.1 IIRC. The UNKNOWN-dirty is because I must like it that way, I guess. ;-) Cheers, Ralf === GNU coreutils UNKNOWN

Re: compiling error

continuing the topic: misc/sort-merge failure (also for me, neither of the suggestions there help) and * Jim Meyering wrote on Tue, Aug 05, 2008 at 11:10:44PM CES

Re: test failures on AIX 5.3: misc/sort-merge, test-copy-acl.sh

* Jim Meyering wrote on Sat, Aug 02, 2008 at 05:56:07PM CEST: > Regarding the ACL failure, > I don't have access to any AIX systems, so if you > can give a little more info, that'd help. > > I.e., in gnulib-tests/test-sameacls.c, there are two blocks: > > #elif HAVE_ACLX_GET /* AIX */ > ... >

Re: compiling error

Hi Jim, * Jim Meyering wrote on Tue, Aug 12, 2008 at 11:07:12PM CEST: > From: Jim Meyering <[EMAIL PROTECTED]> > Date: Tue, 12 Aug 2008 23:05:27 +0200 > Subject: [PATCH] sort: don't use undefined variable in mkstemp failure > diagnostic > > * src/sort.c (create_temp_file): Use temp_dir, not "fil

Re: compiling error

* Jim Meyering wrote on Tue, Aug 12, 2008 at 11:24:44PM CEST: > Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > > --- err_ok 2008-08-12 19:24:03.0 + > > +++ err 2008-08-12 19:24:03.0 + > > @@ -1,2 +1,3 @@ > > ++ LC_ALL=C > > 1+0 r

Re: compiling error

* Jim Meyering wrote on Tue, Aug 12, 2008 at 11:33:23PM CEST: > Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > > FAIL: misc/expr.log (exit: 1) > > = > > > > expr: arbitrary-precision support is not available > > expr (GNU coreut

Re: compiling error

* Jim Meyering wrote on Wed, Aug 13, 2008 at 10:47:13AM CEST: > Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > > FAIL: cp/thru-dangling.log (exit: 1) > > > ... > > --- out 2008-08-12 19:24:01.0 + > > +++ exp

Re: [PATCH] df: new option: --total (-c) to produce grand total (in the same way as du)

Hello, > Bruno Haible <[EMAIL PROTECTED]> wrote: > > Jim Meyering wrote: > > > >>> Some of the changes (& => &&) are unconditional improvements, imho. > > > > I disagree. The & => && change inserts a conditional branch into the control > > flow, with the potential to save a single memory access. I

[PATCH] fix minor shell issues in test suite

* tests/misc/help-version: Fix bad quoting. * tests/cp/same-file: Fix unportable shell quoting. * tests/mv/part-symlink: Likewise. --- Hello Jim, the "`..."..."...`" in part-symlink is unportable (see Autoconf manual). I figured let's adjust same-file likewise so if you add inner "..." bits it do

[PATCH] simplify installation rules, using new Automake

This relies on development Automake to provide multi-file installation, and avoids relying on undocumented Automake interfaces. It also removes special-casing for `['. * configure.ac (AM_INIT_AUTOMAKE): Depend on 1.10a. (CROSS_COMPILING): New Automake conditional. * src/Makefile.am (install-exec-a

Re: [PATCH] simplify installation rules, using new Automake

* Jim Meyering wrote on Tue, Sep 09, 2008 at 08:14:38PM CEST: > Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > > > > I wasn't sure why you needed the special-casing for '['. > > Which shell has problems with it? The commit which adds the > > Hmm...

[PATCH] various VPATH-related fixes

* maint.mk (VC_LIST): Prepend '$(srcdir)/'. (patch-check): Fix to make it work with a VPATH build. * src/Makefile.am (sc_tight_scope): Likewise. * man/Makefile.am (.x.1): Do not make outputs unwritable. --- Hello Jim, this makes maintainer-distcheck work better in a VPATH build setup. Sorry, but

Re: [BUG] coreutils-6.12 "ginstall" bug

Hello Deepak, Eric, Eric Blake byu.net> writes: > According to Deepak Barua on 9/20/2008 11:12 PM: > >I was just cross compiling my MIPS64 platform when i > > noticed a major error in coreutils - 6.12 the "src/ginstall" which is > > compiled , is compiled in the target archit

[PATCH] fix installation with ./ginstall in src

* src/Makefile.am (cu_install_program): New variable, set to either ./ginstall or @INSTALL_PROGRAM@ (for cross compilation). (INSTALL_PROGRAM): Override AC_SUBST unconditionally, to avoid warning, and wrong initialization order. --- D'oh. If and AC_SUBSTed value is not overridden unconditionally

Re: two

Hi Jim, Jim Meyering meyering.net> writes: > Subject: [PATCH] avoid "make distcheck" failure due to src/Makefile.am > > * src/Makefile.am (cu_install_program): Define to $(INSTALL_PROGRAM), > not obsolescent @[EMAIL PROTECTED] > --- a/src/Makefile.am > +++ b/src/Makefile.am > @@ -467,7 +467,7 @

Re: rm -rf: avoid ext3/4 O(N^2) performance hit, further librarify remove.c

Hello Jim, a tiny nit again: Jim Meyering meyering.net> writes: > +/* A comparison function to sort on increasing inode number. */ > +static int > +compare_ino (void const *av, void const *bv) > +{ > + struct readdir_data const *const *a = av; > + struct readdir_data const *const *b = bv; > +

[PATCH] fix make variable quotation error

* tests/check.mk (TESTS_ENVIRONMENT): Quote shell variable $tmp__, fix expansion. --- Hi Jim, a minor nit patch. Cheers, Ralf tests/check.mk |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/tests/check.mk b/tests/check.mk index e1a8e35..c471d1f 100644 --- a/tests/check

Re: [PATCH] bootstrap: check for AC_PROG_LIBTOOL as well as AM_PROG_LIBTOOL

* Jim Meyering wrote on Sun, Oct 05, 2008 at 01:01:14PM CEST: > "Debarshi Ray" <[EMAIL PROTECTED]> wrote: > >> Subject: [PATCH] bootstrap: check for AC_PROG_LIBTOOL as well as > >> AM_PROG_LIBTOOL > >> * build-aux/bootstrap: Check for AC_PROG_LIBTOOL, as well as the > >> obsolete AM_PROG_LIBTOOL.

[PATCH] avoid use of undefined variable in warning

* tests/CuTmpdir.pm (chmod_tree): Do not warn if $dir is undefined. --- Hi Jim, I'm currently debugging my parallel Automake TESTS pending patch using coreutils' test suite. This turned up as side issue; I haven't seen this show up otherwise. I'll post patches when I get the bugs that I see iro

Re: Threaded versions of cp, mv, ls for high latency / parallel filesystems?

Hello Andrew, Andrew McGill lunch.za.net> writes: > >     find -type f -print0 | > xargs -0 -n 8 --max-procs=16 md5sum >& ~/md5sums > >     sort -k2 < md5sums > md5sums.sorted To avoid losing output, use append mode for writing: : > ~/md5sums find -type f -print0 |

Re: du --files-from feature request

Hello Pádraig, Pádraig Brady draigBrady.com> writes: > Note `make check` took about 2 hours due to the very slow msgmerge, > and I checked in anyway as I thought I couldn't break anything > with a simple doc emhancement :) Use msgmerge from CVS gettext. It is roughly 10 times faster for coreuti

[PATCH] more portable bootstrap procedure

, $LIBTOOLIZE. Signed-off-by: Ralf Wildenhues --- Hello Jim, I know bootstrap isn't meant to necessarily be portable. But it's just so much more comfortable to be able to use a git tree also on non-GNU systems, that e.g. have GNU tools installed with a 'g' program prefix (in this ca

Re: Bug in autoconf 2.62 with old GNU awk

[ moving from bug-autoconf ] Hello Daniel, * Daniel Richard G. wrote on Sat, Dec 13, 2008 at 07:46:14AM CET: > I've encountered an Autoconf-related bug in attempting to build GNU coreutils > 6.12 (packaged with autoconf 2.62) on an older Tru64 system. > > % ./configure --disable-nls >

Re: [PATCH] more portable bootstrap procedure

* Jim Meyering wrote on Sat, Dec 13, 2008 at 01:09:10PM CET: > Ralf Wildenhues wrote: > > > > There is one question I have on this: coreutils requires 'tar', my patch > > will allow $TAR as GNU tar. However, Automake's macros will honor > > $AMTAR only

Re: [PATCH] more portable bootstrap procedure

* Jim Meyering wrote on Sat, Dec 13, 2008 at 01:52:46PM CET: > Ralf Wildenhues wrote: > > * Jim Meyering wrote on Sat, Dec 13, 2008 at 01:09:10PM CET: > >> Ralf Wildenhues wrote: > >> > > >> > There is one question I have on this: coreutils requires &#x

Re: [PATCH] more portable bootstrap procedure

* Jim Meyering wrote on Sat, Dec 13, 2008 at 03:29:44PM CET: > Ralf Wildenhues wrote: > > > > Hmm, ok, I understand the point. Well, up to you, that s/TAR/AMTAR/ > > change would be fine with me. > > Since it's your change, you do need to sign off on the incremen

Re: Bug in autoconf 2.62 with old GNU awk

* Daniel Richard G. wrote on Sat, Dec 13, 2008 at 10:37:30PM CET: > Here is the real problem---not gawk(1), but indeed tr(1): > > % ( echo foo ; echo bar ) | tr '\015\012' ' ' > foo > bar > % ( echo foo ; echo bar ) | tr '\015\012' ' ' < note the two-space > string > foo bar % > > The expe

timespec declaration issue on Tru64 (was: Bug in autoconf 2.62 with old GNU awk)

[ adding bug-gnulib, removing bug-autoconf ] * Daniel Richard G. wrote on Sat, Dec 13, 2008 at 11:16:28PM CET: > However, I'm running into a more tricky issue during the build... > > source='sig2str.c' object='sig2str.o' libtool=no DEPDIR=.deps depmode=tru64 > /bin/ksh ../build-aux/depcomp cc

Re: timespec declaration issue on Tru64

Hello, and sorry for the delay, * Daniel Richard G. wrote on Mon, Dec 15, 2008 at 02:49:19AM CET: > > Anyway, I was playing around with this a bit more. The compiler is choking > somewhere inside the #include at the top of sig2str.c. This was already fixed, thanks! [...] > Everything else buil

Re: timespec declaration issue on Tru64

Hi Bruno, * Bruno Haible wrote on Sun, Dec 21, 2008 at 06:22:01PM CET: > Ralf Wildenhues wrote: > > > GNU Make got through that without a problem, but... should gmake be a > > > prerequisite for building coreutils? > > ... > > I guess the easiest would be to requ

Re: FYI: I've pushed a few maint changes, and...

Hello Jim, Jim Meyering meyering.net> writes: > > I mistakenly pushed a merge commit! I don't think that is a problem at all. Actually, once I can find a decent chunk of time again to work on GNU software, I intend to eventually change strategy for Automake and Libtool, to use 'git merge' much

test-fflush2 failure

Hello, on this Debian testing system with GNU C Library stable release version 2.7, by Roland McGrath et al. Copyright (C) 2007 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A

Re: [PATCH] maint: mention how to run a single test in HACKING docs

> Pádraig Brady draigBrady.com> wrote: > > + env DEBUG=yes VERBOSE=yes make check -C tests TESTS=mv/hard-link-1 >> log 2>&1 FWIW, 'make -C' is GNU make-specific, the portable equivalent would be cd tests && env DEBUG=yes VERBOSE=yes make check TESTS=... and catering to even more ugly make iss

Re: [PATCH] maint: mention how to run a single test in HACKING docs

Hi Jim, * Jim Meyering wrote on Fri, Feb 13, 2009 at 12:33:34PM CET: > Ralf Wildenhues wrote: > > > > FWIW, 'make -C' is GNU make-specific, the portable equivalent would be [...] > Thanks for the advice, but I'm beginning to think that it's fine to >

Re: [PATCH] * HACKING: avoid trailing white space

Hi Jim, Jim Meyering writes: > > This is obviously incomplete (the FIXME, and no configuration > recommendations for Emacs' Whitespace), but we have to start somewhere. > As usual, suggestions welcome. Either of these: chmod +x .git/hooks/pre-commit git config apply.whitespace error-all The

[PATCH] * HACKING (Avoid trailing white space): Mention how git can help.

--- Hi Jim, * Jim Meyering wrote on Mon, Mar 02, 2009 at 10:34:41PM CET: > > Good idea. Thanks! > I'll push this tomorrow, unless you'd prefer something else. How about this instead? I looked at git a bit more, and have little experience with git apply (not sure whether it's used all over the

parallel-tests

Hi Jim, this patch enables the use of Automake's parallel-tests instead of using check.mk (use the 'next' branch of git Automake). With it, coreutils make -jN check still passes, but distcheck fails, for reasons not yet apparent to me. FAIL: mv/i-1 (exit: 255) Error

Re: parallel-tests

Hi Jim, * Jim Meyering wrote on Tue, Mar 17, 2009 at 02:40:59PM CET: > Ralf Wildenhues wrote: > > this patch enables the use of Automake's parallel-tests instead of using > > check.mk (use the 'next' branch of git Automake). With it, coreutils > > make

Re: [PATCH] sort: Add --threads option, which parallelizes internal sort.

Hi Paul, all, Paul Eggert writes: > > This patch is by Glen Lenker, Matt Pham, Benjamin Nuernberger, Sky > Lin, TaeSung Roh, and Paul Eggert. It adds support for parallelism > within an internal sort. On our simple tests on a 2-core desktop x86, > overall performance improved by roughly a facto

Re: [PATCH] sort: Add --threads option, which parallelizes internal sort.

Hello Paul, Glen, Jim, [ I already wrote this in part to Glen off-list, sorry for the duplication ] * Paul Eggert wrote on Fri, Apr 03, 2009 at 09:57:54PM CEST: > Of course we cannot reasonably expect this one performance improvement > to make 'sort' run 16x faster on a 16-CPU machine. No. Le

Re: [PATCH] sort: Add --threads option, which parallelizes internal sort.

* Paul Eggert wrote on Fri, Apr 03, 2009 at 09:57:54PM CEST: > More important, it's not clear to me what the role of the test suite > ought to be. Should the test really fail if it doesn't get enough > performance improvement with 2 threads? How do we decide what's > "enough"? None of our other

Re: Core-utils 7.2; building only 'su'

Hello Alfred, Eric, * Alfred M. Szmidt wrote on Tue, Apr 14, 2009 at 02:49:30PM CEST: >>Hmmm. Would it be worth changing autoconf to make './configure >>--help' state something like the following: >> >>| Some influential environment variables: >>| ... >>

[PATCH] Fix some comment typos.

* bootstrap: Fix comment typos. * src/pr.c: Likewise. --- Hello Jim, all, a trivial patch. :-) Cheers, Ralf bootstrap |6 +++--- src/pr.c |4 ++-- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/bootstrap b/bootstrap index 27e4ec2..73a850f 100755 --- a/bootstrap +++ b/

Re: [PATCH] sort: Add --threads option, which parallelizes internal sort.

Hello Paul, Glen, Jim, all, * Paul Eggert wrote on Fri, Apr 03, 2009 at 09:57:54PM CEST: > Of course we cannot reasonably expect this one performance improvement > to make 'sort' run 16x faster on a 16-CPU machine. That is because the > improvement parallelizes only one part of 'sort'. Even assu

Re: [PATCH] sort: Add --threads option, which parallelizes internal sort.

* Pádraig Brady wrote on Mon, Apr 20, 2009 at 01:57:59AM CEST: > Ralf Wildenhues wrote: > > > > This comparison isn't entirely fair, as the splicing was done as a > > precomputation. However, the difference is so pronounced that even > > taking the splicing into

Re: [PATCH] build: use automake's new $(AM_V_GEN) and $(AM_V_at) variables

Hi Jim, Jim Meyering writes: > --- a/src/Makefile.am > +++ b/src/Makefile.am > @@ -290,26 +290,29 @@ editpl = sed -e 's,@''PERL''@,$(PERL),g' > > BUILT_SOURCES += dircolors.h > dircolors.h: dcgen dircolors.hin > - @rm -f $@ $...@-t > - $(PERL) -w -- $(srcdir)/dcgen $(srcdir)/dircolors.h

[PATCH] Fix check-AUTHORS skip logic.

* src/Makefile.am (check-AUTHORS): When this test is skipped, be sure to avoid all commands in the recipe, not just those passed to the first shell. --- Hello, without this patch, I'm getting the following 'make check' failure: check-AUTHORS: skipping this check diff: authors-actual: No such

Re: [PATCH] build: use automake's new $(AM_V_GEN) and $(AM_V_at) variables

Hi Jim, * Jim Meyering wrote on Sat, Apr 25, 2009 at 08:04:36AM CEST: > Ralf Wildenhues wrote: > > Jim Meyering writes: > >> + $(AM_V_GEN) > >> + $(AM_V_at)rm -f $@ $...@-t > > Thanks for using these. Note the $(AM_V_GEN) will expand to the empty > >

Re: improve INSTALL contents (was: Core-utils 7.2; building only 'su')

Hi Eric, thanks for pursuing this. * Eric Blake wrote on Wed, May 13, 2009 at 02:51:34PM CEST: > @@ -156,7 +158,25 @@ Installation Names > In addition, if you use an unusual directory layout you can give options > like @option{--bind...@var{dir}} to specify different values for > particular ki

Re: improve INSTALL contents

* Alfred M. Szmidt wrote on Fri, May 15, 2009 at 04:45:21AM CEST: >In addition, if you use an unusual directory layout you can give >options like @option{--bind...@var{dir}} to specify different >values for particular kinds of files. Run @samp{configure --help} >for a list of the d

Re: improve INSTALL contents

Alfred, can you please also read, and follow ? I'm sure you must have missed it because I failed to spam it to three mailing lists. But your repetitions are just as boring as those from everyone else. And get bug-coreutils and aut

Re: coreutils-5.96 doesn't build (out of the box)

Hi Sam, Jim, * Jim Meyering wrote on Sat, May 27, 2006 at 07:31:45AM CEST: > Sam Sirlin <[EMAIL PROTECTED]> wrote: > > Thanks very much for coreutils. 5.95 builds fine, however 5.96 does > > not. Note that runing autoconf solves the problem > > config.status: executing depfiles commands > > ./con

Some minor issues with 5.96

- Solaris 2.6 doesn't grok these lines: | base64.1: $(common_dep) $(srcdir)/base64.x ../src/base64.c in that ../src/base64.c isn't searched through VPATH. Using GNU make works. Solaris 7 has this fixed. - Let's have `make check' be portable, so users can easily use it. Patch be

Re: Some minor issues with 5.96

* Ralf Wildenhues wrote on Sat, May 27, 2006 at 02:53:32PM CEST: > - Let's have `make check' be portable, so users can easily use it. > Patch below. > * doc/Makefile.am: Use `$(EGREP)' instead of `grep -E'. Hmm. Seems that wasn't enough. | grep: RE erro

Solaris 8: runaway processes in check

[ BTW, please Cc: me on replies ] `make -k check' of 5.96 has a rather serious problem on Solaris 8. Let's say, at one point it causes a fork bomb, I see lots of processes of the form | sh -c ../../../coreutils-5.96/tests/misc/sort -m 'empty' 'f' > m1.O 2> m1.E in the `ps' output. Before I could

Re: Some minor issues with 5.96

Hi Jim, * Jim Meyering wrote on Sat, May 27, 2006 at 03:48:20PM CEST: > > I'm not too worried about portability to Solaris 2.6's make; > I see little downside to leaving this as-is. Besides, isn't > it already documented that if you want a VPATH build to succeed, > you have to have GNU make? Ye

Re: Solaris 8: runaway processes in check

* Jim Meyering wrote on Sat, May 27, 2006 at 04:10:20PM CEST: > Please identify the test that is causing trouble. > Here's how to start: > > cd tests/misc > make check TESTS=sort > > If that test is the one causing the trouble, > then there's something very strange going on. Well. It's the

Re: coreutils-5.96 doesn't build (out of the box)

> > > config.status: executing depfiles commands > > > ./config.status: ./.deps/__fpending.Po: No such file or directory Confirmed. I see this on AIX with its grep. Patch against Automake coming up in another mail. Cheers, Ralf ___ Bug-coreutils mai

do not overwrite MAKEINFO

This patch allows `make' to succeed on systems without `makeinfo'. Cheers, Ralf * doc/Makefile.am: Use `AM_MAKEINFOFLAGS' rather than overwriting `MAKEINFO', so that `missing' can do its job. Index: doc/Makefile.am =

AIX grep limitation: coreutils build failure

Apologies for the cross post. AIX grep allows 2048 characters in a line, and fails otherwise. This breaks coreutils-5.96 configure: | grep: Maximum line length of 2048 exceeded. [...] | grep: Maximum line length of 2048 exceeded. | configure: error: could not make ./config.status because of this

AIX tests failures

With coreutils 5.96, I get three failures on AIX 4.3.3, namely: cp/fail-perm, rm/inaccessible, help-version. Verbose output is below. The last one looks funny. :-) Cheers, Ralf $ TESTS=fail-perm VERBOSE=yes make -e check make check-TESTS + cp --version cp (GNU coreutils) 5.96 Copyright

Re: AIX grep limitation: coreutils build failure

> Autoconf patch: This one wasn't enough (grep from different AIX versions seem to differ here). Updated patch below. Cheers, Ralf * lib/autoconf/status.m4 (_AC_OUTPUT_FILES_PREPARE): Use `tr' to shorten the line length for the delimiter test, for AIX grep. Index: lib/autoconf/

OSF/4.0D strtold

Tru64 UNIX 4.0D doesn't provide strtold (in the standard library at least), but /usr/include.dtk/stdlib.h provides a declaration. Thus the compile test in c-strtod.m4 fails. This causes a link failure for coreutils-5.96 printf. The patch below seems to fix this (but I don't know whether it shoul

Re: coreutils-5.96 doesn't build (out of the box)

* Sam Sirlin wrote on Sun, May 28, 2006 at 01:20:04AM CEST: > > Here's the full output of the bad configure (autoconf 2.59 produced a > working configure) I still have no idea what's going on in your case (and I guess the bug you observe is different from the one on AIX). So I have a few further

Re: AIX tests failures

Hi Jim, Thanks for fixing. Small nit: * Jim Meyering wrote on Sun, May 28, 2006 at 11:04:05AM CEST: > Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > > > With coreutils 5.96, I get three failures on AIX 4.3.3, namely: ^^^ > +#

Re: AIX tests failures

Hi Jim, * Jim Meyering wrote on Sun, May 28, 2006 at 11:22:42AM CEST: > Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > >> > With coreutils 5.96, I get three failures on AIX 4.3.3, namely: > > ^^^ > >> +# HPUX app

5.96: du test failure on Darwin

On powerpc-apple-darwin8.2.0, I get one test failure: Cheers, Ralf $ cd tests/du $ make check TESTS=basic VERBOSE=yes make check-TESTS + du --version du (GNU coreutils) 5.96 Copyright (C) 2006 Free Software Foundation, Inc. This is free software. You may redistribute copies of it under the term

Re: AIX grep limitation: coreutils build failure

Hi Paul, * Paul Eggert wrote on Sun, May 28, 2006 at 10:50:44AM CEST: > > I'm a bit reluctant to rely on 'tr' given its portability hassles. Well, the same can be achieved with (including M4 quoting) sed "s/[[$as_cr_Letters]]//g" but I don't understand the portability problems given the spec

5.96: some locale squashing

I need this patch for successful `make check' on a GNU/Linux with non-English locale settings. Cheers, Ralf * tests/cp/fail-perm: source lang-default. * tests/rm/inaccessible: Likewise. --- tests/cp/fail-perm 2004-06-28 20:47:24.0 +0200 +++ tests/cp/fail-perm 2006-05-28

Re: AIX tests failures

Hi Jim, * Jim Meyering wrote on Sun, May 28, 2006 at 03:48:21PM CEST: > Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > > > With coreutils 5.96, I get three failures on AIX 4.3.3, namely: > > cp/fail-perm, rm/inaccessible, help-version. > > $ env VERBOSE=yes TESTS

Re: AIX tests failures

[ Cc:ing bug-gnulib ] * Jim Meyering wrote on Sun, May 28, 2006 at 07:58:24PM CEST: > Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > > > > ... AIX strndup is severely broken, at least on 4.3.3 and 5.1, similar > > to its strnlen; see also[1]. See for example this test:

Re: 5.96: du test failure on Darwin

* Jim Meyering wrote on Sun, May 28, 2006 at 03:07:08PM CEST: > Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > > On powerpc-apple-darwin8.2.0, I get one test failure: > > $ cd tests/du > > $ make check TESTS=basic VERBOSE=yes > ... > > out exp differ: char 1, li

5.96: chgrp/basic failure on OpenBSD

Hi there, With 5.96, I get one test failure on i386-unknown-openbsd3.8. Cheers, Ralf $ cd tests/chgrp/ $ ls Makefile $ gmake check TESTS=basic VERBOSE=yes gmake check-TESTS gmake[1]: Entering directory `/tmp/build/tests/chgrp' + chgrp --version chgrp (GNU coreutils) 5.96 Copyright (C) 2006 Free

Re: 5.96: chgrp/basic failure on OpenBSD

Hi Paul, * Paul Eggert wrote on Mon, May 29, 2006 at 09:54:04AM CEST: > Ralf Wildenhues <[EMAIL PROTECTED]> writes: > > > With 5.96, I get one test failure on i386-unknown-openbsd3.8. > > Possibly you're suffering from this problem, noted in tests/chgrp/basic: >

5.96: 3 test failures on HP-UX 11.23

I get 3 failures on hppa2.0w-hp-hpux11.23: misc/close-stdout, touch/no-create-missing, and help-version (groups), see the verbose output below. Note that I also get the warning below. On ia64-hp-hpux11.23, the same tests fail. On hppa2.0w-hp-hpux11.11, I get no test failures, and no such warning.

Re: AIX grep limitation: coreutils build failure

Hi Paul, * Paul Eggert wrote on Mon, May 29, 2006 at 11:19:31AM CEST: > > OK, thanks, how about this fix instead? This is fine with me, thank you. > (My reluctance to use tr is due to the fact that we don't rely on it > now, so why add it) Fine with me, too. Please note though that tr is

Re: coreutils-5.96 doesn't build (out of the box)

* Sam Sirlin wrote on Mon, May 29, 2006 at 10:41:03PM CEST: >From: Ralf Wildenhues <[EMAIL PROTECTED]> > /bin/bash --version > echo $PATH > type mkdir expr dirname basename > > dirname is apparently the issue. I had an old dirname shell script > l

Re: 5.96: 3 test failures on HP-UX 11.23

Hi Paul, * Paul Eggert wrote on Tue, May 30, 2006 at 09:51:17AM CEST: > Thanks for reporting this. All these failures seem to be due to a > portability problem in lib/closeout.c. Could you please run, say, "cp > --verbose /dev/null /tmp/foo >&- >/dev/null" in a debugger, putting a > breakpoint o

Re: [bug-gnulib] Re: AIX tests failures

Hi Bruno, * Bruno Haible wrote on Tue, May 30, 2006 at 09:11:04PM CEST: > > I added your patch to gnulib, with 4 modifications: Thanks for applying, your modifications are all good. > > + test $gl_cv_func_strndup = no && > > + if test $gl_cv_func_strndup = no; then > > Was this intended redu

Re: [bug-gnulib] AIX tests failures

* Bruno Haible wrote on Tue, May 30, 2006 at 09:29:37PM CEST: > Ralf Wildenhues wrote: > > Tested on AIX 4.3.3, 5.1, 5.2 (first has strnlen and strndup broken, > > second has strnlen fixed, last has both fixed) > > Hmm? My results for AIX 5.1 differ: On AIX 5.1.0.0 I get

Re: coreutils-5.96 doesn't build (out of the box)

Hi Sam, * Sam Sirlin wrote on Wed, May 31, 2006 at 01:11:49AM CEST: >From: Ralf Wildenhues <[EMAIL PROTECTED]> >Is your script home-grown or does it have some wider usage? What does >it output upon > dirname -- / > > It's old code from SVr2, so it

Re: coreutils-5.96 doesn't build (out of the box)

Hi Paul, * Paul Eggert wrote on Wed, May 31, 2006 at 10:20:56AM CEST: > Ralf Wildenhues <[EMAIL PROTECTED]> writes: > > > +[if (as_dir=`dirname -- /` && test "$as_dir" = /) >/dev/null 2>&1; then > > Surely that should be > > test

  1   2   >