From: "Anthony J. Bentley" <anthony@anjbe.name>
Cc: tech@mdocml.bsd.lv
Subject: Re: Mac OS X patch
Date: Fri, 24 Jul 2015 03:48:27 -0600 [thread overview]
Message-ID: <12235.1437731307@CATHET.us> (raw)
In-Reply-To: <12372.1437731064@CATHET.us>
"Anthony J. Bentley" writes:
> Hi Kristaps,
>
> Kristaps Dzonsons writes:
> > Enclosed is a one-liner unbreaking the Mac OS X build and possibly
> > other systems as well.
> >
> > (I recall that <stdint.h> is required for uint32_t according to C99.)
>
> Yes, and the ohash_interval(3) manual clearly shows that stdint.h must
> be included before ohash.h.
>
> The reason it doesn't fail on OpenBSD is that sys/types.h (incorrectly)
> exposes uint32_t. That's a bit of pollution that shouldn't happen, but
> as the XXX comment in the header states, "the rest of the includes are
> not ready for that yet."
(ok bentley@)
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
prev parent reply other threads:[~2015-07-24 9:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-24 9:08 Kristaps Dzonsons
2015-07-24 9:44 ` Anthony J. Bentley
2015-07-24 9:48 ` Anthony J. Bentley [this message]
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=12235.1437731307@CATHET.us \
--to=anthony@anjbe.name \
--cc=tech@mdocml.bsd.lv \
/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 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).