From: Milan Broz <gmazyland@gmail.com>
To: ".. ink .." <mhogomchungu@gmail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] static libraries
Date: Sun, 06 Jan 2013 11:21:49 +0100 [thread overview]
Message-ID: <50E9503D.8090602@gmail.com> (raw)
In-Reply-To: <CAFnMBaTeM7KSEW29pgF_qKGcLO-Ay6aWYPOGum+Wb0ViQ2aRAA@mail.gmail.com>
On 01/05/2013 11:15 PM, .. ink .. wrote:
>
>
>
> Anyway, if you find some situation when configure script doesn't detect
> some missing library, let me know (with proper info mentioned above).
>
>
> i am using version 0.27.1 of pkg-config
>
> http://pastebin.com/ASBk1X6K
That's exactly error I need to see that something is wrong :)
./configure: line 16992: --static: command not found
(pkgconfig was not properly initialized in autoconf)
> The development package of libgrypt does not ship with libgcrypt.a in
> the distribution i am using and this necessitated me to build another
> version of libgrcypt to have a static library and i installed it in
> "/home/local" because thats where i install personal packages.
Gcrypt supports static libraries but not all distros use them.
The fun is here it uses own libgcrypt-config script which does not
have --static switch to properly detect libraries needed for
static compilation.
IOW see
libgcrypt-config --libs
(In fedora for example it reports -lgpg-error.)
But cryptsetup autoconf tries to handle that but I do not
want workaround for every broken gcrypt install...
As you can see here, it tries gpg-error library
LIBS="$saved_LIBS $LIBGCRYPT_LIBS -static"
AC_CHECK_LIB(gcrypt, gcry_check_version,,
AC_MSG_ERROR([Cannot find static gcrypt library.]),
[-lgpg-error])
So maybe the error message just should mention gpg-error as well.
Milan
next prev parent reply other threads:[~2013-01-06 10:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-05 9:05 [dm-crypt] static libraries .. ink ..
2013-01-05 11:05 ` Milan Broz
2013-01-05 12:12 ` .. ink ..
2013-01-05 17:56 ` Milan Broz
2013-01-05 22:15 ` .. ink ..
2013-01-05 22:48 ` .. ink ..
2013-01-06 10:21 ` Milan Broz [this message]
2013-01-06 10:50 ` .. ink ..
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=50E9503D.8090602@gmail.com \
--to=gmazyland@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