From: Alec Salazar <alec.j.salazar@gmail.com>
To: musl@lists.openwall.com
Subject: Re: XPG4
Date: Thu, 14 Aug 2014 19:28:53 -0400 [thread overview]
Message-ID: <CAL1O-RzifARrJkvYM5UZyw353SOkJ_KbtEN_2R3BhoGPL1-d7A@mail.gmail.com> (raw)
In-Reply-To: <20140814194632.GK12888@brightrain.aerifal.cx>
[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]
I seem to be taking a wrong turn somewhere. Running find . -type f -print0
| xargs -0 /bin/grep D_FMT in /usr/include for the installed 1.1.4 yields:
./langinfo.h:#define D_FMT 0x20029
./langinfo.h:#define ERA_D_FMT 0x2002E
Pulling the latest sources and running the same command in gitdir yields:
./src/time/strptime.c: s = strptime(s, nl_langinfo(D_FMT),
tm);
./src/time/strftime.c: item = D_FMT;
./include/langinfo.h:#define D_FMT 0x20029
./include/langinfo.h:#define ERA_D_FMT 0x2002E
Neither directory yields a result for DATE_FMT. Am I botching the unix-fu,
barking up the wrong tree or something else entirely?
On Thu, Aug 14, 2014 at 3:46 PM, Rich Felker <dalias@libc.org> wrote:
> On Thu, Aug 14, 2014 at 03:31:23PM -0400, Alec Salazar wrote:
> > Is there any interest or plan to support the xopen xpg4 standard? My
> > specific interest is regarding zfs on linux. There is a function call
> > nl_langinfo(_DATE_FMT). Apparently this nl item was added in xpg4. I'm
> > wondering what the possibility is of a long-term solution.
>
> _DATE_FMT is just an incorrect or obsolete spelling for DATE_FMT. The
> latter is standard and is supported by musl.
>
> Rich
>
[-- Attachment #2: Type: text/html, Size: 1730 bytes --]
next prev parent reply other threads:[~2014-08-14 23:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-14 19:31 XPG4 Alec Salazar
2014-08-14 19:46 ` XPG4 Rich Felker
2014-08-14 23:28 ` Alec Salazar [this message]
2014-08-14 23:40 ` XPG4 Rich Felker
2014-08-14 23:48 ` XPG4 Alec Salazar
2014-08-15 0:42 ` XPG4 Isaac Dunham
2014-08-15 0:56 ` XPG4 Alec Salazar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAL1O-RzifARrJkvYM5UZyw353SOkJ_KbtEN_2R3BhoGPL1-d7A@mail.gmail.com \
--to=alec.j.salazar@gmail.com \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).