On 3/6/20 2:48 AM, Pádraig Brady wrote:
I'm not very attached to the new behavior so feel free to apply this.
As per the original discussion, the change was made to distinguish
unreachable directories from empty directories.
Unreachable dirs are not common, but it seems useful for the user
to kn
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 00:00:0
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 error
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: 'SYS_g
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 erro
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 reachab
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 dire
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 i
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'?
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 (SYS_getdents
10 matches
Mail list logo
