All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/5] gnupg2: new package
Date: Fri, 6 Jun 2014 19:06:58 +0200	[thread overview]
Message-ID: <20140606170658.GD3481@free.fr> (raw)
In-Reply-To: <5391EDAD.6070908@imgtec.com>

Vincente, All,

On 2014-06-06 17:34 +0100, Vicente Olivert Riera spake thusly:
> On 06/06/2014 03:33 PM, Bernd Kuhls wrote:
> >afaik gnupg2 is compatible with uclibc if you use the existing libpthsem
> >package instead of your new pth package.
> 
> no, it doesn't build (as is) using libpthsem. Here is why:
[--SNIP--]
> So, we have three options here and we need to decide one of them:
> 
> Option 1: add the new pth package
>   pros: -there is no need to patch libpthsem
>   cons: -gnupg2 will not work with uclibc
> 
> Option 2: patch the libpthsem package
>   pros: -no need to add pth package
>         -gnupg2 will work with uclibc
>   cons: -we need to patch libpthsem to install compatibility stuff
> 
> Option 3: patch gnupg2 to use libpthsem in case of pth is missing
>   pros: -no need to add pth package
>         -gnupg2 will work with uclibc
>         -gnupg2 will work with both libpthsem and pth
>   cons: -patching gnupg2 source code should be accepted upstream

I think option 1 is the best for now.

If Bernd (or anyone else) is interested in making gnupg2 work on uClibc,
it will be possible for him to apply either option 2 or option 3 later
on. Adding support for uClibc can (and should) be done in a separate
patch, anyway.

And whatever the package we patch (pthsem or gnupg2 or both), the patch
should be submitted upstream, of course! ;-)

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2014-06-06 17:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-06 13:44 [Buildroot] [PATCH 0/5] Add support for gnupg2 Vicente Olivert Riera
2014-06-06 13:44 ` [Buildroot] [PATCH 1/5] pth: new package Vicente Olivert Riera
2014-06-06 19:47   ` Thomas Petazzoni
2014-06-09  8:53     ` Vicente Olivert Riera
2014-07-23 21:36   ` Thomas Petazzoni
2014-06-06 13:44 ` [Buildroot] [PATCH 2/5] libksba: " Vicente Olivert Riera
2014-06-06 14:35   ` Bernd Kuhls
2014-06-09 13:00   ` Thomas Petazzoni
2014-06-06 13:44 ` [Buildroot] [PATCH 3/5] gnupg2: " Vicente Olivert Riera
2014-06-06 14:33   ` Bernd Kuhls
2014-06-06 16:34     ` Vicente Olivert Riera
2014-06-06 17:06       ` Yann E. MORIN [this message]
2014-07-23 21:35       ` Thomas Petazzoni
2014-06-06 13:44 ` [Buildroot] [PATCH 4/5] gnupg: Make gnupg and gnupg2 mutual exclusive Vicente Olivert Riera
2014-07-23 21:36   ` Thomas Petazzoni
2014-06-06 13:44 ` [Buildroot] [PATCH 5/5] pinentry: new package Vicente Olivert Riera
2014-06-09 13:32   ` Thomas Petazzoni

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=20140606170658.GD3481@free.fr \
    --to=yann.morin.1998@free.fr \
    --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 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.