From: Milan Broz <mbroz@redhat.com>
To: Colin Misare <corban.dallas@gmail.com>
Cc: dm-crypt@saout.de, ".. ink .." <mhogomchungu@gmail.com>
Subject: Re: [dm-crypt] odd behavior with libcryptsetup.h
Date: Mon, 28 May 2012 09:47:58 +0200 [thread overview]
Message-ID: <4FC32DAE.90109@redhat.com> (raw)
In-Reply-To: <CABnp7Mhs_cn0s=GfYRfqbz37jps9JfwO_NgMinaKfcCW=5w2og@mail.gmail.com>
On 05/28/2012 09:00 AM, Colin Misare wrote:
> I see this behaviour as well with gcc 4.6.3 using the libcryptset.h from git.
>
> Some quick searching on Googe leads me to believe that size_t is
> supposed to be in stddef.h. Like you noted simply adding that fixes
> the compilation.
Yes, it should be included in header itself.
Actually I just fixed it before I read your reply here... :)
http://code.google.com/p/cryptsetup/source/detail?r=65c4c62f78e07408081a20f1bea2b29212b85e01#
Thanks,
Milan
prev parent reply other threads:[~2012-05-28 7:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-28 6:42 [dm-crypt] odd behavior with libcryptsetup.h .. ink ..
2012-05-28 7:00 ` Colin Misare
2012-05-28 7:47 ` Milan Broz [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=4FC32DAE.90109@redhat.com \
--to=mbroz@redhat.com \
--cc=corban.dallas@gmail.com \
--cc=dm-crypt@saout.de \
--cc=mhogomchungu@gmail.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox