public inbox for dm-crypt@saout.de
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: Anon <5050202089@pm.me>, dm-crypt <dm-crypt@saout.de>
Subject: Re: [dm-crypt] Building issues with latest cryptsetup package
Date: Thu, 12 Sep 2019 16:33:04 +0200	[thread overview]
Message-ID: <12549b0d-82aa-2fe6-8af5-ea7fc436615d@gmail.com> (raw)
In-Reply-To: <3qMW-xDCmV_cpIim00eiw8xpCeZHnpPyKKHU3kQq_FOQCjWNFhh4g7w-wP65FoD6-r8piBT_VYaGpAGT0csU3GjSw-ILrv7G6PrtihA5YfY=@pm.me>



On 12/09/2019 12:13, Anon wrote:
> Hi,
> 
> Ime having issues trying to properly install/configure cryptsetup 2.2.1. I'm testing it in a VM with the same is as I use primarily to prevent data loss and I'm glad I did. I use Kubuntu 19.04. As luks is security software I like to stay up to date, Kubuntu includes version 2.1.0 therefore I'm trying to update it's version.
> 
> I extracted the archive, CD into it and ran: ./configure
> First time got a bunch of missing dependencies such as dev-mapper header files, libssl, blkid..I got those all installed then configure ran without errors.
> 
> I then ran make, and that completed just fine. Then sudo make install, which was successful.
> 
> Once running a cryptsetup command (such as cryptsetup --version), it would give me error: cryptsetup: relocation error: cryptsetup: symbol crypt_reencrypt_init_by_passphrase version CRYPTSETUP_2.0 not defined in file libcryptsetup.so.12 with link time reference

Check ldd over cryptsetup binary, you have apparently some older libcryptsetup library in some system path, just remove it.

(This is a new symbol added in 2.2)

m.

      reply	other threads:[~2019-09-12 14:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-12 10:13 [dm-crypt] Building issues with latest cryptsetup package Anon
2019-09-12 14:33 ` 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=12549b0d-82aa-2fe6-8af5-ea7fc436615d@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=5050202089@pm.me \
    --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