DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: demo demo <demodemodx@gmail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] Building error
Date: Wed, 08 Aug 2012 11:39:56 +0200	[thread overview]
Message-ID: <502233EC.1030701@gmail.com> (raw)
In-Reply-To: <CACgeVjLcDk65jjQvoPtB4zx-BpKALK1yUjrwfCo+VfkgeLUf2w@mail.gmail.com>

On 08/08/2012 11:10 AM, demo demo wrote:
> Hi,
> 
> My goal is to manage crypted devices using own C program which should include and use Cryptsetup API.
> 
> In order to start I'm first trying to build the example files but I got the following error:
> 
> # make
> gcc -O0 -g -Wall -D_GNU_SOURCE   -c -o crypt_luks_usage.o crypt_luks_usage.c
> crypt_luks_usage.c: In function ‘format_and_add_keyslots’:
> crypt_luks_usage.c:85: error: ‘struct crypt_params_luks1’ has no member named ‘data_device’
> make: *** [crypt_luks_usage.o] Error 1
> 
> 
> It's on CentOS 6.2, cryptsetup 1.2.0

The example is taken from more recent version of cryptsetup source (data_device was introduced later).

Whatever, in this example just comment out this line setting data_device to NULL
and it will work even int RHEL6.

(I will perhaps remove it upstream as well so the basic example compiles even on older versions of library.)

Milan

  reply	other threads:[~2012-08-08  9:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-08  9:10 [dm-crypt] Building error demo demo
2012-08-08  9:39 ` Milan Broz [this message]
     [not found]   ` <CACgeVjKhPvSXjqt0CR2w2KCV3vut8cK3P=AnsM7qqjAEZQUZxw@mail.gmail.com>
2012-08-16  6:43     ` demo demo
2012-08-16 10:52       ` Milan Broz
2012-08-16 11:13         ` demo demo
2012-08-16 10:29   ` demo demo
  -- strict thread matches above, loose matches on Subject: below --
2012-08-08  9:29 demo demo

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=502233EC.1030701@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=demodemodx@gmail.com \
    --cc=dm-crypt@saout.de \
    /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