public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Joonas Niilola" <juippis@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: www-servers/lighttpd/files/, www-servers/lighttpd/
Date: Sat,  3 Jul 2021 15:46:19 +0000 (UTC)	[thread overview]
Message-ID: <1625326939.386e519bafff8c44a4b04a0f658b6bf382b0c095.juippis@gentoo> (raw)

commit:     386e519bafff8c44a4b04a0f658b6bf382b0c095
Author:     Herb Miller Jr <herb <AT> hlmjr <DOT> com>
AuthorDate: Thu May 20 21:05:19 2021 +0000
Commit:     Joonas Niilola <juippis <AT> gentoo <DOT> org>
CommitDate: Sat Jul  3 15:42:19 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=386e519b

www-servers/lighttpd: Fix nspr header location

Bug: https://bugs.gentoo.org/783936
Package-Manager: Portage-3.0.18, Repoman-3.0.3
Signed-off-by: Herb Miller Jr. <herb <AT> hlmjr.com>
Closes: https://github.com/gentoo/gentoo/pull/20900
Signed-off-by: Joonas Niilola <juippis <AT> gentoo.org>

 .../lighttpd/files/lighttpd-1.4.59-nspr-header.patch     | 16 ++++++++++++++++
 www-servers/lighttpd/lighttpd-1.4.59.ebuild              |  2 ++
 2 files changed, 18 insertions(+)

diff --git a/www-servers/lighttpd/files/lighttpd-1.4.59-nspr-header.patch b/www-servers/lighttpd/files/lighttpd-1.4.59-nspr-header.patch
new file mode 100644
index 00000000000..497ea36a167
--- /dev/null
+++ b/www-servers/lighttpd/files/lighttpd-1.4.59-nspr-header.patch
@@ -0,0 +1,16 @@
+diff --git a/configure.ac b/configure.ac
+index 325a1b4b..3f32daa9 100644
+--- a/configure.ac
++++ b/configure.ac
+@@ -887,7 +887,10 @@ if test "x$use_nss" = "xyes"; then
+       NSS_LIBS="-L$WITH_NSS/lib -lnss3"
+   else
+       PKG_CHECK_MODULES([NSS],[nss])
+-      CPPFLAGS="$CPPFLAGS -I/usr/include/nspr4"
++      if test "x$CRYPTO_LIB" = "x"; then
++        PKG_CHECK_MODULES([NSPR],[nspr])
++        CPPFLAGS="$CPPFLAGS $NSPR_CFLAGS"
++      fi
+   fi
+   AC_DEFINE([HAVE_NSS_NSS_H], [1], [nss/nss.h])
+   AC_DEFINE([HAVE_NSS3_NSS_H], [1], [nss3/nss.h])

diff --git a/www-servers/lighttpd/lighttpd-1.4.59.ebuild b/www-servers/lighttpd/lighttpd-1.4.59.ebuild
index b3d8e44ff79..86b8878e842 100644
--- a/www-servers/lighttpd/lighttpd-1.4.59.ebuild
+++ b/www-servers/lighttpd/lighttpd-1.4.59.ebuild
@@ -71,6 +71,8 @@ RDEPEND="${COMMON_DEPEND}
 	selinux? ( sec-policy/selinux-apache )
 "
 
+PATCHES=( "${FILESDIR}"/${P}-nspr-header.patch )
+
 # update certain parts of lighttpd.conf based on conditionals
 update_config() {
 	local config="${D}/etc/lighttpd/lighttpd.conf"


             reply	other threads:[~2021-07-03 15:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-03 15:46 Joonas Niilola [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-01-14 10:47 [gentoo-commits] repo/gentoo:master commit in: www-servers/lighttpd/files/, www-servers/lighttpd/ Sam James
2024-07-12 10:29 Sam James
2024-05-06 16:34 Sam James
2024-05-06 14:05 Sam James
2023-09-08 21:05 Sam James
2019-08-02 12:04 Mikle Kolyada
2018-04-28 12:53 Mikle Kolyada

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=1625326939.386e519bafff8c44a4b04a0f658b6bf382b0c095.juippis@gentoo \
    --to=juippis@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