From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gmazyland@gmail.com>
Received: from mail.saout.de ([127.0.0.1])
 by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id juIjIl3vJGPb for <dm-crypt@saout.de>;
 Mon,  7 Jan 2013 19:12:23 +0100 (CET)
Received: from mail-ee0-f53.google.com (mail-ee0-f53.google.com [74.125.83.53])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mail.saout.de (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Mon,  7 Jan 2013 19:12:23 +0100 (CET)
Received: by mail-ee0-f53.google.com with SMTP id c50so9172045eek.12
 for <dm-crypt@saout.de>; Mon, 07 Jan 2013 10:12:23 -0800 (PST)
Message-ID: <50EB1004.6020407@gmail.com>
Date: Mon, 07 Jan 2013 19:12:20 +0100
From: Milan Broz <gmazyland@gmail.com>
MIME-Version: 1.0
References: <50DF635C.90003@gmail.com> <20121230083814.GA12005@tansi.org>
 <5f058e3c77fb70c10ba5e65e077baa3e.squirrel@ssl.verfeiert.org>
 <20121230102039.GA12533@tansi.org> <50E02816.9000001@gmail.com>
 <1357474572.2800.50.camel@scapa> <50E9A54F.1060203@gmail.com>
 <1357539821.2800.67.camel@scapa>
 <465f60dfbd6c3ec3ef49c17d2beee680.squirrel@ssl.verfeiert.org>
In-Reply-To: <465f60dfbd6c3ec3ef49c17d2beee680.squirrel@ssl.verfeiert.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] [ANNOUNCE] cryptsetup 1.6.0-rc1
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt/>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: sven@whgl.uni-frankfurt.de
Cc: dm-crypt@saout.de

On 01/07/2013 12:21 PM, Sven Eschenberg wrote:
> Exactly, when the header is missing, you can hardly compile support in, as
> the compiler does not know the interface. Putting the header into
> cryptsetup package is not an option, as it is not part of cryptsetup
> itself, but merely the kernel and possibly changes from time to time.
> 
> Usually, a package describes its dependencies and then the builder's job
> is to provide an adequate build environment to get the build he wants.

Well, it would be nice to have exact bug report if you see some problem,
please test current git version.

The  --disable-kernel_crypto switch is required only for systems where
kernel with userspace crypto API will never be available.

For other systems it is maintainer's job to set up dependences properly
(require proper kernel headers).

FYI: you will see this warning (RHEL5, as example of old system)
...
checking for linux/if_alg.h... no
configure: error: You need Linux kernel headers with userspace crypto interface. (Or use --disable-kernel_crypto.)

Here (RHEL5) the only option is to use --disable-kernel_crypto.

Milan