Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Aleksandr Makarov <aleksandr.o.makarov@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2] package/libest: new package
Date: Sat, 8 Jan 2022 14:38:24 +0100	[thread overview]
Message-ID: <20220108143824.2cdc9a29@windsurf> (raw)
In-Reply-To: <20200715223514.15744-1-aleksandr.o.makarov@gmail.com>

Hello Aleksandr,

On Wed, 15 Jul 2020 16:35:14 -0600
Aleksandr Makarov <aleksandr.o.makarov@gmail.com> wrote:

> libest is a C implementation of RFC 7030 (Enrollment over
> Secure Transport).
> 
> It can be used to provision public key certificates from
> a certificate authority (CA) or registration authority (RA)
> to end-user devices and network infrastructure devices.
> 
> https://github.com/cisco/libest
> 
> Notes on patches included in this package:
> 
> - libest bundles a stubbed version of libsafec, and has no provision
>   to build against a system-installed full (non-stubbed) libsafec.
>   We add a patch to make that possible.
> 
> - Added a configuration option --{enable,disable}-examples to toggle
>   examples build by a separate patch.
> 
> - There's a configuration option `--enable-jni` which allows to build
>   a JNI library for binding libest to Java programs. And that library
>   would be using an outdated version of OpenSSL 1.0.
>   We fix that by adding support for OpenSSL 1.1 API for that library.
> 
> - Fixed a bug when specifying either `--enable-FEATURE` or `--disable-FEATURE`
>   has always been enabling the feature.

Sorry for the long delay. I finally applied your patch, but after
making some significant changes:

    [Thomas:
    - Added comments about the upstream status in existing patches
    - Added a patch fixing an autoreconf issue
    - Added a patch adding a missing "extern" on a variable to fix build
      with gcc 10
    - Removed the glibc dependency by using the new libexecinfo package
    - Drastically simplified the complex libcoap disabling and client-only
      mode vs. OpenJDK issue. libcoap support is now forcefully disabled,
      and client-mode only option is made invisible when OpenJDK is
      enabled.
    - Fixed the license information;
    - Added missing host-pkgconf
    ]

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2022-01-08 13:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-15 22:35 [Buildroot] [PATCH v2] package/libest: new package Aleksandr Makarov
2022-01-08 13:38 ` Thomas Petazzoni [this message]

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=20220108143824.2cdc9a29@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=aleksandr.o.makarov@gmail.com \
    --cc=buildroot@buildroot.org \
    /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