public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michael Haubenwallner" <haubi@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/prefix:master commit in: dev-libs/openssl/
Date: Tue,  3 Oct 2017 07:49:26 +0000 (UTC)	[thread overview]
Message-ID: <1507016943.2cc68faf61f24aaa4350875ca9647a42db54e5af.haubi@gentoo> (raw)

commit:     2cc68faf61f24aaa4350875ca9647a42db54e5af
Author:     Michael Haubenwallner <haubi <AT> gentoo <DOT> org>
AuthorDate: Tue Oct  3 07:48:49 2017 +0000
Commit:     Michael Haubenwallner <haubi <AT> gentoo <DOT> org>
CommitDate: Tue Oct  3 07:49:03 2017 +0000
URL:        https://gitweb.gentoo.org/repo/proj/prefix.git/commit/?id=2cc68faf

dev-libs/openssl: preserve non-static .dll.a libs

Package-Manager: Portage-2.3.10-prefix, Repoman-2.3.3

 dev-libs/openssl/openssl-1.0.2l.ebuild | 2 +-
 dev-libs/openssl/openssl-1.1.0f.ebuild | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/dev-libs/openssl/openssl-1.0.2l.ebuild b/dev-libs/openssl/openssl-1.0.2l.ebuild
index 78e448cb50..2022ae6658 100644
--- a/dev-libs/openssl/openssl-1.0.2l.ebuild
+++ b/dev-libs/openssl/openssl-1.0.2l.ebuild
@@ -225,7 +225,7 @@ multilib_src_install_all() {
 	# Only way around this would be to manually configure+compile openssl
 	# twice; once with shared lib support enabled and once without.
 	use static-libs || find "${ED}"usr/lib* -mindepth 1 -maxdepth 1 \
-		-name "lib*.a" -not -name "lib*$(get_libname)" -delete
+		-name "lib*.a" -not -name "*.dll.a" -not -name "*$(get_libname)" -delete
 
 	# create the certs directory
 	dodir ${SSL_CNF_DIR}/certs

diff --git a/dev-libs/openssl/openssl-1.1.0f.ebuild b/dev-libs/openssl/openssl-1.1.0f.ebuild
index 38100de289..2ae77799e5 100644
--- a/dev-libs/openssl/openssl-1.1.0f.ebuild
+++ b/dev-libs/openssl/openssl-1.1.0f.ebuild
@@ -203,7 +203,7 @@ multilib_src_install_all() {
 	# Only way around this would be to manually configure+compile openssl
 	# twice; once with shared lib support enabled and once without.
 	use static-libs || find "${ED}"usr/lib* -mindepth 1 -maxdepth 1 \
-		-name "lib*.a" -not -name "lib*$(get_libname)" -delete
+		-name "lib*.a" -not -name "*.dll.a" -not -name "*$(get_libname)" -delete
 
 	# create the certs directory
 	keepdir ${SSL_CNF_DIR}/certs


             reply	other threads:[~2017-10-03  7:49 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-03  7:49 Michael Haubenwallner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-12-15  0:42 [gentoo-commits] repo/proj/prefix:master commit in: dev-libs/openssl/ Sam James
2021-06-21 18:37 Fabian Groffen
2021-03-26  7:54 Fabian Groffen
2021-01-06 11:58 Fabian Groffen
2020-12-26 19:16 Fabian Groffen
2020-12-08 23:24 Sam James
2020-06-07 13:10 Fabian Groffen
2019-09-17 10:47 Fabian Groffen
2019-05-14  9:15 Michael Haubenwallner
2019-02-26  9:17 Michael Haubenwallner
2019-02-15 20:10 Michael Haubenwallner
2019-02-13 16:31 Michael Haubenwallner
2018-07-03 20:03 Fabian Groffen
2018-07-03 13:24 Michael Haubenwallner
2018-06-22  8:49 Fabian Groffen
2016-05-09 15:57 Michael Haubenwallner
2016-03-24  7:14 Fabian Groffen
2015-11-02 19:06 Fabian Groffen

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=1507016943.2cc68faf61f24aaa4350875ca9647a42db54e5af.haubi@gentoo \
    --to=haubi@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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