DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "shmick@riseup.net" <shmick@riseup.net>
To: Milan Broz <gmazyland@gmail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] 1.6.2 - waiting for zero, luksFormat hung
Date: Fri, 22 Nov 2013 01:55:26 +1100	[thread overview]
Message-ID: <528E1EDE.9010309@riseup.net> (raw)
In-Reply-To: <528D07E2.9040601@gmail.com>



Milan Broz:
> 
> On 11/20/2013 05:44 PM, shmick@riseup.net wrote:
>> ./configure --with-crypto_backend=openssl --enable-dev-random
>>
>> cryptsetup benchmark
>>
>> # Tests are approximate using memory only (no storage IO).
>> cryptsetup: relocation error: cryptsetup: symbol crypt_benchmark_kdf,
>> version CRYPTSETUP_1.0 not defined in file libcryptsetup.so.4 with link
>> time reference
> 
> You are compiling own version, but code apparently tries to load old
> libryptsetup library from system.
> (And it seems I did lib versioning wrong here ...)

i tried compiling with libgcrypt 1.5.3 but the same errors occur

> 
> Either try to run src/cryptsetup (libtool wrapper should provide proper paths)
> or override library path using LD_LIBRARY_PATH.
> (it should point to src/lib/.libs or so)

same problem
./configure --with-libgcrypt-prefix=/usr/local LDFLAGS=-L/usr/local/lib
(this is where libgcrypt is)

> 
> (Or if you installed compiled version, be sure it overwrites old libcryptsetup.)

ive also then tried with my distro default cryptsetup 1.4.1 but the same
errors again in xts mode with AES or TWOFISH

any ideas ???

> 
> Milan
> 

  reply	other threads:[~2013-11-21 14:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-20 16:44 [dm-crypt] 1.6.2 - waiting for zero, luksFormat hung shmick
2013-11-20 19:05 ` Milan Broz
2013-11-21 14:55   ` shmick [this message]
2013-11-21 18:58     ` Milan Broz
2013-11-22  7:40       ` shmick
2013-11-22  8:13         ` Milan Broz
2013-11-22  8:38           ` shmick
2013-11-22  9:17             ` Milan Broz
2013-11-22 11:56               ` shmick
2013-11-22 13:11                 ` Milan Broz

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=528E1EDE.9010309@riseup.net \
    --to=shmick@riseup.net \
    --cc=dm-crypt@saout.de \
    --cc=gmazyland@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