From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-crypt/mcrypt/
Date: Tue, 26 Nov 2024 02:56:01 +0000 (UTC) [thread overview]
Message-ID: <1732589725.10a63c37c1de76f654b504d9d8650270a030da4a.sam@gentoo> (raw)
commit: 10a63c37c1de76f654b504d9d8650270a030da4a
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Tue Nov 26 02:54:56 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Nov 26 02:55:25 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=10a63c37
app-crypt/mcrypt: build w/ -std=gnu17
We already apply a bunch of patches, not worth adding another for this.
Closes: https://bugs.gentoo.org/943960
Signed-off-by: Sam James <sam <AT> gentoo.org>
app-crypt/mcrypt/mcrypt-2.6.8-r3.ebuild | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/app-crypt/mcrypt/mcrypt-2.6.8-r3.ebuild b/app-crypt/mcrypt/mcrypt-2.6.8-r3.ebuild
index c22efa90f5b7..499e2efbd242 100644
--- a/app-crypt/mcrypt/mcrypt-2.6.8-r3.ebuild
+++ b/app-crypt/mcrypt/mcrypt-2.6.8-r3.ebuild
@@ -3,6 +3,8 @@
EAPI=7
+inherit flag-o-matic
+
DESCRIPTION="Replacement of the old unix crypt(1)"
HOMEPAGE="https://mcrypt.sourceforge.net/"
SRC_URI="https://downloads.sourceforge.net/mcrypt/${P}.tar.gz"
@@ -27,5 +29,8 @@ PATCHES=(
)
src_configure() {
+ # bug #943960
+ append-cflags -std=gnu17
+
econf $(use_enable nls)
}
next reply other threads:[~2024-11-26 2:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-26 2:56 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-19 10:19 [gentoo-commits] repo/gentoo:master commit in: app-crypt/mcrypt/ Ulrich Müller
2021-01-06 12:55 Fabian Groffen
2020-01-28 8:24 Joonas Niilola
2017-03-15 18:29 Alon Bar-Lev
2017-03-15 14:35 Michael Weber
2017-03-04 14:02 Agostino Sarubbo
2017-03-04 13:38 Agostino Sarubbo
2017-01-13 23:32 Alon Bar-Lev
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=1732589725.10a63c37c1de76f654b504d9d8650270a030da4a.sam@gentoo \
--to=sam@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