public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "David Seifert" <soap@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-misc/lirc/
Date: Sat, 30 Jul 2016 08:31:55 +0000 (UTC)	[thread overview]
Message-ID: <1469867385.b6fc4b167abbbc56620169a1bfc845e347e0de94.soap@gentoo> (raw)

commit:     b6fc4b167abbbc56620169a1bfc845e347e0de94
Author:     Craig Andrews <candrews <AT> integralblue <DOT> com>
AuthorDate: Mon Jul 18 14:30:35 2016 +0000
Commit:     David Seifert <soap <AT> gentoo <DOT> org>
CommitDate: Sat Jul 30 08:29:45 2016 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b6fc4b16

app-misc/lirc-0.9.4a: workaround parallel make bug

Gentoo-bug: 588864
Closes: https://github.com/gentoo/gentoo/pull/1911

Signed-off-by: David Seifert <soap <AT> gentoo.org>

 app-misc/lirc/lirc-0.9.4a.ebuild | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/app-misc/lirc/lirc-0.9.4a.ebuild b/app-misc/lirc/lirc-0.9.4a.ebuild
index 63a2b92..395ddd3 100644
--- a/app-misc/lirc/lirc-0.9.4a.ebuild
+++ b/app-misc/lirc/lirc-0.9.4a.ebuild
@@ -58,6 +58,14 @@ src_configure() {
 		$(use_with X x)
 }
 
+# Defined src_compile as a workaround for a parallel make issue
+# See https://bugs.gentoo.org/show_bug.cgi?id=588864
+# and https://sourceforge.net/p/lirc/tickets/210/
+src_compile() {
+	emake lib
+	emake
+}
+
 src_install() {
 	default
 


             reply	other threads:[~2016-07-30  8:32 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-30  8:31 David Seifert [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-15 23:48 [gentoo-commits] repo/gentoo:master commit in: app-misc/lirc/ Craig Andrews
2023-06-28  7:50 Sam James
2023-04-19  9:43 Sam James
2023-04-19  9:26 Arthur Zamarin
2023-04-19  8:44 Arthur Zamarin
2023-04-19  8:29 Arthur Zamarin
2023-02-27 14:24 Craig Andrews
2022-11-29 15:58 WANG Xuerui
2022-10-17 22:39 Sam James
2022-10-16 20:45 Craig Andrews
2022-06-07 21:17 Sam James
2022-06-07 21:17 Sam James
2022-06-07 21:16 Sam James
2022-06-07 21:16 Sam James
2022-06-06  4:59 Sam James
2022-06-05 22:08 Sam James
2022-06-05 22:06 Sam James
2022-05-18 18:54 Craig Andrews
2021-05-31 20:18 Michał Górny
2020-12-11 23:10 Sergei Trofimovich
2020-12-11 23:07 Sergei Trofimovich
2020-12-03  2:19 Thomas Deutschmann
2020-12-02 23:54 Sam James
2020-11-18 17:56 Craig Andrews
2020-11-08  7:57 Sam James
2020-03-19  6:28 Michał Górny
2020-03-19  6:28 Michał Górny
2020-02-09 16:11 Michał Górny
2019-08-28 16:12 David Seifert
2019-05-20 10:56 Mikle Kolyada
2019-05-19 13:14 Thomas Deutschmann
2019-05-11 16:17 Craig Andrews
2018-10-20 12:16 Sergei Trofimovich
2018-08-18 22:36 Sergei Trofimovich
2018-08-08 21:54 Mikle Kolyada
2018-08-06 22:20 Thomas Deutschmann
2018-08-06 17:13 Craig Andrews
2018-08-01 16:38 Craig Andrews
2018-08-01 16:38 Craig Andrews
2018-07-30 18:47 Craig Andrews
2018-07-27 17:22 Craig Andrews
2018-07-26 20:16 Craig Andrews
2018-07-09 14:15 Craig Andrews
2018-07-09 14:09 Craig Andrews
2018-06-23 10:02 Pacho Ramos
2018-04-06 18:46 Craig Andrews
2018-04-06 18:46 Craig Andrews
2017-08-18 15:44 Craig Andrews
2017-06-28  9:35 Alexis Ballier
2017-03-28 22:12 Göktürk Yüksek
2017-03-04  0:55 Michael Palimaka
2017-02-21  9:29 Michał Górny
2017-02-21  8:51 Michał Górny
2016-12-30 22:03 Patrice Clement
2016-12-30 21:58 Patrice Clement
2016-08-24 10:38 Pacho Ramos
2016-07-08 11:48 Patrice Clement
2016-07-08 11:44 Patrice Clement
2016-07-08 11:38 Patrice Clement
2016-04-26 17:53 Austin English
2016-01-10 10:07 Sven Wegener
2016-01-05 11:45 Pacho Ramos
2016-01-05 11:45 Pacho Ramos

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=1469867385.b6fc4b167abbbc56620169a1bfc845e347e0de94.soap@gentoo \
    --to=soap@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