From afbd32c040538f83af18579da5a887e8b3f95257 Mon Sep 17 00:00:00 2001 From: Jim Meyering Date: Fri, 25 Jul 2003 07:23:40 +0000 Subject: [PATCH] Disable the --line-bytes=$_4gb test, because it'd evoke spurious failure on 64-bit systems. --- tests/misc/split-fail | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/tests/misc/split-fail b/tests/misc/split-fail index 247f4d4751..e1a1820b23 100755 --- a/tests/misc/split-fail +++ b/tests/misc/split-fail @@ -42,9 +42,11 @@ split --lines=$_4gb in || fail=1 split --bytes=$_4gb in || fail=1 # Currently (coreutils-5.0.1) split --line-bytes=M fails -# with `invalid number of bytes' for M=2^32 or larger. Test it. -# Of course, this is an artificial limit and should be fixed. -split --line-bytes=$_4gb 2> /dev/null in && fail=1 +# with `invalid number of bytes' for M=2^32 or larger. Actually, +# the limit is SIZE_MAX, which is 2^32 on 32-bit systems. +# On 64-bit systems, there's no problem with a count of 2^32, +# So disable this test in order to avoid the `failure' on 64-bit systems. +#split --line-bytes=$_4gb 2> /dev/null in && fail=1 # Make sure that a huge obsolete option evokes the right failure. env -u _POSIX2_VERSION split -99999999999999999991 2> out && fail=1 -- 2.47.2