Home | History | Annotate | only in /sfw/usr/src/cmd/coreutils/coreutils-7.4
Up to higher level directory
NameDateSize
.prev-version03-May-20094
.tarball-version07-May-20094
.version07-May-20094
.vg-suppressions27-Feb-20091.9K
.x-sc_file_system18-Sep-200851
.x-sc_GPL_version18-Sep-200822
.x-sc_obsolete_symbols18-Sep-200810
.x-sc_po_check27-Jan-20095
.x-sc_program_name18-Sep-200839
.x-sc_prohibit_atoi_atof02-Mar-200925
.x-sc_prohibit_stat_st_blocks12-Oct-200869
.x-sc_prohibit_strcmp27-Jan-200910
.x-sc_require_config_h27-Jan-2009160
.x-sc_space_tab18-Sep-2008151
.x-sc_sun_os_names18-Sep-200834
.x-sc_trailing_blank18-Sep-200811
.x-sc_unmarked_diagnostics18-Sep-200834
.x-sc_useless_cpp_parens18-Sep-2008212
ABOUT-NLS18-Sep-200878.7K
aclocal.m407-May-200945.8K
AUTHORS24-Apr-20093.5K
bootstrap29-Apr-200921.1K
bootstrap.conf04-May-20095.5K
build-aux/07-May-2009
cfg.mk03-May-20096.9K
ChangeLog07-May-2009247.6K
ChangeLog-200527-Feb-2009438.4K
ChangeLog-200627-Feb-2009149.8K
ChangeLog-200727-Feb-2009154.9K
ChangeLog-200827-Feb-200913.4K
configure07-May-20091.1M
configure.ac24-Apr-200914.2K
COPYING27-Feb-200934.3K
dist-check.mk03-May-20094.8K
doc/07-May-2009
gl/07-May-2009
gnulib-tests/07-May-2009
GNUmakefile15-Mar-20094.6K
INSTALL04-May-200911.6K
lib/07-May-2009
m4/07-May-2009
maint.mk04-May-200927.1K
Makefile.am03-May-20094.3K
Makefile.in07-May-200953.8K
man/07-May-2009
NEWS07-May-2009102.9K
old/07-May-2009
po/07-May-2009
README02-May-200910.4K
src/07-May-2009
tests/07-May-2009
THANKS04-May-200933.5K
THANKS-to-translators07-May-20091.6K
THANKStt.in18-Sep-2008121
TODO04-May-20097.5K

README

      1 These are the GNU core utilities.  This package is the union of
      2 the GNU fileutils, sh-utils, and textutils packages.
      3 
      4 Most of these programs have significant advantages over their Unix
      5 counterparts, such as greater speed, additional options, and fewer
      6 arbitrary limits.
      7 
      8 The programs that can be built with this package are:
      9 
     10   [ arch base64 basename cat chcon chgrp chmod chown chroot cksum comm cp
     11   csplit cut date dd df dir dircolors dirname du echo env expand expr
     12   factor false fmt fold groups head hostid hostname id install join kill
     13   link ln logname ls md5sum mkdir mkfifo mknod mktemp mv nice nl nohup
     14   od paste pathchk pinky pr printenv printf ptx pwd readlink rm rmdir
     15   runcon seq sha1sum sha224sum sha256sum sha384sum sha512sum shred shuf
     16   sleep sort split stat stty su sum sync tac tail tee test timeout touch tr
     17   true truncate tsort tty uname unexpand uniq unlink uptime users vdir wc who
     18   whoami yes
     19 
     20 See the file NEWS for a list of major changes in the current release.
     21 
     22 If you obtained this file as part of a "git clone", then see the
     23 README-hacking file.  If this file came to you as part of a tar archive,
     24 then see the file INSTALL for compilation and installation instructions.
     25 
     26 These programs are intended to conform to POSIX (with BSD and other
     27 extensions), like the rest of the GNU system.  By default they conform
     28 to older POSIX (1003.2-1992), and therefore support obsolete usages
     29 like "head -10" and "chown owner.group file".  This default is
     30 overridden at build-time by the value of <unistd.h>'s _POSIX2_VERSION
     31 macro, and this in turn can be overridden at runtime as described in
     32 the documentation under "Standards conformance".
     33 
     34 The ls, dir, and vdir commands are all separate executables instead of
     35 one program that checks argv[0] because people often rename these
     36 programs to things like gls, gnuls, l, etc.  Renaming a program
     37 file shouldn't affect how it operates, so that people can get the
     38 behavior they want with whatever name they want.
     39 
     40 Special thanks to Paul Eggert, Brian Matthews, Bruce Evans, Karl Berry,
     41 Kaveh Ghazi, and Franois Pinard for help with debugging and porting
     42 these programs.  Many thanks to all of the people who have taken the
     43 time to submit problem reports and fixes.  All contributed changes are
     44 attributed in the commit logs.
     45 
     46 And thanks to the following people who have provided accounts for
     47 portability testing on many different types of systems: Bob Proulx,
     48 Christian Robert, Franois Pinard, Greg McGary, Harlan Stenn,
     49 Joel N. Weber, Mark D. Roth, Matt Schalit, Nelson H. F. Beebe,
     50 Rjean Payette, Sam Tardieu.
     51 
     52 Thanks to Michael Stone for inflicting test releases of this package
     53 on Debian's unstable distribution, and to all the kind folks who used
     54 that distribution and found and reported bugs.
     55 
     56 Note that each man page is now automatically generated from a template
     57 and from the corresponding --help usage message.  Patches to the template
     58 files (man/*.x) are welcome.  However, the authoritative documentation
     59 is in texinfo form in the doc directory.
     60 
     61 
     62 *****************************************
     63 On Mac OS X 10.5.1 (Darwin 9.1), test failure
     64 -----------------------------------------
     65 
     66 Mac OS X 10.5.1 (Darwin 9.1) provides only partial (and incompatible)
     67 ACL support, so although "./configure && make" succeeds, "make check"
     68 exposes numerous failures.  The solution is to turn off ACL support
     69 manually via "./configure --disable-acl".  For details, see
     70 <http://thread.gmane.org/gmane.comp.gnu.coreutils.bugs/12292/focus=12318>.
     71 
     72 
     73 *****************************************
     74 Test failure with NLS and gettext <= 0.17
     75 -----------------------------------------
     76 
     77 Due to a conflict between libintl.h and gnulib's new xprintf module,
     78 when you configure with NLS support, and with a gettext installation
     79 older than 0.17.1 (not yet released, at the time of this writing),
     80 then some tests fail, at least on NetBSD 1.6.  To work around it in
     81 the mean time, you can configure with --disable-nls.  For details,
     82 see <http://thread.gmane.org/gmane.comp.lib.gnulib.bugs/12015/>.
     83 
     84 
     85 ***********************
     86 Pre-C99 build failure
     87 -----------------------
     88 
     89 There is a new, implicit build requirement:
     90 To build the coreutils from source, you should have a C99-conforming
     91 compiler, due to the use of declarations after non-declaration statements
     92 in several files in src/.  There is code in configure to find and, if
     93 possible, enable an appropriate compiler.  However, if configure doesn't
     94 find a C99 compiler, it continues nonetheless, and your build will fail.
     95 If that happens, simply[*] apply the included patch using the following
     96 command, and then run make again:
     97 
     98   cd src && patch < c99-to-c89.diff
     99 
    100 [*] however, as of coreutils-7.1, the "c99-to-c89.diff" file is no longer
    101 maintained, so even if the patches still apply, the result will be an
    102 incomplete conversion.  It's been 10 years.  Get a decent compiler! ;-)
    103 
    104 
    105 ***********************
    106 HPUX 11.x build failure
    107 -----------------------
    108 
    109 A known problem exists when compiling on HPUX on both hppa and ia64
    110 in 64-bit mode (i.e. +DD64) on HP-UX 11.0, 11.11, and 11.23.  This
    111 is not due to a bug in the package but instead due to a bug in the
    112 system header file which breaks things in 64-bit mode.  The default
    113 compilation mode is 32-bit and the software compiles fine using the
    114 default mode.  To build this software in 64-bit mode you will need
    115 to fix the system /usr/include/inttypes.h header file.  After
    116 correcting that file the software also compiles fine in 64-bit mode.
    117 Here is one possible patch to correct the problem:
    118 
    119 --- /usr/include/inttypes.h.orig	Thu May 30 01:00:00 1996
    120 +++ /usr/include/inttypes.h	Sun Mar 23 00:20:36 2003
    121 @@ -489 +489 @@
    122 -#ifndef __STDC_32_MODE__
    123 +#ifndef __LP64__
    124 
    125 
    126 ************************
    127 OSF/1 4.0d build failure
    128 ------------------------
    129 
    130 If you use /usr/bin/make on an OSF/1 4.0d system, it will fail due
    131 to the presence of the "[" target.  That version of make appears to
    132 treat "[" as some syntax relating to locks.  To work around that,
    133 the best solution is to use GNU make.  Otherwise, simply remove
    134 all mention of "[$(EXEEXT)" from src/Makefile.
    135 
    136 
    137 
    138 **********************
    139 Running tests as root:
    140 ----------------------
    141 
    142 If you run the tests as root, note that a few of them create files
    143 and/or run programs as a non-root user, `nobody' by default.
    144 If you want to use some other non-root username, specify it via
    145 the NON_ROOT_USERNAME environment variable.  Depending on the
    146 permissions with which the working directories have been created,
    147 using `nobody' may fail, because that user won't have the required
    148 read and write access to the build and test directories.
    149 I find that it is best to unpack and build as a non-privileged
    150 user, and then to run the following command as that user in order
    151 to run the privilege-requiring tests:
    152 
    153   sudo env PATH="$PATH" NON_ROOT_USERNAME=$USER make -k check-root
    154 
    155 If you can run the tests as root, please do so and report any
    156 problems.  We get much less test coverage in that mode, and it's
    157 arguably more important that these tools work well when run by
    158 root than when run by less privileged users.
    159 
    160 
    161 ***************
    162 Reporting bugs:
    163 ---------------
    164 
    165 IMPORTANT: if you take the time to report a test failure,
    166 please be sure to include the output of running `make check'
    167 in verbose mode for each failing test.  For example,
    168 if the test that fails is tests/misc/df, then you would
    169 run this command:
    170 
    171   (cd tests && make check TESTS=misc/df VERBOSE=yes) >> log 2>&1
    172 
    173 For some tests, you can get even more detail by adding DEBUG=yes.
    174 Then include the contents of the file `log' in your bug report.
    175 
    176 Send bug reports, questions, comments, etc. to bug-coreutils (a] gnu.org.
    177 If you would like to suggest a patch, see the files README-hacking
    178 and HACKING for tips.
    179 
    180 ***************************************
    181 
    182 There are many tests, but nowhere near as many as we need.
    183 Additions and corrections are very welcome.
    184 
    185 If you see a problem that you've already reported, feel free to re-report
    186 it -- it won't bother me to get a reminder.  Besides, the more messages I
    187 get regarding a particular problem the sooner it'll be fixed -- usually.
    188 If you sent a complete patch and, after a couple weeks you haven't
    189 received any acknowledgement, please ping us.  A complete patch includes
    190 a well-written ChangeLog entry, unified (diff -u format) diffs relative
    191 to the most recent test release (or, better, relative to the latest
    192 sources in the public repository), an explanation for why the patch is
    193 necessary or useful, and if at all possible, enough information to
    194 reproduce whatever problem prompted it.  Plus, you'll earn lots of
    195 karma if you include a test case to exercise any bug(s) you fix.
    196 Here are instructions for checking out the latest development sources:
    197 
    198   http://savannah.gnu.org/git/?group=coreutils
    199 
    200 If your patch adds a new feature, please try to get some sort of consensus
    201 that it is a worthwhile change.  One way to do that is to send mail to
    202 bug-coreutils (a] gnu.org including as much description and justification
    203 as you can.  Based on the feedback that generates, you may be able to
    204 convince us that it's worth adding.
    205 
    206 
    207 WARNING:  Now that we use the ./bootstrap script, you should not run
    208 autoreconf manually.  Doing that will overwrite essential source files
    209 with older versions, which may make the package unbuildable or introduce
    210 subtle bugs.
    211 
    212 
    213 WARNING:  If you modify files like configure.in, m4/*.m4, aclocal.m4,
    214 or any Makefile.am, then don't be surprised if what gets regenerated no
    215 longer works.  To make things work, you'll have to be using appropriate
    216 versions of the tools listed in bootstrap.conf's buildreq string.
    217 
    218 All of these programs except `test' recognize the `--version' option.
    219 When reporting bugs, please include in the subject line both the package
    220 name/version and the name of the program for which you found a problem.
    221 
    222 For general documentation on the coding and usage standards
    223 this distribution follows, see the GNU Coding Standards,
    224 http://www.gnu.org/prep/standards_toc.html.
    225 
    226 Mail suggestions and bug reports for these programs to
    227 the address on the last line of --help output.
    228 
    229 
    230 ========================================================================
    231 
    232 Copyright (C) 1998, 2002-2009 Free Software Foundation, Inc.
    233 
    234 Permission is granted to copy, distribute and/or modify this document
    235 under the terms of the GNU Free Documentation License, Version 1.2 or
    236 any later version published by the Free Software Foundation; with no
    237 Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
    238 Texts.  A copy of the license is included in the ``GNU Free
    239 Documentation License'' file as part of this distribution.
    240