From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sci-libs/superlu/
Date: Mon, 10 Feb 2025 08:56:48 +0000 (UTC) [thread overview]
Message-ID: <1739177556.c6fd1d70702a9bb45a5a3e30ae0a437360f2d6b1.sam@gentoo> (raw)
commit: c6fd1d70702a9bb45a5a3e30ae0a437360f2d6b1
Author: NHOrus <jy6x2b32pie9 <AT> yahoo <DOT> com>
AuthorDate: Mon Jan 27 08:17:04 2025 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Feb 10 08:52:36 2025 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c6fd1d70
sci-libs/superlu: update EAPI 7 -> 8, fix C version on gnu89
We have a newer package where woes of modern C are solved.
This one for dependencies.
Closes: https://bugs.gentoo.org/926310
Closes: https://bugs.gentoo.org/948886
Signed-off-by: NHOrus <jy6x2b32pie9 <AT> yahoo.com>
Closes: https://github.com/gentoo/gentoo/pull/40328
Signed-off-by: Sam James <sam <AT> gentoo.org>
sci-libs/superlu/{superlu-4.3-r3.ebuild => superlu-4.3-r4.ebuild} | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/sci-libs/superlu/superlu-4.3-r3.ebuild b/sci-libs/superlu/superlu-4.3-r4.ebuild
similarity index 92%
rename from sci-libs/superlu/superlu-4.3-r3.ebuild
rename to sci-libs/superlu/superlu-4.3-r4.ebuild
index 028c3d805d0c..3d6ee03311d3 100644
--- a/sci-libs/superlu/superlu-4.3-r3.ebuild
+++ b/sci-libs/superlu/superlu-4.3-r4.ebuild
@@ -1,9 +1,9 @@
-# Copyright 1999-2022 Gentoo Authors
+# Copyright 1999-2025 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
-EAPI=7
+EAPI=8
-inherit autotools fortran-2 multilib toolchain-funcs
+inherit autotools fortran-2 multilib toolchain-funcs flag-o-matic
MY_PN=SuperLU
@@ -33,6 +33,7 @@ PATCHES=(
src_prepare() {
unset VERBOSE
+ append-cflags -std=gnu89
sed \
-e "s:= ar:= $(tc-getAR):g" \
-e "s:= ranlib:= $(tc-getRANLIB):g" \
next reply other threads:[~2025-02-10 8:57 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 8:56 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-24 19:55 [gentoo-commits] repo/gentoo:master commit in: sci-libs/superlu/ Sam James
2023-06-03 11:15 Arthur Zamarin
2022-12-04 9:23 WANG Xuerui
2022-08-25 0:53 Sam James
2021-11-09 21:41 Jakov Smolić
2021-11-09 21:37 Sam James
2021-11-09 21:36 Sam James
2021-11-09 21:35 Sam James
2021-11-09 21:35 Sam James
2021-11-09 21:34 Sam James
2021-11-09 13:48 Jakov Smolić
2021-10-24 21:14 Sam James
2021-10-12 22:23 Marek Szuba
2021-10-04 19:33 Jakov Smolić
2021-10-04 19:33 Jakov Smolić
2021-10-02 23:17 Sam James
2021-07-14 16:15 Marek Szuba
2021-01-05 22:55 Sam James
2021-01-05 22:51 Sam James
2021-01-05 22:32 Sam James
2021-01-05 21:09 Sam James
2021-01-05 20:51 Sam James
2021-01-03 12:10 Sergei Trofimovich
2021-01-03 11:51 Sergei Trofimovich
2020-12-29 17:14 Sam James
2019-02-27 4:25 Aaron Bauman
2018-08-22 0:35 Mikle Kolyada
2018-08-18 22:36 Sergei Trofimovich
2017-11-27 19:46 Sergei Trofimovich
2017-10-16 3:34 David Seifert
2017-07-30 10:04 Michał Górny
2017-07-08 9:25 Alexis Ballier
2017-07-01 9:52 Sergei Trofimovich
2017-04-29 12:42 Jeroen Roovers
2016-12-22 15:40 Sebastien Fabbro
2016-12-19 23:51 Sebastien Fabbro
2016-06-07 16:47 Tobias Klausmann
2015-11-10 19:06 Markus Meier
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=1739177556.c6fd1d70702a9bb45a5a3e30ae0a437360f2d6b1.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