bug#39929: coreutils-8.32 fails to build on aarch64

2020-03-07 Thread Paul Eggert
On 3/5/20 11:36 PM, Bernhard Voelker wrote: s/emits/shall not emit/ P.S. Also the check for $host_triplet containing 'linux' in test is: a) no longer needed, ... Thanks for catching those; I installed the attached further patch. >From ab149bd415daf1cb8ecde0b948bc0a2663611a61 Mon Sep 17

bug#39929: coreutils-8.32 fails to build on aarch64

2020-03-06 Thread Pádraig Brady
On 05/03/2020 21:43, Paul Eggert wrote: On 3/5/20 9:39 AM, Pádraig Brady wrote: Ah well. Does the attached address this for you. Eeeuw. Why is this code even there at all? If readdir(3) says that the current directory has no entries, shouldn't 'ls' just say that? Why should ls report an

bug#39929: coreutils-8.32 fails to build on aarch64

2020-03-06 Thread Kamil Dudka
On Thursday, March 5, 2020 6:39:23 PM CET Pádraig Brady wrote: > On 05/03/2020 16:21, Kamil Dudka wrote: > > While trying to build coreutils-8.32 for Fedora on aarch64, I got the > > following compilation failure: > > > > ../src/ls.c: In function 'print_dir': > > ../src/ls.c:3026:24: error:

bug#39929: coreutils-8.32 fails to build on aarch64

2020-03-05 Thread Bernhard Voelker
On 2020-03-06 08:31, Bernhard Voelker wrote: > On 2020-03-06 02:27, Paul Eggert wrote: >> On 3/5/20 1:43 PM, Paul Eggert wrote: >> >>> Why is this code even there at all? If readdir(3) says that the current >>> directory has no entries, shouldn't 'ls' just say that? Why should ls >>> report an

bug#39929: coreutils-8.32 fails to build on aarch64

2020-03-05 Thread Bernhard Voelker
On 2020-03-06 02:27, Paul Eggert wrote: > On 3/5/20 1:43 PM, Paul Eggert wrote: > >> Why is this code even there at all? If readdir(3) says that the current >> directory has no entries, shouldn't 'ls' just say that? Why should ls >> report an error simply because the current directory isn't

bug#39929: coreutils-8.32 fails to build on aarch64

2020-03-05 Thread Paul Eggert
On 3/5/20 1:43 PM, Paul Eggert wrote: Why is this code even there at all? If readdir(3) says that the current directory has no entries, shouldn't 'ls' just say that? Why should ls report an error simply because the current directory isn't reachable from the filesystem? Whether the current

bug#39929: coreutils-8.32 fails to build on aarch64

2020-03-05 Thread Paul Eggert
On 3/5/20 9:39 AM, Pádraig Brady wrote: Ah well. Does the attached address this for you. Eeeuw. Why is this code even there at all? If readdir(3) says that the current directory has no entries, shouldn't 'ls' just say that? Why should ls report an error simply because the current directory

bug#39929: coreutils-8.32 fails to build on aarch64

2020-03-05 Thread Pádraig Brady
On 05/03/2020 16:21, Kamil Dudka wrote: While trying to build coreutils-8.32 for Fedora on aarch64, I got the following compilation failure: ../src/ls.c: In function 'print_dir': ../src/ls.c:3026:24: error: 'SYS_getdents' undeclared (first use in this function); did you mean 'SYS_getdents64'?

bug#39929: coreutils-8.32 fails to build on aarch64

2020-03-05 Thread Kamil Dudka
While trying to build coreutils-8.32 for Fedora on aarch64, I got the following compilation failure: ../src/ls.c: In function 'print_dir': ../src/ls.c:3026:24: error: 'SYS_getdents' undeclared (first use in this function); did you mean 'SYS_getdents64'? 3026 | if (syscall