gmane.comp.gnu.core-utils.bugs

Re: (no subject)

Alfred M. Szmidt — 2008-12-03T16:49:46

I think you posted to the wrong list... Your message seems to relate to the GNU Debugger.

Re: [PATCH]: chmod, chown, chgrp: Reduce verbosity of silent mode

Jim Meyering — 2008-12-03T10:59:24

... I've pushed those two change sets.

Re: du --files-from feature request

Ralf Wildenhues — 2008-12-03T08:43:38

Hello Pádraig, Pádraig Brady

draigBrady.com> writes: Use msgmerge from CVS gettext. It is roughly 10 times faster for coreutils files. Cheers, Ralf

using gpg on Windows (was: (no subject))

Eric Blake — 2008-12-03T05:46:07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [Please use a better subject line, if you want to ensure your mail is not confused with junk mail] According to Martin Douglas on 11/29/2008 2:15 PM: You have reached the GNU Coreutils mailing list. The GNU Coreutils are the basic file, shell and text manipulation utilities of the GNU Operating System. You can learn more about GNU Coreutils here: http://www.gnu.org/software/coreutils/ The GNU Coreutils are part of the GNU Operating System. You can learn more about the GNU Project here: http://www.gnu.org/ But you are asking about gpg. I am sorry but this is the wrong mailing list. We are unable to help you here; you will probably have better luck with the gpg project: http://www.gnupg.org/ Meanwhile, it appears that you are asking about a w32 port of gpg; often-times, you will get more appropriate response for questions about using GNU software on Windows by asking the people that provide the precompiled binary that you are using (such as the c

(no subject)

Jan Halla — 2008-12-02T16:56:33

< at >menu * Overview:: Overview * Hardware:: POD, Pins, Power * Driver:: The Driver * Library:: A Library for Applications * Testing:: Is BDM working * GDB:: Building and using GDB * Server:: BDM Server < at >c Following blank line required for remaining bug in makeinfo conds/menus * Reporting Bugs:: Reporting Bugs * Index:: Index < at >end menu < at >end ifinfo < at >c --------------------------------------- < at >node Overview, Build System, Top, Top < at >chapter Overview < at >cindex what is this? Welcome to Background Debug Mode (BDM) support for GDB. BDM is emulator or debugger support in a range of Motorola processors. This package deals with the CPU32, and Coldfire family of processors. PowerPC processors are not supported by this package. CPU32 processors were the first processors to appear with BDM support. The Coldfire family's BDM module is similar

Re: [PATCH] avoid warnings about initialization of automaticaggregates

Jim Meyering — 2008-12-02T10:18:43

No trouble at all. Thanks for taking the time to think about it and to reply.

Re: [PATCH] avoid warnings about initialization of automaticaggregates

Pádraig Brady — 2008-12-02T10:08:15

Ah Ok. Sorry for the noise. Pádraig.

Re: [PATCH] avoid warnings about initialization of automaticaggregates

Jim Meyering — 2008-12-02T09:55:04

Only the temporary is static. The original code (that evokes a warning) is like this: mbstate_t mbstate = { 0, }; Using DECLARE_ZEROED_AGGREGATE, it's like this (modulo formatting onto two lines and the approximate line number) static mbstate_t s0_3724; mbstate_t mbstate = s0_3724; I considered using memset, but preferred the above. So I think we're ok.

Re: [PATCH] avoid warnings about initialization of automaticaggregates

Pádraig Brady — 2008-12-02T09:36:28

Absolutely. Thinking a bit more about your patch, I'm not sure about the use of static variables as this is a logically different thing. I.E. the static variables will only be initialised at program start, whereas 'type var = {0,}' would be initialised each time the scope is entered. For e.g. I think quote_name() in ls.c will now behave differently? I think you did this to support using this at global scope, but that also has the caveat that static is overloaded to mean don't export in that case. Or perhaps you meant to only do compile tests with -Wmissing-field-initializers (and -Dlint), but I think it would be nice to be able to test binaries built in this mode. Would it be better just to use memset() and restrict usage to automatic variables? For global scope one can use static if appropriate If we restrict it to auto variables and considering you can use {0, } to init scalar variables also, I would rename the macro to: /* With -Dlint, avoid overzealous gcc -Wmissing-field-initializers warning abo

Re: [PATCH] avoid warnings about initialization of automaticaggregates

Jim Meyering — 2008-12-02T07:31:43

Thanks. However, I prefer not to use this -Wno... option, because it could later hide some legitimate warnings in the affected files. Please tread lightly there. Or maybe even not at all ;-) Given our penchant for avoiding casts, that might not be soluble.

Re: fix du and wc wrt --files0-from=F

Jim Meyering — 2008-12-02T07:16:07

Thanks! I adjusted the log: wc: read and process --files0-from= input a name at a time, when the file name list is not too large. Before, wc would always read the entire file name list into memory and *then* process each file name. wc does read the list into memory when the list is known not to be too large; this is done in order to be able to align the output numbers, as it does with arguments specified on the command-line * src/wc.c: Include "argv-iter.h". (main): Rewrite to use argv-iter when the input file name list is known to be too large. * NEWS (Bug fixes): Mention it. I could go either way, and vacillated as I wrote. I'm not particularly attached to wc's alignment feature, dislike the added stat-related complexity, and yet, am reluctant to remove it. There are a few reasons not to change sort. Here's the main one: sort is different from wc and du in that typical usage won't usually involve more than 10s or 100s of files, and when there are many, th

Re: [PATCH] seq: plug a leak

Jim Meyering — 2008-12-02T06:39:11

Rats. Yes. Adding the fix to my list of ChangeLog bugs to be automatically fixed. This is the final straw. I'll push probable patches to a new branch from now on (it will be frequently rebased as things migrate onto master)

Re: [PATCH] avoid warnings about initialization of automaticaggregates

Pádraig Brady — 2008-12-01T23:46:55

Some notes on this issue: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36750 So the warning can be suppressed in gcc with -Wno-missing-field-initializers I must dust off and split up my patch to allow us to use -Wsign-compare cheers, Pádraig

Re: fix du and wc wrt --files0-from=F

Pádraig Brady — 2008-12-01T23:23:10

^^^ I'd also mention why wc tries to read the whole list into RAM if there's place (so that it can auto align the numbers outputted). I'm not sure number alignment is worth this extra code/complexity, but it's written now :) I presume you're not forgetting sort --files0-from as you've previously mentioned it. cheers, Pádraig.

Re: [PATCH] seq: plug a leak

Pádraig Brady — 2008-12-01T23:00:14

I presume you meant "factor: plug a leak" ?

[PATCH] seq: plug a leak

Jim Meyering — 2008-12-01T21:44:44

I've just pushed this: From 9461c4d8e58f080a6b27caa923820a4ac8eea6d5 Mon Sep 17 00:00:00 2001 From: Jim Meyering redhat.com> Date: Mon, 1 Dec 2008 22:39:58 +0100 Subject: [PATCH] seq: plug a leak * src/factor.c (emit_ul_factor): Call mpz_clear. --- src/factor.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/src/factor.c b/src/factor.c index 187143a..83cd0a8 100644 --- a/src/factor.c +++ b/src/factor.c < at >< at > -82,6 +82,7 < at >< at > emit_ul_factor (unsigned long int i) mpz_init (t); mpz_set_ui (t, i); emit_factor (t); + mpz_clear (t); } static void -- 1.6.0.4.1101.g642f8

Re: [bug #24974] Document that comm's option "-1","-2" and "-3"can be combined

Frank Lin PIAT — 2008-12-01T21:12:37

Actually, this one deserves an example too. I've probably read that manpage 50+ times, And i never understood what "-m" meant. Thanks, Franklin

Re: [bug #24974] Document that comm's option "-1","-2" and "-3" can be combined

Andreas Schwab — 2008-12-01T21:00:56

That only works when no data line begins with a TAB. sort -m does not have this problem. sort -u file1 file2 Andreas.

[PATCH] avoid warnings about initialization of automatic aggregates

Jim Meyering — 2008-12-01T20:21:13

Finally getting serious about avoiding warnings, I've just eliminated this batch: From c58b5daa337b16416be50adfeb3e99e3c009c891 Mon Sep 17 00:00:00 2001 From: Jim Meyering redhat.com> Date: Sun, 30 Nov 2008 22:37:42 +0100 Subject: [PATCH] avoid warnings about initialization of automatic aggregates * src/system.h (DZA_CONCAT0, DZA_CONCAT): New macros. (DECLARE_ZEROED_AGGREGATE): New macro. * src/ls.c (quote_name): Use it. * src/pathchk.c (portable_chars_only): Use it. * src/shred.c (main): Use it. * src/stty.c (main): Use it. * src/wc.c (SUPPORT_OLD_MBRTOWC): Use it. --- src/ls.c | 2 +- src/pathchk.c | 2 +- src/shred.c | 2 +- src/stty.c | 4 ++-- src/system.h | 13 +++++++++++++ src/wc.c | 2 +- 6 files changed, 19 insertions(+), 6 deletions(-) diff --git a/src/ls.c b/src/ls.c index 7619ceb..0081865 100644 --- a/src/ls.c +++ b/src/ls.c < at >< at > -3721,7 +3721,7 < at >< at > quote_name (FILE *out, const char *name, struct quoting_options const *options, reach its end, r

Re: [bug #24974] Document that comm's option "-1","-2" and "-3"can be combined

Frank Lin PIAT — 2008-12-01T19:44:45

Actually, I think both information are useful... Maybe something like: "suppress lines unique to FILE1 (suppress output of column 1)" but that's 79 character long... not really nice. So maybe: "suppress lines unique to FILE1 (i.e don't output column 1)" Yes, I love examples in manpages. Maybe just focus on what each command does very well. "Print lines present in both file1 and file2 (Intersection)." comm -12 file1 file2 "Print lines not in the other file, both way (Symmetric Difference)" comm -3 file1 file2 | sed 's/^\t*//' Note: This only works if the input files don't contain duplicated lines. "Print lines in file2 not present in file1 (Difference / Substraction):" grep -Fv -f file1 file2 "Print all distinct lines in file1 or file2 (Union):" sort -u file1 file 2 That feature is great. Actually, it's worth emphasizing that files should be sorted in the manpage: the sentence "Compare sorted files FILE1 and FILE2 line by line." is quite clear... for those who read it carefully. may be :

Re: [bug #24974] Document that comm's option "-1","-2" and "-3" can be combined

Eric Blake — 2008-12-01T20:10:47

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Pádraig Brady on 12/1/2008 10:15 AM: I like that proposal. I could go either way, but agree that --nocheck-order is probably a new-enough invention that we can remove it altogether. - -- Don't work too hard, make some time for fun as well! Eric Blake ebb9< at >byu.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkk0RMcACgkQ84KuGfSFAYBaTQCeM+m6Jz33BdzDXoNnCdEipZpe jPUAmQFSs5D7aVtwu0vK0hVeUDVrWxq2 =e4FZ -----END PGP SIGNATURE-----