Hi Branden,

> I bumped into this commit log message and thought it might amuse you.

Thanks for sharing =)

> Any luck re-running the command with the corrected environment variable
> name?

First of all let me say that I should've caught the LC_CALL typo, but
most of my open source / groff work happens in the evening I might not
be the most attentive after a long day, apologies.

Here's the output of the commands as requested:

/usr/bin/env LC_ALL=C printf 'Eat at the caf\351.\n' | /usr/bin/od -x
0000000      6145    2074    7461    7420    6568    6320    6661    2ee9
0000020      000a
0000021

/usr/bin/env LC_ALL=C printf 'Eat at the caf\351.\n' | /usr/bin/od -c
0000000    E   a   t       a   t       t   h   e       c   a   f 351   .
0000020   \n
0000021

In a previous email you said:
> This automated test needs to both (1) set up the locale and (2) use a
> portable incantation of printf(1).  If we can achieve that on your
> system, then I think we have a path to resolving this test failure.

So the (hopefully) good news is that while nixpkgs on Darwin uses
libSystem.dylib for its libc it does use printf from GNU's coreutils,
which seems more predictable / familiar in the context of a groff
build environment:

which printf
/nix/store/hf6y9njhfwvigr25kzrwmsvmv6jpni5n-coreutils-9.9/bin/printf

Does this help to open up a path to resolving this test failure?


Best
Alexis

Reply via email to