All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: "Almeida, Gabriel" <Gabriel.Almeida@harman.com>,
	"dm-crypt@saout.de" <dm-crypt@saout.de>
Subject: Re: [dm-crypt] configure
Date: Mon, 7 Dec 2015 15:32:03 +0100	[thread overview]
Message-ID: <56659863.6080701@gmail.com> (raw)
In-Reply-To: <B267CE46C9DC3C4BB251EC9C004EA5662C5230F9@HIKAWSEXMB01.ad.harman.com>


On 12/07/2015 03:12 PM, Almeida, Gabriel wrote:
> While trying to install cryptsetup and I get the following error…
> Steps are done as follows:
> 
> 
> 
> $ git clone https://gitlab.com/cryptsetup/cryptsetup.git
> 
> $ git checkout v1_7_0
> 
> $ cd cryptsetup
> 
> 
> 
> At this point, instructions are asking to run ./configure, however
> there is no such file inside.

Configure is distributed in tarballs, downloaded from
https://www.kernel.org/pub/linux/utils/cryptsetup/

For git branch you need to run ./autogen.sh to generate it.

> So while running ./autogen.sh  I get the following error:
> 
> 
> 
> configure.ac:42: error: possibly undefined macro: AC_MSG_ERROR
> 
> If this token and others are legitimate, please use
> m4_pattern_allow.
> 
> See the Autoconf documentation.
> 
> configure.ac:156: error: possibly undefined macro: AM_PATH_LIBGCRYPT

You do not have all development packages installed.
(I guess pkgconfig or gcrypt devel here.)

I do not know your distro but better use tarball, run pregenerated
configure and it will probably print more info.

Milan

  reply	other threads:[~2015-12-07 14:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-07 14:12 [dm-crypt] configure Almeida, Gabriel
2015-12-07 14:32 ` Milan Broz [this message]
2015-12-07 14:38   ` Almeida, Gabriel
  -- strict thread matches above, loose matches on Subject: below --
2015-12-07 14:08 Almeida, Gabriel

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=56659863.6080701@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=Gabriel.Almeida@harman.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.