From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-libs/nas/
Date: Wed, 15 Jan 2025 23:16:08 +0000 (UTC) [thread overview]
Message-ID: <1736982909.789e82b5e0baae616ec7dc6b4aa20cf0a0cc8e45.sam@gentoo> (raw)
commit: 789e82b5e0baae616ec7dc6b4aa20cf0a0cc8e45
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed Jan 15 23:15:09 2025 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Jan 15 23:15:09 2025 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=789e82b5
media-libs/nas: fix build issues
* Build w/ -std=gnu89 (ancient configure, not C23 compatible either)
* Ignore MAKEOPTS/GNUMAKEFLAGS as it confuses imake
Closes: https://bugs.gentoo.org/899834
Closes: https://bugs.gentoo.org/944403
Closes: https://bugs.gentoo.org/944451
Closes: https://bugs.gentoo.org/947416
Signed-off-by: Sam James <sam <AT> gentoo.org>
media-libs/nas/nas-1.9.5-r2.ebuild | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/media-libs/nas/nas-1.9.5-r2.ebuild b/media-libs/nas/nas-1.9.5-r2.ebuild
index 8fb0b91a04be..e548bf7f0d89 100644
--- a/media-libs/nas/nas-1.9.5-r2.ebuild
+++ b/media-libs/nas/nas-1.9.5-r2.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2024 Gentoo Authors
+# Copyright 1999-2025 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=8
@@ -50,6 +50,9 @@ src_prepare() {
}
multilib_src_configure() {
+ # Ancient configure and relies on imake, not worth it
+ append-cflags -std=gnu89
+
# -Werror=lto-type-mismatch
# https://bugs.gentoo.org/859934
# https://sourceforge.net/p/nas/bugs/13/
@@ -60,6 +63,9 @@ multilib_src_configure() {
econf
popd || die
+ # bug #947416
+ unset MAKEOPTS GNUMAKEFLAGS
+
local cpp=($(get_abi_CHOST ${DEFAULT_ABI})-gcc $(get_abi_CFLAGS) -E) #884203
CC="$(tc-getBUILD_CC)" LD="$(tc-getLD)" \
IMAKECPP="${IMAKECPP:-${cpp[*]}}" \
next reply other threads:[~2025-01-15 23:16 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 23:16 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-27 18:40 [gentoo-commits] repo/gentoo:master commit in: media-libs/nas/ Andreas K. Hüttel
2024-08-10 5:27 Michał Górny
2024-08-09 8:50 Jakov Smolić
2024-06-30 17:31 Sam James
2024-06-30 17:31 Sam James
2024-06-30 17:31 Sam James
2024-06-30 12:22 Sam James
2024-06-30 12:22 Sam James
2024-06-30 11:29 Miroslav Šulc
2024-03-20 6:26 Sam James
2022-12-04 5:38 Ionen Wolkens
2022-03-18 8:22 Arthur Zamarin
2022-03-16 8:13 Jakov Smolić
2022-03-15 12:33 Jakov Smolić
2022-03-15 9:39 Jakov Smolić
2022-03-15 7:41 Agostino Sarubbo
2022-03-15 7:41 Agostino Sarubbo
2022-03-15 7:40 Agostino Sarubbo
2022-02-04 8:45 Miroslav Šulc
2019-05-15 1:04 Aaron Bauman
2019-04-20 7:47 Sergei Trofimovich
2018-10-05 5:48 Andreas Sturmlechner
2018-10-05 4:56 Markus Meier
2018-09-15 2:31 Andreas Sturmlechner
2018-09-14 10:18 Tobias Klausmann
2018-08-25 18:55 Sergei Trofimovich
2018-08-25 18:25 Sergei Trofimovich
2018-08-25 18:11 Sergei Trofimovich
2018-08-23 20:13 Sergei Trofimovich
2018-08-23 2:35 Mikle Kolyada
2018-08-23 1:41 Thomas Deutschmann
2017-06-19 11:42 Alexis Ballier
2017-06-19 10:59 Alexis Ballier
2015-09-12 9:46 Jeroen Roovers
2015-09-05 17:15 Anthony G. Basile
2015-09-05 17:12 Mikle Kolyada
2015-08-30 15:38 Tobias Klausmann
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=1736982909.789e82b5e0baae616ec7dc6b4aa20cf0a0cc8e45.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