All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nanno Langstraat <nlcom_os-lQF5CfOoLd8@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: New manpage for betoh64() and friends
Date: Mon, 19 Jan 2009 00:54:11 +0100	[thread overview]
Message-ID: <4973C123.9080004@ii.nl> (raw)
In-Reply-To: <cfd18e0f0901141906k539535f5nb4707d79b11f7932-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

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-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2009-01-18 23:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-08 21:50 New manpage for betoh64() and friends Nanno Langstraat
     [not found] ` <4873E122.1010504-lQF5CfOoLd8@public.gmane.org>
2008-07-08 22:22   ` Michael Kerrisk
     [not found]     ` <cfd18e0f0807081522u710a15e1wa1a513843e46ee2f-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-07-08 22:35       ` Nanno Langstraat
     [not found]         ` <4873EBB4.4030307-lQF5CfOoLd8@public.gmane.org>
2008-07-08 22:43           ` Nanno Langstraat
     [not found]             ` <4873ED78.2080303-lQF5CfOoLd8@public.gmane.org>
2009-01-13  9:13               ` Michael Kerrisk
     [not found]                 ` <cfd18e0f0901130113x605b09f6k724330d43e30dfce-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-01-14 12:12                   ` Nanno Langstraat
     [not found]                     ` <496DD6BF.2080707-lQF5CfOoLd8@public.gmane.org>
2009-01-15  3:06                       ` Michael Kerrisk
     [not found]                         ` <cfd18e0f0901141906k539535f5nb4707d79b11f7932-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-01-18 23:54                           ` Nanno Langstraat [this message]
     [not found]                             ` <4973C123.9080004-lQF5CfOoLd8@public.gmane.org>
2009-01-19  0:20                               ` Michael Kerrisk
2009-01-14 10:24   ` Michael Kerrisk
     [not found]     ` <496DBD70.2010601-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-01-19  0:09       ` Nanno Langstraat
     [not found]         ` <4973C4D6.8010902-lQF5CfOoLd8@public.gmane.org>
2009-01-19  0:28           ` Michael Kerrisk
     [not found]             ` <cfd18e0f0901181628v7d860dedw91bf4c68655e3cd8-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-01-19  0:51               ` Michael Kerrisk
     [not found]                 ` <cfd18e0f0901181651h2f9b86b4lfdad1141194b0224-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-01-20  0:00                   ` Nanno Langstraat
2009-01-19  0:53           ` Michael Kerrisk

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=4973C123.9080004@ii.nl \
    --to=nlcom_os-lqf5cfoold8@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    /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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.