The programs that can be built with this package are:
- [ base64 basename cat chgrp chmod chown chroot cksum comm cp csplit cut date
- dd df dir dircolors dirname du echo env expand expr factor false fmt fold
- ginstall groups head hostid hostname id join kill link ln logname ls
- md5sum mkdir mkfifo mknod mv nice nl nohup od paste pathchk pinky pr
- printenv printf ptx pwd readlink rm rmdir seq sha1sum sha224sum sha256sum
- sha384sum sha512sum shred shuf sleep sort split stat stty su sum sync tac
- tail tee test touch tr true tsort tty uname unexpand uniq unlink uptime
- users vdir wc who whoami yes
+ [ arch base64 basename cat chcon chgrp chmod chown chroot cksum comm cp
+ csplit cut date dd df dir dircolors dirname du echo env expand expr
+ factor false fmt fold groups head hostid hostname id install join kill
+ link ln logname ls md5sum mkdir mkfifo mknod mktemp mv nice nl nohup
+ od paste pathchk pinky pr printenv printf ptx pwd readlink rm rmdir
+ runcon seq sha1sum sha224sum sha256sum sha384sum sha512sum shred shuf
+ sleep sort split stat stty su sum sync tac tail tee test timeout touch tr
+ true truncate tsort tty uname unexpand uniq unlink uptime users vdir wc who
+ whoami yes
See the file NEWS for a list of major changes in the current release.
-See the file INSTALL for compilation and installation instructions.
+If you obtained this file as part of a "git clone", then see the
+README-hacking file. If this file came to you as part of a tar archive,
+then see the file INSTALL for compilation and installation instructions.
These programs are intended to conform to POSIX (with BSD and other
extensions), like the rest of the GNU system. By default they conform
files (man/*.x) are welcome. However, the authoritative documentation
is in texinfo form in the doc directory.
-If you run the tests on a SunOS4.1.4 system, expect the ctime-part of
-the ls `time-1' test to fail. I believe that is due to a bug in the
-way Sun implemented link(2) and chmod(2).
+
+*****************************************
+On Mac OS X 10.5.1 (Darwin 9.1), test failure
+-----------------------------------------
+
+Mac OS X 10.5.1 (Darwin 9.1) provides only partial (and incompatible)
+ACL support, so although "./configure && make" succeeds, "make check"
+exposes numerous failures. The solution is to turn off ACL support
+manually via "./configure --disable-acl". For details, see
+<http://thread.gmane.org/gmane.comp.gnu.coreutils.bugs/12292/focus=12318>.
+
+
+*****************************************
+Test failure with NLS and gettext <= 0.17
+-----------------------------------------
+
+Due to a conflict between libintl.h and gnulib's new xprintf module,
+when you configure with NLS support, and with a gettext installation
+older than 0.17.1 (not yet released, at the time of this writing),
+then some tests fail, at least on NetBSD 1.6. To work around it in
+the mean time, you can configure with --disable-nls. For details,
+see <http://thread.gmane.org/gmane.comp.lib.gnulib.bugs/12015/>.
***********************
+#ifndef __LP64__
+************************
+OSF/1 4.0d build failure
+------------------------
+
+If you use /usr/bin/make on an OSF/1 4.0d system, it will fail due
+to the presence of the "[" target. That version of make appears to
+treat "[" as some syntax relating to locks. To work around that,
+the best solution is to use GNU make. Otherwise, simply remove
+all mention of "[$(EXEEXT)" from src/Makefile.
+
+
+
**********************
Running tests as root:
----------------------
user, and then to run the following command as that user in order
to run the privilege-requiring tests:
- sudo env NON_ROOT_USERNAME=$USER make -k check
+ sudo env PATH="$PATH" NON_ROOT_USERNAME=$USER make -k check-root
If you can run the tests as root, please do so and report any
problems. We get much less test coverage in that mode, and it's
received any acknowledgement, please ping us. A complete patch includes
a well-written ChangeLog entry, unified (diff -u format) diffs relative
to the most recent test release (or, better, relative to the latest
-sources in the CVS repository), an explanation for why the patch is
+sources in the public repository), an explanation for why the patch is
necessary or useful, and if at all possible, enough information to
reproduce whatever problem prompted it. Plus, you'll earn lots of
karma if you include a test case to exercise any bug(s) you fix.
-Instructions for checking out the latest source via CVS are here:
-
- http://savannah.gnu.org/cvs/?group=coreutils
+Here are instructions for checking out the latest development sources:
+ http://savannah.gnu.org/git/?group=coreutils
If your patch adds a new feature, please try to get some sort of consensus
that it is a worthwhile change. One way to do that is to send mail to
projects / platform / upstream / coreutils.git / blobdiff