public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Fabian Groffen" <grobian@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: mail-filter/opendmarc/
Date: Fri, 22 Dec 2017 11:04:41 +0000 (UTC)	[thread overview]
Message-ID: <1513940672.bd68b762f17880871e949916b727c8e791c63593.grobian@gentoo> (raw)

commit:     bd68b762f17880871e949916b727c8e791c63593
Author:     Fabian Groffen <grobian <AT> gentoo <DOT> org>
AuthorDate: Fri Dec 22 11:04:15 2017 +0000
Commit:     Fabian Groffen <grobian <AT> gentoo <DOT> org>
CommitDate: Fri Dec 22 11:04:32 2017 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=bd68b762

mail-filter/opendmarc: fix building older version with newer glibc

Closes: https://bugs.gentoo.org/640012
Package-Manager: Portage-2.3.13, Repoman-2.3.3

 mail-filter/opendmarc/opendmarc-1.1.3.ebuild | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/mail-filter/opendmarc/opendmarc-1.1.3.ebuild b/mail-filter/opendmarc/opendmarc-1.1.3.ebuild
index 776550c0112..d57dcbb4599 100644
--- a/mail-filter/opendmarc/opendmarc-1.1.3.ebuild
+++ b/mail-filter/opendmarc/opendmarc-1.1.3.ebuild
@@ -17,6 +17,11 @@ DEPEND="dev-perl/DBI
 RDEPEND="${DEPEND}
 	dev-perl/Switch"
 
+src_prepare() {
+	# fix building with newer glibc, already fixed in later releases, #640012
+	sed -i -e 's/T_RRSIG/disabled_T_RRSIG/' libopendmarc/opendmarc_dns.c || die
+}
+
 src_configure() {
 	econf \
 		--docdir="${EPREFIX}"/usr/share/doc/${PF} \


             reply	other threads:[~2017-12-22 11:04 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-22 11:04 Fabian Groffen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-26 20:25 [gentoo-commits] repo/gentoo:master commit in: mail-filter/opendmarc/ Fabian Groffen
2022-08-04  1:45 Sam James
2022-04-22  6:34 Fabian Groffen
2022-03-10 21:12 Sam James
2021-08-20  7:31 Fabian Groffen
2021-08-20  6:26 Fabian Groffen
2021-08-19  1:08 Sam James
2021-08-11  6:39 Agostino Sarubbo
2021-08-11  0:04 Sam James
2021-08-10  6:43 Agostino Sarubbo
2021-08-10  6:43 Agostino Sarubbo
2021-08-10  6:42 Agostino Sarubbo
2021-05-08  8:23 Fabian Groffen
2021-03-05 20:27 Sam James
2020-10-16  6:29 Fabian Groffen
2020-10-15 18:40 Sergei Trofimovich
2020-10-03 15:13 Sam James
2020-10-02 22:31 Sam James
2020-10-02 21:36 Sam James
2020-10-01 22:55 Sergei Trofimovich
2020-09-29 11:42 Sam James
2020-09-28 17:41 Sergei Trofimovich
2020-05-12 17:50 Mart Raudsepp
2020-04-28  5:57 Fabian Groffen
2019-11-13 16:09 Agostino Sarubbo
2019-11-01 10:48 Mikle Kolyada
2019-10-17 11:23 Agostino Sarubbo
2019-10-17 10:32 Agostino Sarubbo
2019-10-17 10:29 Agostino Sarubbo
2019-10-17 10:25 Agostino Sarubbo
2019-10-17  9:53 Agostino Sarubbo
2019-05-11 12:16 Mikle Kolyada
2019-05-06 15:25 Tobias Klausmann
2019-05-03  7:11 Sergei Trofimovich
2019-04-14 11:12 Agostino Sarubbo
2019-04-11 19:15 Sergei Trofimovich
2019-04-10 17:04 Thomas Deutschmann
2019-03-16 15:15 Fabian Groffen
2018-12-10 10:56 Fabian Groffen
2018-03-08 20:01 Markus Meier
2017-06-27 13:30 Fabian Groffen
2017-05-16  6:35 Fabian Groffen
2017-03-29  7:24 Fabian Groffen
2016-02-22 10:25 Patrice Clement

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=1513940672.bd68b762f17880871e949916b727c8e791c63593.grobian@gentoo \
    --to=grobian@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