public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Ionen Wolkens" <ionen@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: x11-misc/dclock/
Date: Tue, 11 Oct 2022 08:56:34 +0000 (UTC)	[thread overview]
Message-ID: <1665478563.9dc96ba4b5fe632eb7239f1f8b7a58ff3f2d4078.ionen@gentoo> (raw)

commit:     9dc96ba4b5fe632eb7239f1f8b7a58ff3f2d4078
Author:     Ionen Wolkens <ionen <AT> gentoo <DOT> org>
AuthorDate: Tue Oct 11 08:26:34 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=9dc96ba4

x11-misc/dclock: 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/dclock/dclock-2.2.2_p12.ebuild | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/x11-misc/dclock/dclock-2.2.2_p12.ebuild b/x11-misc/dclock/dclock-2.2.2_p12.ebuild
index 40e1bc5b5574..6ff7ea856b37 100644
--- a/x11-misc/dclock/dclock-2.2.2_p12.ebuild
+++ b/x11-misc/dclock/dclock-2.2.2_p12.ebuild
@@ -45,6 +45,8 @@ src_prepare() {
 }
 
 src_configure() {
+	append-cflags -std=gnu89 # old codebase, incompatible with c2x
+
 	if use xft; then
 		append-cppflags \
 			-DXFT_SUPPORT \


             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 --
2022-09-30 11:02 [gentoo-commits] repo/gentoo:master commit in: x11-misc/dclock/ Ionen Wolkens
2021-04-15  6:39 Joonas Niilola
2021-03-15 21:25 Sam James
2021-03-15 21:21 Sam James
2021-03-15 21:18 Sam James
2020-09-04  8:12 Jeroen Roovers
2017-09-23  6:46 Jeroen Roovers
2017-02-21  6:29 Jeroen Roovers

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.9dc96ba4b5fe632eb7239f1f8b7a58ff3f2d4078.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