Thank you for the help! I tried using 8002ca7b56acb46b42eeac4a343e112a8ee283cf
and the latest commits from master and received the following errors while
running bootstrap now:
#10 154.1 Copying file m4/stdint_h.m4
#10 154.2 Copying file m4/threadlib.m4
#10 154.2 Copying file m4/uintmax_t.m4
#10
On 2021/08/17 16:00, Paul Eggert wrote:
That's different from displaying the size that would have been allocated
on a device with a block size of 1 byte. 'du' can't do what you
requested, any more than 'ls' can.
However you want to phrase it, with:
--block-size=SIZE
I want to have
On 8/17/21 3:24 AM, L A Walsh wrote:
On 2021/08/15 21:36, Paul Eggert wrote:
On 8/15/21 9:26 PM, L A Walsh wrote:
I don't want to display the allocated size on the current device,
but the size that would be allocated on a device with block-size=1-byte.
There's no practical way for 'ls' to c
On 17/08/2021 16:16, Pádraig Brady wrote:
On 17/08/2021 02:32, softwarebugreports via GNU coreutils Bug Reports wrote:
I receive the following error when using make with coreutils in a alpine based
docker container:
#10 304.5 parse-datetime.tab.c:658:10: fatal error: parse-datetime.tab.h: N
On 17/08/2021 02:32, softwarebugreports via GNU coreutils Bug Reports wrote:
I receive the following error when using make with coreutils in a alpine based
docker container:
#10 304.0 CC lib/mkdir-p.o
#10 304.1 CC lib/modechange.o
#10 304.1 CC lib/mpsort.o
#10 304.2 CC lib/nproc.o
#10 304.2 CC
On 2021/08/15 21:36, Paul Eggert wrote:
On 8/15/21 9:26 PM, L A Walsh wrote:
I don't want to display the allocated size on the current device,
but the size that would be allocated on a device with block-size=1-byte.
There's no practical way for 'ls' to calculate that, as the kernel
doesn't
On Tue, Aug 17, 2021 at 2:02 AM Pádraig Brady wrote:
> On 16/08/2021 22:17, Assaf Gordon wrote:
> > Hello Emil and all,
> >
> > Thanks for the clear and easily reproducible bug report.
> >
> > Attached a suggested fix.
> > Comments very welcomed,
>
> minor nit in NEWS:
> s/silently discard/silentl
