On 23/05/2025 14:20, Peter Dyballa via GNU coreutils Bug Reports wrote:
Hello!
The compile used is Clang, Apple LLVM version 10.0.0 (clang-1000.11.45.5). The
CPU built into the Mac is Intel(R) Core(TM) i7-2860QM CPU @ 2.50GHz.
The error is:
mv -f src/blake2/.deps/cksum-b2sum.Tpo src/b
> Am 23.05.2025 um 16:52 schrieb Peter Dyballa :
>
> So presumingly it's not renameatu() but rather
> lib/targetdir.c:61:target_directory_operand (char const *file, struct stat
> *st) that is faulty…
In modern macOS target_directory_operand() returns -1, target_dirfd_valid(-1)
evaluates to F
Having finally managed to codesign Gdb!
On macOS Sonoma 14.7.4 (intel) mv starts as on PPC Tiger. It reaches lines #457
and #459, but "target_dirfd_valid (fd)" delivers here FALSE, deduced from the
fact that line #478 gets executed with errno presumingly 20 (on line #480 I can
print err, which
Hello!
The compile used is Clang, Apple LLVM version 10.0.0 (clang-1000.11.45.5). The
CPU built into the Mac is Intel(R) Core(TM) i7-2860QM CPU @ 2.50GHz.
The error is:
mv -f src/blake2/.deps/cksum-b2sum.Tpo src/blake2/.deps/cksum-b2sum.Po
/usr/bin/clang -I. -I./lib -DHASH_ALG
On 23/04/2025 13:22, Pádraig Brady wrote:
Older coreutils was less efficient and always called
getxattr("security.selinux"),
and thus shows the SELinux context as expected:
$ coreutils-9.3/src/ls -lZd /run/initramfs
drwxr-xr-x. 3 root root system_u:object_r:tmpfs_t:s0 60 Apr 19 14:52
/
When using Gdb I skip in mv.c's main() function over the first few calls and
come to the while loop, line #344. It is entered and
378 target_directory = optarg;.
is – visited? The name "out" contains a "t" which is also listed in the list of
command line options. After the while l
Paul,
I have a strange effect when building coreutils 9.7 with MacPorts. Yesterday I
tried to build with -O0 – and it failed! This morning I repeated it – with same
result:
/opt/local/bin/gcc-apple-4.2 -std=gnu99 -I. -I./lib -Ilib -I./lib
-Isrc -I./src -I/opt/local/include -fPIC -p
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
On 5/20/25 09:04, Torbjörn Granlund wrote:
The current factor.c code is becoming insanely complex. Contructs
masking bugs triggered on hypothetical systems doesn't help with
managing complexity.
If such hardware seems to be quite some time away, what about
guarding the code for the ranges we k
