From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-vcs/cvs/
Date: Sun, 16 Feb 2025 13:02:50 +0000 (UTC) [thread overview]
Message-ID: <1739710201.1a88f3abcb27749e709314a3a3903c5918cb6194.sam@gentoo> (raw)
commit: 1a88f3abcb27749e709314a3a3903c5918cb6194
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 16 12:49:27 2025 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Feb 16 12:50:01 2025 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1a88f3ab
dev-vcs/cvs: build w/ -std=gnu17
It's a miracle it builds at all and it was quite the mission to get
it ported to C99 for which we're still carrying patches. Dead upstream.
Closes: https://bugs.gentoo.org/943853
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-vcs/cvs/cvs-1.12.12-r15.ebuild | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/dev-vcs/cvs/cvs-1.12.12-r15.ebuild b/dev-vcs/cvs/cvs-1.12.12-r15.ebuild
index 1e8235508d99..0dd5d741cfb6 100644
--- a/dev-vcs/cvs/cvs-1.12.12-r15.ebuild
+++ b/dev-vcs/cvs/cvs-1.12.12-r15.ebuild
@@ -1,9 +1,9 @@
-# Copyright 1999-2024 Gentoo Authors
+# Copyright 1999-2025 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=8
-inherit autotools pam toolchain-funcs
+inherit autotools flag-o-matic pam toolchain-funcs
DESCRIPTION="Concurrent Versions System - source code revision control tools"
HOMEPAGE="https://cvs.nongnu.org/"
@@ -67,6 +67,9 @@ src_prepare() {
}
src_configure() {
+ # bug #943853
+ append-cflags -std=gnu17
+
if tc-is-cross-compiler ; then
# Sane defaults when cross-compiling (as these tests want to
# try and execute code).
next reply other threads:[~2025-02-16 13:02 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-16 13:02 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-16 13:42 [gentoo-commits] repo/gentoo:master commit in: dev-vcs/cvs/ Sam James
2024-11-03 0:47 Andreas K. Hüttel
2024-10-31 13:51 Sam James
2024-10-30 15:46 Arthur Zamarin
2024-10-28 21:30 Sam James
2024-10-27 2:09 Sam James
2024-10-27 2:09 Sam James
2024-10-27 2:07 Sam James
2024-10-27 2:07 Sam James
2024-05-20 21:59 Sam James
2024-05-20 21:58 Sam James
2024-05-20 21:58 Sam James
2023-06-28 7:37 Sam James
2022-06-16 16:30 Sam James
2021-06-30 18:40 Sam James
2021-01-24 10:24 Mikle Kolyada
2021-01-06 22:58 Fabian Groffen
2020-12-27 16:38 Fabian Groffen
2019-10-12 19:13 Mikle Kolyada
2019-07-29 13:04 Aaron Bauman
2019-06-12 17:08 Michael Haubenwallner
2019-01-27 16:53 Pacho Ramos
2018-06-03 19:38 Mikle Kolyada
2017-12-01 18:06 Fabian Groffen
2017-09-24 19:57 Sergei Trofimovich
2017-09-24 11:00 Sergei Trofimovich
2017-09-11 21:52 Sergei Trofimovich
2017-09-10 19:47 Sergei Trofimovich
2017-09-07 19:41 Markus Meier
2017-09-04 7:30 Tobias Klausmann
2017-09-02 19:08 Aaron Bauman
2017-09-02 19:08 Aaron Bauman
2017-08-30 21:42 Sergei Trofimovich
2017-08-30 18:41 Pacho Ramos
2017-08-30 13:15 Pacho Ramos
2017-08-14 6:37 Michał Górny
2017-04-09 20:05 Andreas Hüttel
2017-01-09 13:47 Jeroen Roovers
2016-11-29 17:18 Markus Meier
2016-11-23 9:20 Tobias Klausmann
2016-11-20 13:08 Agostino Sarubbo
2016-11-20 13:04 Agostino Sarubbo
2016-06-27 22:11 Robin H. Johnson
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=1739710201.1a88f3abcb27749e709314a3a3903c5918cb6194.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