From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/5] libressl: new package
Date: Thu, 15 Jun 2017 23:25:23 +0200 [thread overview]
Message-ID: <20170615232523.6adeb951@windsurf.lan> (raw)
In-Reply-To: <20170615142928.31927-1-aduskett@codeblue.com>
Hello Adam,
Thanks for working on the libressl topic, definitely a useful change.
See some comments below.
On Thu, 15 Jun 2017 10:29:24 -0400, Adam Duskett wrote:
> Libressl is a fork of openssl from OpenSSL in 2014. It's goal is to
> modernize the OpenSSL codebase, improve security, and apply best practice
> development processes.
>
> Right now, libressl is API compatible with OpenSSL 1.0.1, but does not yet
> include all new APIs from OpenSSL 1.0.2 and later.
>
> The main source is libressl-portable, which "Includes the build scaffold
> and compatibility layer that builds portable LibreSSL from the OpenBSD
> source code."
>
> Before the build process can begin, autogen.sh must be ran manually,
> as it pulls from the upstream OpenBSD source which adds several
> directories to the source, along with several other steps necessary
> before building can begin. Setting LIBRESSL_AUTORECONF = YES fails
> with several "No such file or directory" errors as well.
>
> This package has been tested with the following architectures and c libraries:
> - armv4
> - aarch64
> - ppc
> - ppc64
> - ppc64le
> - x86_64
> - uClibc-ng
> - glibc 2.24
> - musl
Why is this entire commit log indented with 4 spaces? Could you just
start the lines, well, at the beginning of the lines?
> +LIBRESSL_VERSION = v2.5.4
> +LIBRESSL_SITE = https://github.com/libressl-portable/portable.git
> +LIBRESSL_SITE_METHOD = git
Please use the "github" helper function instead.
Or even better, use release tarballs from
http://ftp.openbsd.org/pub/OpenBSD/LibreSSL/. This way, you don't need
to call autogen.sh.
> +LIBRESSL_LICENSE = ISC, BSD-3-Clause, OpenSSL or SSLeay
Where do this license list comes from?
> +LIBRESSL_LICENSE_FILES = COPYING
I don't see any file named "COPYING" in the repository at
https://github.com/libressl-portable/portable/tree/v2.5.4.
> +LIBRESSL_INSTALL_STAGING = YES
> +
> +# autogen.sh needs to be ran manually as it pulls from the upstream
> +# OpenBSD source which adds several directories to the source.
> +# Setting LIBRESSL_AUTORECONF = YES fails with several
> +# "No such file or directory" errors.
> +define LIBRESSL_RUN_AUTOGEN
> + cd $(@D) && PATH=$(BR_PATH) ./autogen.sh
> +endef
> +LIBRESSL_POST_PATCH_HOOKS += LIBRESSL_RUN_AUTOGEN
Not needed if you use the release tarballs, as suggested above.
> +
> +ifeq ($(BR2_PACKAGE_LIBRESSL_BIN),)
> +define LIBRESSL_REMOVE_BIN
> + $(RM) -f $(TARGET_DIR)/usr/bin/openssl
> +endef
> +LIBRESSL_POST_INSTALL_TARGET_HOOKS += LIBRESSL_REMOVE_BIN
> +endif
> +
> +$(eval $(autotools-package))
> +$(eval $(host-autotools-package))
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-06-15 21:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-15 14:29 [Buildroot] [PATCH 1/5] libressl: new package Adam Duskett
2017-06-15 14:29 ` [Buildroot] [PATCH 2/5] libssl: new virtual package Adam Duskett
2017-06-15 21:28 ` Thomas Petazzoni
2017-06-15 22:54 ` Arnout Vandecappelle
2017-06-16 12:43 ` Adam Duskett
2017-06-20 13:11 ` Adam Duskett
2017-06-22 11:32 ` Adam Duskett
2017-06-22 12:17 ` Thomas Petazzoni
2017-06-24 15:55 ` Adam Duskett
2017-06-15 22:34 ` Arnout Vandecappelle
2017-06-15 14:29 ` [Buildroot] [PATCH 3/5] libressl: add libssl virtual package support Adam Duskett
2017-06-15 22:41 ` Arnout Vandecappelle
2017-06-15 14:29 ` [Buildroot] [PATCH 4/5] openssl: " Adam Duskett
2017-06-15 22:44 ` Arnout Vandecappelle
2017-06-15 14:29 ` [Buildroot] [PATCH 5/5] DEVELOPERS: Add Adam Duskett for libressl Adam Duskett
2017-06-15 21:28 ` Thomas Petazzoni
2017-06-15 21:25 ` Thomas Petazzoni [this message]
2017-06-15 22:27 ` [Buildroot] [PATCH 1/5] libressl: new package Arnout Vandecappelle
2017-06-16 12:38 ` Adam Duskett
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=20170615232523.6adeb951@windsurf.lan \
--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