public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Tiziano Müller" <dev-zero@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-devel/dwz/
Date: Sat, 13 Apr 2019 10:36:54 +0000 (UTC)	[thread overview]
Message-ID: <1555151794.1f0a334057d92489c4f2749085194910767653da.dev-zero@gentoo> (raw)

commit:     1f0a334057d92489c4f2749085194910767653da
Author:     Tiziano Müller <dev-zero <AT> gentoo <DOT> org>
AuthorDate: Sat Apr 13 10:33:27 2019 +0000
Commit:     Tiziano Müller <dev-zero <AT> gentoo <DOT> org>
CommitDate: Sat Apr 13 10:36:34 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1f0a3340

sys-devel/dwz: fix calling cc directly

Closes: https://bugs.gentoo.org/683024
Package-Manager: Portage-2.3.62, Repoman-2.3.12
Signed-off-by: Tiziano Müller <dev-zero <AT> gentoo.org>

 sys-devel/dwz/dwz-0.12-r1.ebuild | 29 +++++++++++++++++++++++++++++
 1 file changed, 29 insertions(+)

diff --git a/sys-devel/dwz/dwz-0.12-r1.ebuild b/sys-devel/dwz/dwz-0.12-r1.ebuild
new file mode 100644
index 00000000000..9926eba6d80
--- /dev/null
+++ b/sys-devel/dwz/dwz-0.12-r1.ebuild
@@ -0,0 +1,29 @@
+# Copyright 1999-2019 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=7
+
+inherit toolchain-funcs
+
+FPKG_HASH="1624afa75b94633e03c6e1bb952fb348"
+
+DESCRIPTION="DWARF optimization and duplicate removal tool"
+HOMEPAGE="https://sourceware.org/git/?p=dwz.git;a=summary"
+SRC_URI="https://src.fedoraproject.org/repo/pkgs/dwz/${P}.tar.bz2/${FPKG_HASH}/${P}.tar.bz2"
+
+LICENSE="GPL-2+ GPL-3+"
+SLOT="0"
+KEYWORDS="~amd64"
+IUSE=""
+
+DEPEND="dev-libs/elfutils"
+RDEPEND="${DEPEND}"
+BDEPEND=""
+
+src_prepare() {
+	default
+	sed -i \
+		-e '/^CFLAGS/d' \
+		Makefile || die "sed failed"
+	tc-export CC
+}


             reply	other threads:[~2019-04-13 10:36 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-13 10:36 Tiziano Müller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-01-26  2:01 [gentoo-commits] repo/gentoo:master commit in: sys-devel/dwz/ Sam James
2025-01-26  1:56 Sam James
2025-01-25 14:17 Sam James
2025-01-25 14:15 Sam James
2025-01-25 14:15 Sam James
2025-01-25 13:50 Sam James
2025-01-25 13:43 Sam James
2025-01-07  2:24 Sam James
2025-01-07  2:01 Sam James
2025-01-07  2:01 Sam James
2025-01-05 12:32 WANG Xuerui
2025-01-05 12:32 WANG Xuerui
2024-12-14 10:43 Sam James
2024-12-14 10:43 Sam James
2024-08-31  1:08 Sam James
2024-02-21  2:15 Sam James
2024-02-03 23:23 Jakov Smolić
2024-02-03 21:34 Sam James
2024-02-03 14:19 Arthur Zamarin
2024-02-03 11:32 Arthur Zamarin
2024-02-03 11:07 Sam James
2024-02-03 11:05 Arthur Zamarin
2024-02-03 11:05 Arthur Zamarin
2024-02-03 11:03 Arthur Zamarin
2024-02-03 10:21 Arthur Zamarin
2024-02-03  8:22 Arthur Zamarin
2024-02-03  8:22 Arthur Zamarin
2024-02-03  8:22 Arthur Zamarin
2024-02-03  8:22 Arthur Zamarin
2023-11-29  4:23 Sam James
2023-03-19 20:51 Arsen Arsenović
2023-03-19 20:51 Arsen Arsenović
2023-03-19 15:25 Arsen Arsenović
2021-11-30  7:27 Joonas Niilola
2021-11-30  7:27 Joonas Niilola
2021-11-30  7:27 Joonas Niilola
2020-09-23 21:54 Conrad Kostecki
2020-09-22 21:19 Conrad Kostecki
2020-09-22 21:19 Conrad Kostecki
2019-04-13 10:36 Tiziano Müller
2018-07-15 20:30 Tiziano Müller

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=1555151794.1f0a334057d92489c4f2749085194910767653da.dev-zero@gentoo \
    --to=dev-zero@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