From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ecryptfs-utils: new package
Date: Fri, 31 May 2013 20:26:22 +0200 [thread overview]
Message-ID: <20130531202622.6576897d@skate> (raw)
In-Reply-To: <CAOPBCFU3+h-zu7RK6rvhC=ja9jFHWerOLzkRkpK1bQrsDysHkA@mail.gmail.com>
Dear Marcin Bis,
On Fri, 31 May 2013 18:31:20 +0200, Marcin Bis wrote:
> > Apparently, ecryptfs-utils can be built without libnss, and use gcrypt
> > instead. Maybe it would be worth supporting this possibility. But it's
> > not mandatory to get your patch accepted.
>
> I have got a problem trying to build it with gcrypt instead of nss.
>
> The dependencies seems to be hard-coded:
> http://bazaar.launchpad.net/~ecryptfs/ecryptfs/trunk/view/head:/src/libecryptfs/main.c#L24
> nss.h and pk11func.h are provided only by libnss.
> (and libecryptfs is essential for mount.ecryptfs to work)
>
> Foud this one too: https://bugs.launchpad.net/ecryptfs/+bug/1072643
Is this case, no problem, just submit something like you did, which
depends on NSS only. If someone cares enough to make it work with
gcrypt, this someone will fix it.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-05-31 18:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 15:49 [Buildroot] [PATCH] ecryptfs-utils: new package Marcin Bis
2013-05-31 16:11 ` Thomas Petazzoni
2013-05-31 16:31 ` Marcin Bis
2013-05-31 18:26 ` Thomas Petazzoni [this message]
2013-05-31 20:12 ` [Buildroot] [PATCH v2] " Marcin Bis
2013-06-02 21:17 ` Peter Korsgaard
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=20130531202622.6576897d@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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