coreutils/m4, branch v8.5Mirror of https://https.git.savannah.gnu.org/git/coreutils.git/
https://git.shady.money/coreutils/atom?h=v8.52010-04-06T14:02:27Zmaint: fix a masked syntax-check violation2010-04-06T14:02:27ZJim Meyeringmeyering@redhat.com2010-04-06T14:01:32Zurn:sha1:f267926f2d3e51756a21b772b017f698c0a10f41
* m4/jm-macros.m4 (ARGMATCH_DIE): Use usage(EXIT_FAILURE), not usage(1).
* .x-sc_prohibit_magic_number_exit: Remove *.m4 exemption that was
masking the above.
sort: inform the system about our input access pattern2010-03-04T10:42:00ZJoey Deggesjdegges@gmail.com2010-03-01T10:26:22Zurn:sha1:dae35bac98520c1402d29c60df11a2993889ec85
Tell the system that we'll access input sequentially,
so that we more efficiently process uncached files in a few cases:
Reading from faster flash devices. E.g. 21 MB/s key:
NORMAL 31.6s (26.8 user)
SEQUENTIAL 27.7s
WILLNEED 27.7s
Processing in parallel with readahead when using a small 1M buffer:
NORMAL 24.7s (21.1 user)
SEQUENTIAL 22.7s
WILLNEED 25.6s
A small benefit when merging:
NORMAL 25.0s (16.9 user)
SEQUENTIAL 24.6s (16.6 user)
WILLNEED 38.4s (13.1 user)
Note WILLNEED is presented above for comparison to show it
has some unwanted characteristics due to its synchronous
prepopulation of the cache. It has a good benefit on a
mechanical disk @ 80MB/s and a multicore system with
competing processes:
NORMAL 14.73s
SEQUENTIAL 10.95s
WILLNEED 05.22s
However the scheduling differences causing this result
are probably best explicitly managed using `nice` etc.
* m4/jm-macros.m4 (coreutils_MACROS): check for posix_fadvise().
* src/sort.c (fadvise_input): A new function to apply
the POSIX_FADV_SEQUENTIAL hint to an input stream.
(stream_open): Call the above function for all input streams.
who --mesg (-T) can use a more accurate test for TTY writability2010-01-25T10:43:49ZKamil Dudkakdudka@redhat.com2010-01-22T14:17:19Zurn:sha1:aad0bde0b5aa6ccf2714f43676d4941f820c6283
Enabled when coreutils is configured with --with-tty-group.
Based on a patch written by Piotr Gackiewicz. Details at
http://bugzilla.redhat.com/454261
* src/who.c (is_tty_writable): A new function returning true if a TTY
device is writable by the group. Additionally it checks the group to be
the same as TTY_GROUP_NAME when compiled with --with-tty-group.
* m4/jm-macros.m4: Introduce a new configure option --with-tty-group.
* NEWS: Mention the change.
build: fix failure from bogus USE_XATTR definition2010-01-19T13:41:57ZEric Blakeebb9@byu.net2010-01-16T13:46:17Zurn:sha1:e489fd04d66000829f5458843970794eccacced8
* m4/xattr.m4 (gl_FUNC_ADDR): Fix regression introduced in commit
6beca4248.
* THANKS: Update.
Reported by Adam Sampson.
build: fix build failure due to missing libxattr2010-01-12T07:06:47ZJim Meyeringmeyering@redhat.com2010-01-12T06:58:44Zurn:sha1:6beca4248f572c2503657fb16341bd43cfa7d254
Configure is supposed to detect insufficient XATTR support.
However, if a system has the required headers, but no library,
the configure script would mistakenly enable USE_XATTR.
* m4/xattr.m4 (gl_FUNC_XATTR): If the attr_copy_file function
is not found, don't set USE_XATTR.
Nelson Beebe reported a link failure on RHEL 5.3.
Also, do not let the combination of --disable-xattr and
a stray LIB_XATTR environment setting perturb the build.
* NEWS (Build-related): Mention it.
maint: update all FSF copyright year lists to include 20102010-01-01T13:06:47ZJim Meyeringmeyering@redhat.com2010-01-01T09:56:28Zurn:sha1:1aa17dc89b3f313697661541adca0aa0defbdc09
Use this command:
git ls-files | grep -v COPYING \
| xargs env UPDATE_COPYRIGHT_USE_INTERVALS=1 \
build-aux/update-copyright
maint: issue warnings for more missing optional libraries2009-10-20T16:11:00ZPádraig BradyP@draigBrady.com2009-10-19T10:12:40Zurn:sha1:71adb516deee94274669f968636194bf261b1207
* README-hacking: Suggest to use ./configure --quiet so that
any warnings are easily noticed.
* m4/gmp.m4 (cu_GMP): Warn if libgmp is not available.
* m4/jm-macros.m4 (coreutils_MACROS): Normalize the libcap warning.
* m4/xattr.m4 (gl_FUNC_XATTR): Warn if libattr is not available.
build: use gnulib's isblank module2009-10-19T05:57:15ZJim Meyeringmeyering@redhat.com2009-10-19T05:55:42Zurn:sha1:6ac6c7e4b77898d6d82d5565b5d8b053ecacbc64
* bootstrap.conf (gnulib_modules): Add isblank.
* src/system.h (isblank): Don't define.
* m4/check-decl.m4: Don't check for isblank declaration.
* gnulib: Update submodule to latest.
build: don't let environment settings perturb build2009-10-15T19:03:40ZJim Meyeringmeyering@vm.meyering.net.localdomain2009-10-15T18:54:02Zurn:sha1:2fa407885c5fbcbcf92ef640859440b896d3c6b1
Setting the envvars, LIB_FDATASYNC, LIB_XATTR or LIB_CRYPT
could cause a configure-time and/or build-time malfunction.
Typically, a configure-time function-in-library test is performed
via code like this:
LIB_VAR=
AC_SUBST([LIB_VAR])
prefix_saved_LIBS=$LIBS
AC_SEARCH_LIBS([FUNC], [LIB_NAME],
[test "$ac_cv_search_FUNC" = "none required" ||
LIB_VAR=$ac_cv_search_FUNC])
LIBS=$prefix_saved_LIBS
However, in each of the files affected by this change, the LIB_VAR=
initialization was omitted. Thus, when set in the environment, its
value would propagate into generated Makefiles when FUNC is not found
in LIB_NAME.
* m4/jm-macros.m4 (coreutils_MACROS): Initialize AC_SUBST'd var
* m4/lib-check.m4 (cu_LIB_CHECK): Likewise.
* m4/xattr.m4 (gl_FUNC_XATTR): Likewise.
copy: allow symlink timestamp preservation on more systems2009-10-10T21:16:52ZEric Blakeebb9@byu.net2009-10-08T21:57:06Zurn:sha1:7280a913a12ebfe33e8cad1b217b84944bbd3681
* src/copy.c (utimens_symlink): Simplify by using lutimens.
* m4/jm-macros.m4 (coreutils_MACROS): Drop utimensat; gnulib does
this for us.
* tests/cp/preserve-slink-time: Recognize lutimes support.