coreutils 5.92, rm on Solaris, bad error message

2005-10-31 Thread Keith Thompson
: cannot remove directory `tmpdir': Is a directory On a Linux-x86 system, this problem doesn't occur under any version of coreutils I've tried ( 5.2.1, 5.3.0, 5.90, 5.91, 5.92); they all correctly give: rm: cannot remove `tmpdir': Is a directory -- Keith Thompson <[EMAIL P

coreutils 5.93, more bad error messages on Solaris

2005-12-05 Thread Keith Thompson
tils) 5.93 % chgrp root tmp chgrp: changing group of `tmp': Not owner -- Keith Thompson (The_Other_Keith) [EMAIL PROTECTED] <http://www.ghoti.net/~kst> San Diego Supercomputer Center <*> <http://users.sdsc.edu/~kst> We must do something. This is somet

Re: coreutils 5.93, more bad error messages on Solaris

2005-12-05 Thread Keith Thompson
On Mon, Dec 05, 2005 at 11:10:22PM +0100, Jim Meyering wrote: > Keith Thompson <[EMAIL PROTECTED]> wrote: > > I'm seeing some more misleading error messages in corutils 5.93 > > on Solaris. These are similar to the problem I reported on > > Mon 2005-10-31, subjec

coreutils 6.0, Solaris 9 build failure

2006-08-15 Thread Keith Thompson
in a system header. Probably coreutils shouldn't try to provide a declaration or definition of gai_strerror() if the system already provides one. -- Keith Thompson (The_Other_Keith) [EMAIL PROTECTED] <http://www.ghoti.net/~kst> San Diego Supercomputer Center <*> <http://u

Re: coreutils 6.0, Solaris 9 build failure

2006-08-15 Thread Keith Thompson
On Tue 06-08-15 15:30, Paul Eggert wrote: > Keith Thompson <[EMAIL PROTECTED]> writes: > > > % uname -a > > SunOS elmak 5.9 Generic_118558-20 sun4u sparc SUNW,Sun-Blade-100 Solaris > > % config.guess > > sparc-sun-solaris2.9 > > % gcc --version >

Re: coreutils 6.0, Solaris 9 build failure

2006-08-15 Thread Keith Thompson
On Tue 06-08-15 16:50, Paul Eggert wrote: > Keith Thompson <[EMAIL PROTECTED]> writes: > > > There's also a gcc 4.1.1 on the system. I'll try again with that. > > Thanks. I got the same error with gcc 4.1.1. > You might also want to try with /opt/sfw/bin/

Re: coreutils 6.0, Solaris 9 build failure

2006-08-15 Thread Keith Thompson
I've also run into a build problem on Solaris 7; details to follow. -- Keith Thompson (The_Other_Keith) [EMAIL PROTECTED] <http://www.ghoti.net/~kst> San Diego Supercomputer Center <*> <http://users.sdsc.edu/~kst> We must do something. This is something. The

Re: coreutils 6.0, Solaris 9 build failure

2006-08-16 Thread Keith Thompson
On Tue 06-08-15 22:12, Paul Eggert wrote: > Keith Thompson <[EMAIL PROTECTED]> writes: > > > I got the same error with gcc 4.1.1. > > Are you building GCC with the Sun linker, or with the binutils linker? > I'm doing the former, and that might be related to the

"split --verbose" fails

2003-06-26 Thread Keith Thompson
ind of longopts usage (using the address of the flag variable). The only other case I found was su's --preserve-environment option, but that seems to work correctly. -- Keith Thompson (The_Other_Keith) [EMAIL PROTECTED] <http://www.ghoti.net/~kst> San Diego Supercomputer Center

bug#72567: printf: Incorrect description of "%b"

2024-08-10 Thread Keith Thompson
There are three different descriptions of the printf(1) "%b" format: - printf --help - man printf.1 - info coreutils printf As of release 9.5 and the latest version in git (Thu 2024-08-08 c5725c8c4), the first two incorrectly say that octal escapes are of the form \0 or \0NNN. In fact the \0 can

bug#72568: [PATCH] printf: Fix description of %b format

2024-08-10 Thread Keith Thompson
* src/printf.c: Document that \0 can be followed by 0 to 3 octal digits * doc/coreutils.texi: Change "\0OOO" to "\0NNN" for legibility and consistency with man page and help message. Remove extraneous '\'. --- doc/coreutils.texi | 4 ++-- src/printf.c | 6 -- 2 files changed, 6 insertion

bug#72568: Acknowledgement ([PATCH] printf: Fix description of %b format)

2024-08-10 Thread Keith Thompson
I see I've inadvertently created two bug reports for the same issue, #72567 and #72568. Also, the patch I submitted doesn't mention a bug number. I presume you can resolve that on your end, but let me know if there's anything I need to do. On Sat, Aug 10, 2024 at 8:08 PM GNU bug Tracking System