GNU bug report logs - #78509
Coreutils' mv and cp 9.5 do not work properly on old PPC Mac OS X 10.4.11, Tiger

Previous Next

Full log

Message #56 received at 78509 <at> debbugs.gnu.org (full text, mbox):

From: Peter Dyballa <Peter_Dyballa <at> Web.DE>
To: Pádraig Brady <P <at> draigBrady.com>
Cc: 78509 <at> debbugs.gnu.org
Subject: Re: bug#78509: Coreutils' mv and cp 9.5 do not work properly on old
 PPC Mac OS X 10.4.11, Tiger
Date: Fri, 23 May 2025 10:03:40 +0200

[Message part 1 (text/plain, inline)]

Hello Pádraig!

Yesterday coreutils did not build because of use of -O0 instead of -Os before. This morning I am using simply -O, and the tests stop at the test after existing-perm-dir.sh (last line in build log), which is existing-perm-race.sh.

coreutils-9.7/tests/cp has:

	-rw-r--r-- 1 macports admin  6687 23. Mai 09:03 existing-perm-race.log
	-rw-r--r-- 1 macports admin  6194 23. Mai 09:03 existing-perm-dir.log
	-rw-r--r-- 1 macports admin    82 23. Mai 09:03 existing-perm-dir.trs
	-rw-r--r-- 1 macports admin  6004 23. Mai 09:03 dir-vs-file.log
	-rw-r--r-- 1 macports admin    82 23. Mai 09:03 dir-vs-file.trs
	...
	-rw-r--r-- 1 macports admin  7745 23. Mai 08:40 link-heap.log
	-rw-r--r-- 1 macports admin    83 23. Mai 08:40 link-heap.trs
	-rwxr-xr-x 1 macports admin  2882 23. Mai 08:21 existing-perm-race.sh
	-rwxr-xr-x 1 macports admin  1736 23. Mai 08:21 file-perm-race.sh
	-rwxr-xr-x 1 macports admin  1406 20. Jan 16:16 symlink-slash.sh
	-rwxr-xr-x 1 macports admin  3477  7. Jan 18:31 cp-i.sh
	-rwxr-xr-x 1 macports admin  1639  7. Jan 13:36 abuse.sh

which indicates that existing-perm-race.sh and file-perm-race.sh have been patched, as the compile log also indicates:

	patch phase started at Fri May 23 08:21:43 CEST 2025
	Executing org.macports.patch (coreutils-devel)
	--->  Applying patches to coreutils-devel
	--->  Applying patch-tests_cp_existing-perm-race.sh.diff



I observed an unpleasant behaviour of 'make check': When it's killed coreutils-9.7/tests/cp/existing-perm-race.log just vanishes. Is there a way to keep that "unfinished" log file, in order to find in it a possible clue for some misbehaviour?

The test log contains a complaint (?) about not knowing the local file systems – they are:

	Filesystem     Type  1K-blocks     Used Available Use% Mounted on
	/dev/disk0s7   hfs    53515952 42970824  10289128  81% /
	devfs          devfs         1        1         0 100% /dev
	fdesc          fdesc         1        1         0 100% /dev
	<volfs>        volfs       512      512         0 100% /.vol
	/dev/disk0s3   hfs    18852212 14069028   4783184  75% /Volumes/BSD-Linux
	/dev/disk0s5   hfs    65678668 57482724   8195944  88% /Volumes/Leopard
	/dev/disk0s9   hfs    17719744 15903256   1816488  90% /Volumes/Halde

See attached existing-perm-race.log and patched existing-perm-race.sh!

--

Greetings

  Pete

"When you breathe, you inspire. When you do not breathe, you expire."

[existing-perm-race.log (application/octet-stream, attachment)]

[existing-perm-race.sh (application/octet-stream, attachment)]

[Message part 4 (text/plain, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.