From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Sun, 21 Jun 2015 06:45:40 +0200 Subject: [Buildroot] [PATCH 1/2] openssl: support building the binary without MMU In-Reply-To: <1434711274-49716-1-git-send-email-benoit@wsystem.com> References: <1434711274-49716-1-git-send-email-benoit@wsystem.com> Message-ID: <20150621064540.534ebebc@free-electrons.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Dear Beno?t Th?baudeau, On Fri, 19 Jun 2015 12:54:33 +0200, Beno?t Th?baudeau wrote: > 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 Hum. But then it means that we have propagated the MMU dependency to all reverse dependencies of openssl (i.e packages that depend on openssl), but they may no longer need this dependency anymore. There is a fairly huge list of packages that "select BR2_PACKAGE_OPENSSL". How can we find out which ones will now build fine without MMU support ? By the way, do you have a specific need for openssl on no-MMU platforms? If so, on which platform? We don't have many no-MMU users, so it's good when they speak up :-) Thanks, Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com