From: "Tony Vroon" <chainsaw@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-wireless/rfkill/
Date: Tue, 27 Sep 2016 13:13:48 +0000 (UTC) [thread overview]
Message-ID: <1474982025.68aa66b89f2d32b8bff55056ac18befaa1d2a74a.chainsaw@gentoo> (raw)
commit: 68aa66b89f2d32b8bff55056ac18befaa1d2a74a
Author: Tony Vroon <chainsaw <AT> gentoo <DOT> org>
AuthorDate: Tue Sep 27 13:13:19 2016 +0000
Commit: Tony Vroon <chainsaw <AT> gentoo <DOT> org>
CommitDate: Tue Sep 27 13:13:45 2016 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=68aa66b8
net-wireless/rfkill: Do not set toolchain variables in global scope; closes bug #593408 by Michał Górny.
Package-Manager: portage-2.3.1
net-wireless/rfkill/rfkill-0.5.ebuild | 9 +++------
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/net-wireless/rfkill/rfkill-0.5.ebuild b/net-wireless/rfkill/rfkill-0.5.ebuild
index 248b232..4453dc7 100644
--- a/net-wireless/rfkill/rfkill-0.5.ebuild
+++ b/net-wireless/rfkill/rfkill-0.5.ebuild
@@ -1,8 +1,8 @@
-# Copyright 1999-2013 Gentoo Foundation
+# Copyright 1999-2016 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Id$
-EAPI=5
+EAPI=6
inherit toolchain-funcs
@@ -18,11 +18,8 @@ IUSE=""
RDEPEND=""
DEPEND=""
-CC=$(tc-getCC)
-LD=$(tc-getLD)
-
src_compile() {
- emake V=1 || die "Failed to compile"
+ emake CC=$(tc-getCC) LD=$(tc-getLD) V=1 || die "Failed to compile"
}
src_install() {
next reply other threads:[~2016-09-27 13:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-27 13:13 Tony Vroon [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-10-05 19:35 [gentoo-commits] repo/gentoo:master commit in: net-wireless/rfkill/ Jeroen Roovers
2016-10-14 6:50 Patrice Clement
2017-10-23 11:17 Lars Wendler
2017-10-23 12:47 Lars Wendler
2021-02-17 19:13 Rick Farina
2021-05-31 20:45 David Seifert
2022-03-20 0:38 Sam James
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=1474982025.68aa66b89f2d32b8bff55056ac18befaa1d2a74a.chainsaw@gentoo \
--to=chainsaw@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