public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Yixun Lan" <dlan@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/crash/
Date: Wed,  3 Jun 2020 03:05:48 +0000 (UTC)	[thread overview]
Message-ID: <1591153512.539abe6b27b67042f2067b3e495b30748411f79a.dlan@gentoo> (raw)

commit:     539abe6b27b67042f2067b3e495b30748411f79a
Author:     Yixun Lan <dlan <AT> gentoo <DOT> org>
AuthorDate: Wed Jun  3 02:57:13 2020 +0000
Commit:     Yixun Lan <dlan <AT> gentoo <DOT> org>
CommitDate: Wed Jun  3 03:05:12 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=539abe6b

dev-util/crash: respect CC/AR variables

Closes: https://bugs.gentoo.org/724262
Package-Manager: Portage-2.3.100, Repoman-2.3.22
Signed-off-by: Yixun Lan <dlan <AT> gentoo.org>

 dev-util/crash/crash-7.2.8-r1.ebuild | 30 ++++++++++++++++++++++++++++++
 1 file changed, 30 insertions(+)

diff --git a/dev-util/crash/crash-7.2.8-r1.ebuild b/dev-util/crash/crash-7.2.8-r1.ebuild
new file mode 100644
index 00000000000..45bbff51590
--- /dev/null
+++ b/dev-util/crash/crash-7.2.8-r1.ebuild
@@ -0,0 +1,30 @@
+# Copyright 1999-2020 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI="7"
+
+inherit toolchain-funcs
+
+DESCRIPTION="Red Hat crash utility; used for analyzing kernel core dumps"
+HOMEPAGE="https://people.redhat.com/anderson/"
+SRC_URI="https://people.redhat.com/anderson/${P}.tar.gz"
+
+LICENSE="GPL-3"
+SLOT="0"
+KEYWORDS="-* ~alpha ~amd64 ~arm ~ia64 ~ppc64 ~s390 ~x86"
+IUSE=""
+# there is no "make test" target, but there is a test.c so the automatic
+# make rules catch it and tests fail
+RESTRICT="test"
+
+src_prepare() {
+	sed -i -e "s|ar -rs|\${AR} -rs|g" Makefile || die
+	default
+}
+
+src_compile() {
+	emake \
+		CC="$(tc-getCC)" \
+		AR="$(tc-getAR)" \
+		CFLAGS="${CFLAGS}" LDFLAGS="${LDFLAGS}"
+}


             reply	other threads:[~2020-06-03  3:05 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-03  3:05 Yixun Lan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-04-29 14:17 [gentoo-commits] repo/gentoo:master commit in: dev-util/crash/ Yixun Lan
2025-04-29 14:17 Yixun Lan
2024-12-02 10:07 Yixun Lan
2024-05-09  3:05 Yixun Lan
2024-05-09  3:05 Yixun Lan
2024-03-05  6:57 Sam James
2023-11-23 12:39 Yixun Lan
2023-11-23 12:27 Yixun Lan
2023-11-23 12:27 Yixun Lan
2023-08-09 23:09 Yixun Lan
2023-05-12 12:36 Yixun Lan
2023-05-12 12:36 Yixun Lan
2022-12-19  2:40 Yixun Lan
2022-08-24 14:28 Yixun Lan
2022-08-24 14:28 Yixun Lan
2022-07-28  3:33 Yixun Lan
2022-04-27  9:08 Yixun Lan
2022-04-27  9:07 Yixun Lan
2022-04-09 10:59 Yixun Lan
2022-04-09  2:35 Sam James
2022-04-02 10:59 Yixun Lan
2022-04-02  8:24 Yixun Lan
2022-04-02  8:24 Yixun Lan
2021-12-21  8:41 Yixun Lan
2021-12-21  2:26 Yixun Lan
2021-12-21  2:26 Yixun Lan
2021-05-15  9:02 Yixun Lan
2021-01-26  3:41 Yixun Lan
2021-01-26  3:41 Yixun Lan
2021-01-15 21:28 Yixun Lan
2020-06-03  3:05 Yixun Lan
2020-02-16 14:27 Yixun Lan
2019-10-21  1:39 Yixun Lan
2019-10-21  0:01 Thomas Deutschmann
2019-10-20  6:19 Yixun Lan
2019-10-20  1:08 Yixun Lan
2019-04-09  0:02 Doug Goldstein
2018-03-10 21:44 Doug Goldstein
2017-05-10  7:28 Yixun Lan
2016-04-21  4:51 Mike Frysinger

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=1591153512.539abe6b27b67042f2067b3e495b30748411f79a.dlan@gentoo \
    --to=dlan@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