From: "Ionen Wolkens" <ionen@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: x11-misc/xcalendar/
Date: Tue, 11 Oct 2022 08:56:35 +0000 (UTC) [thread overview]
Message-ID: <1665478563.f7ea685a290d32a4fbb3f3422a4facf307dcbd61.ionen@gentoo> (raw)
commit: f7ea685a290d32a4fbb3f3422a4facf307dcbd61
Author: Ionen Wolkens <ionen <AT> gentoo <DOT> org>
AuthorDate: Tue Oct 11 08:27:17 2022 +0000
Commit: Ionen Wolkens <ionen <AT> gentoo <DOT> org>
CommitDate: Tue Oct 11 08:56:03 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f7ea685a
x11-misc/xcalendar: pass -std=gnu89
Does not build with `clang -std=c2x`, early workaround for
when this will become a default.
(not actively hunting for these, merely revisiting packages
previously looked at for clang16 even if not an issue "yet").
Signed-off-by: Ionen Wolkens <ionen <AT> gentoo.org>
x11-misc/xcalendar/xcalendar-4.0-r3.ebuild | 1 +
1 file changed, 1 insertion(+)
diff --git a/x11-misc/xcalendar/xcalendar-4.0-r3.ebuild b/x11-misc/xcalendar/xcalendar-4.0-r3.ebuild
index e400aa3e3cdc..77be8a1f274a 100644
--- a/x11-misc/xcalendar/xcalendar-4.0-r3.ebuild
+++ b/x11-misc/xcalendar/xcalendar-4.0-r3.ebuild
@@ -42,6 +42,7 @@ src_prepare() {
src_compile() {
tc-export CC
+ append-cflags -std=gnu89 # old codebase, incompatible with c2x
if use motif; then
append-cppflags $($(tc-getPKG_CONFIG) --cflags x11 xmu xt || die)
next reply other threads:[~2022-10-11 8:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 8:56 Ionen Wolkens [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-04-15 6:39 [gentoo-commits] repo/gentoo:master commit in: x11-misc/xcalendar/ Joonas Niilola
2020-05-14 22:25 Aaron Bauman
2017-04-13 19:28 Patrice Clement
2017-04-04 19:28 Tobias Klausmann
2017-03-22 7:30 Michael Weber
2017-03-21 10:08 Michael Weber
2017-03-20 11:04 Agostino Sarubbo
2017-02-21 8:14 David Seifert
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=1665478563.f7ea685a290d32a4fbb3f3422a4facf307dcbd61.ionen@gentoo \
--to=ionen@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