From: Andre McCurdy <armccurdy@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH v2 3/5] openssl_1.0: drop unmaintained darwin support
Date: Sat, 28 Jul 2018 13:39:21 -0700 [thread overview]
Message-ID: <1532810363-23110-3-git-send-email-armccurdy@gmail.com> (raw)
In-Reply-To: <1532810363-23110-1-git-send-email-armccurdy@gmail.com>
The fact that the darwin support only appears to consider x86 (and
not x86_64) suggests that it's not maintained or tested. In general
oe-core doesn't support building on darwin.
Signed-off-by: Andre McCurdy <armccurdy@gmail.com>
---
meta/recipes-connectivity/openssl/openssl_1.0.2o.bb | 7 -------
1 file changed, 7 deletions(-)
diff --git a/meta/recipes-connectivity/openssl/openssl_1.0.2o.bb b/meta/recipes-connectivity/openssl/openssl_1.0.2o.bb
index c2d9264..2804203 100644
--- a/meta/recipes-connectivity/openssl/openssl_1.0.2o.bb
+++ b/meta/recipes-connectivity/openssl/openssl_1.0.2o.bb
@@ -89,10 +89,6 @@ CFLAG += "-Wa,--noexecstack"
CFLAG_append_class-native = " -fPIC"
-do_configure_prepend_darwin () {
- sed -i -e '/version-script=openssl\.ld/d' Configure
-}
-
do_configure () {
# The crypto_use_bigint patch means that perl's bignum module needs to be
# installed, but some distributions (for example Fedora 23) don't ship it by
@@ -190,9 +186,6 @@ do_configure () {
linux-sparc)
target=linux-sparcv8
;;
- darwin-i386)
- target=darwin-i386-cc
- ;;
esac
# inject machine-specific flags
--
1.9.1
next prev parent reply other threads:[~2018-07-28 20:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-28 20:39 [PATCH v2 1/5] openssl_1.0: drop obsolete ca.patch Andre McCurdy
2018-07-28 20:39 ` [PATCH v2 2/5] openssl_1.0: drop obsolete exporting of AS, EX_LIBS and DIRS Andre McCurdy
2018-07-28 20:39 ` Andre McCurdy [this message]
2018-07-28 20:39 ` [PATCH v2 4/5] openssl_1.0: add PACKAGECONFIG option to control manpages Andre McCurdy
2018-07-28 20:39 ` [PATCH v2 5/5] openssl_1.0: squash whitespace in CC_INFO Andre McCurdy
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=1532810363-23110-3-git-send-email-armccurdy@gmail.com \
--to=armccurdy@gmail.com \
--cc=openembedded-core@lists.openembedded.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