(not subscribed, please CC replies to me.)
In cut_fields_mb in cut.c, wint_t wc is not initialized before being
compared to WEOF. It just so happens that when I compile it on my
system, through some miracle of perversity and stack layout, wc picks up
-1 as its initial value.
On cut.c line 836,
_POSIX2_VERSION in unistd.h, in descending order of importance.
One of the great things about GNU software in the past was that it
basically behaved the same (as much as possible) independent of the host
system. It did not gratuitiously change behavior based on system
settings.
Thus, it
On Thu, 2005-03-31 at 16:06 +0100, Tim Waugh wrote:
On Thu, Mar 31, 2005 at 12:11:25AM -0700, Zan Lynx wrote:
(not subscribed, please CC replies to me.)
In cut_fields_mb in cut.c, wint_t wc is not initialized before being
compared to WEOF. It just so happens that when I compile it on
On Thu, Mar 31, 2005 at 10:32:42AM +0200, Rene de Zwart wrote:
On Wed, Mar 30, 2005 at 11:43:24PM -0500, Paul Eggert wrote:
Rene de Zwart [EMAIL PROTECTED] writes:
I debbuged date from coreutils 5.3.0 and got
get_date (when, datestr, NULL);
with datestr=19370701
returned
Warren L Dodge [EMAIL PROTECTED] writes:
Here is an strace. I don't have access to the sources.
If you know who generated the software distribution operating on your
servers, then you should be able to get the sources from them.
The strace output says /bin/uname read /proc/cpuinfo, but I
The tsort documentation has a nice example to get us started,
tsort EOF
a b c...
will produce the output
a
b...
Why can't the ptx documentation have one also?
ptxEOF
[3 to 5 lines of input]
makes
[whatever output]
an example is worth a 1000 words.
Here is uname.c from the redhat release we use. Their coreutils-4.5.3
Also below are two patches that may be applied. They had uname mentioned in
them.
/* uname -- print system information
Copyright 1989, 1992, 1993, 1996, 1997, 1999, 2000, 2001, 2002 Free
Software Foundation, Inc.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Boris New on 3/31/2005 1:54 PM:
Hi,
I send you the zip file with the two files. I tested a lot of windows
port and all have this problem. I thought it was perhaps due to locale
on windows.
The format is the same and files are
I was surprised to see that pr didn't reject as invalid a
negative page number. I've checked this in:
2005-04-01 Jim Meyering [EMAIL PROTECTED]
Don't let pr treat +1:-1 like +1:18446744073709551615.
* src/pr.c (strtoumax): Remove declaration.
(first_last_page): Use