buildroot/package/openssl/Config.in, branch 2017.11

openssl: disable libressl on uClibc noMMU

2017-11-06T14:17:45+00:00

uClibc doesn't implement __register_atfork() on noMMU systems, causing a build failure of libressl. Since openssl is available as an alternative on such platforms, we just disable libressl on uClibc/noMMU systems. Fixes: /home/thomas/projets/buildroot/output/build/libressl-2.5.5/crypto/.libs/libcrypto.a(arc4random.o): In function `_rs_init.part.1': arc4random.c:(.text+0x74): undefined reference to `__register_atfork' collect2: error: ld returned 1 exit status This build issue is not visible in the autobuilders, because libressl is only selectable through a choice, which isn't randomized by the autobuilder logic. Signed-off-by: Thomas Petazzoni Signed-off-by: Peter Korsgaard

openssl: unconditionally define BR2_PACKAGE_PROVIDES_HOST_OPENSSL

2017-10-22T12:04:48+00:00

Fixes: http://autobuild.buildroot.net/results/207/207d0ca1fe5328e675246c851fcb0d5685f8c0bd/ http://autobuild.buildroot.net/results/546/546a56d6dd39e5e9ecfe25fd36a00510e6c0c45b/ host-openssl may be used without openssl being enabled for the target, so move BR2_PACKAGE_PROVIDES_HOST_OPENSSL outside the BR2_PACKAGE_OPENSSL conditional. While we're at it, add a comment explaining what this magic config symbol does. Signed-off-by: Peter Korsgaard Signed-off-by: Thomas Petazzoni

openssl: add libressl as a provider

2017-10-21T19:28:13+00:00

At this point, libressl can be added to the openssl virtual package. - Remove the entry package/libressl/Config.in from package/Config.in - Remove the file: package/libressl/Config.in - Add libressl entry to package/openssl/Config.in Signed-off-by: Adam Duskett Signed-off-by: Thomas Petazzoni

openssl: introduce BR2_PACKAGE_OPENSSL_FORCE_LIBOPENSSL

2017-10-21T19:28:13+00:00

Some packages that use openssl are not compatible with libressl, only with the real openssl (known as libopenssl in Buildroot). So before we add libressl as a provider for the openssl virtual package, we introduce a BR2_PACKAGE_OPENSSL_FORCE_LIBOPENSSL hidden option that packages incompatible with LibreSSL will be able to select. This will allow packages that need OpenSSL to continue using "select", without having to change to using "depends on" dependencies. Signed-off-by: Thomas Petazzoni

openssl: new virtual package

2017-10-21T19:28:13+00:00

To ease the transition to having both OpenSSL and LibreSSL, there has to be a new virtual package introduced to handle both. Instead of making a libssl, and adding OpenSSL and libressl to that package, it will be far easier to move openssl to libopenssl and to make OpenSSL a virtual package. This offers a few advantages: - BR2_PACKAGE_OPENSSL is still a visible symbol with no dependencies. - It does not require a huge patch to convert every instance of OpenSSL -> libssl) - Users will be able to update without ever having to select anything new. - LibreSSL can be added at a later date to the virtual package. Signed-off-by: Adam Duskett [Thomas: define BR2_PACKAGE_PROVIDES_HOST_OPENSSL to the value "host-libopenssl" as we always want to use the original OpenSSL for the host variant.] Signed-off-by: Thomas Petazzoni

openssl: drop !static dependency from OPENSSL_BIN option

2015-07-09T06:55:16+00:00

The dependency doesn't make sense now that the option only controls if the built binary gets installed into the target or not, so drop it. Signed-off-by: Peter Korsgaard

openssl: always build apps

2015-07-06T15:09:45+00:00

Now that building the openssl binary without MMU is supported, the only reason left for not building apps if the openssl binary is disabled is to save build time. Moreover, the commit 720893b62510438237b9923d744dd079ddb4f67d "openssl: disable apps for NOMMU", which added this behavior, had a side effect: the scripts from apps (CA.pl, CA.sh and tsget) and the default configuration file (openssl.cnf) were no longer installed, which is not advertized by the BR2_PACKAGE_OPENSSL_BIN option. CA.pl and CA.sh use the openssl binary, so not installing them without the latter makes sense. But tsget does not use the openssl binary, and openssl.cnf can be used by libcrypto, so it is preferable to handle BR2_PACKAGE_OPENSSL_BIN like before the commit mentioned above, i.e. to always build and install apps and to just remove the openssl binary afterwards if needed. This is what the current commit does, but installing only the helper scripts having their dependencies (perl or the openssl binary) satisfied. The help text is updated accordingly. Signed-off-by: Benoît Thébaudeau Signed-off-by: Thomas Petazzoni

openssl: support building the binary without MMU

2015-06-30T14:44:12+00:00

The commit 720893b62510438237b9923d744dd079ddb4f67d "openssl: disable apps for NOMMU" prevented the openssl binary from being built without MMU in order to fix a build failure without fork(). However, openssl is designed to support the lack of fork() with -DHAVE_FORK=0, so allow the openssl binary to be enabled without MMU thanks to this option. Signed-off-by: Benoît Thébaudeau Signed-off-by: Thomas Petazzoni

package/openssl: bin/openssl depends on dynamic linking

2015-04-19T09:38:37+00:00

Fixes /home/br/br3/output/host/usr/lib/gcc/i586-buildroot-linux-uclibc/4.8.4/../../../../i586-buildroot-linux-uclibc/bin/ld: cannot find -ldl using this defconfig BR2_STATIC_LIBS=y BR2_PACKAGE_OPENSSL=y BR2_PACKAGE_OPENSSL_BIN=y Quoting PROBLEMS: "We don't have framework to associate -ldl with no-dso, therefore the only way is to edit Makefile right after ./config no-dso and remove -ldl from EX_LIBS line." To not make the build procedure more complicated disable static building of bin/openssl. [Thomas: add corresponding kconfig comment.] Signed-off-by: Bernd Kuhls Signed-off-by: Thomas Petazzoni

Config.in files: use if/endif instead of 'depends on' for main symbol

2013-12-25T11:21:39+00:00

In the Config.in file of package foo, it often happens that there are other symbols besides BR2_PACKAGE_FOO. Typically, these symbols only make sense when foo itself is enabled. There are two ways to express this: with depends on BR2_PACKAGE_FOO in each extra symbol, or with if BR2_PACKAGE_FOO ... endif around the entire set of extra symbols. The if/endif approach avoids the repetition of 'depends on' statements on multiple symbols, so this is clearly preferred. But even when there is only one extra symbol, if/endif is a more logical choice: - it is future-proof for when extra symbols are added - it allows to have just one strategy instead of two (less confusion) This patch modifies the Config.in files accordingly. Signed-off-by: Thomas De Schampheleire Signed-off-by: Thomas Petazzoni