Michael Kerrisk wrote:
> I spoke too soon. I'd gone back and looked at your initial mail, seen
> mention of "betoh64" as one of the required link names, grepped for
> that in the glibc headers, and hadn't found it. But that name is
> wrong, I think you meant "be64toh". And indeed these interfaces are
> present in glibc 2.9.
>
Ah, I see.
I'm very sorry for all the confusion that this one manpage has cost you.
My simple aim was: to get a standard set of htobe64() / betoh64() etc.
macros on all platforms
(OpenBSD, Linux, FreeBSD; and hopefully outward from there).
End result: complete failure.
* OpenBSD wasn't willing to adopt <endian.h> instead of
<sys/endian.h> for userspace apps.
(would accomodate glibc: glibc makes a sharper distinction between
kernel API vs. userspace C library than the *BSDs do)
* glibc's Ulrich Drepper evidently chose to use his own naming
scheme (be64toh), instead of adopting the original OpenBSD scheme
(betoh64).
* FreeBSD didn't have much interest altogether.
So, I clearly didn't hit the right notes to interest anybody in adopting
a standard.
I hope that this at least explains the situation & our grep confusion.
With regards,
Nanno
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
