From: "Robin H. Johnson" <robbat2@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-metrics/node_exporter/
Date: Sun, 26 Nov 2023 21:47:39 +0000 (UTC) [thread overview]
Message-ID: <1701035256.9bd2a2d610a131178d15bc55f1c5ef2c7bd63f5f.robbat2@gentoo> (raw)
commit: 9bd2a2d610a131178d15bc55f1c5ef2c7bd63f5f
Author: Robin H. Johnson <robbat2 <AT> gentoo <DOT> org>
AuthorDate: Sun Nov 26 21:47:01 2023 +0000
Commit: Robin H. Johnson <robbat2 <AT> gentoo <DOT> org>
CommitDate: Sun Nov 26 21:47:36 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9bd2a2d6
app-metrics/node_exporter: workaround bug #917577 for x86 builds
Signed-off-by: Robin H. Johnson <robbat2 <AT> gentoo.org>
Bug: https://bugs.gentoo.org/917577
app-metrics/node_exporter/node_exporter-1.7.0.ebuild | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/app-metrics/node_exporter/node_exporter-1.7.0.ebuild b/app-metrics/node_exporter/node_exporter-1.7.0.ebuild
index e02032dc5f61..8e9236baea4d 100644
--- a/app-metrics/node_exporter/node_exporter-1.7.0.ebuild
+++ b/app-metrics/node_exporter/node_exporter-1.7.0.ebuild
@@ -51,6 +51,10 @@ src_unpack() {
}
src_compile() {
+ if use x86; then
+ #917577 pie breaks build on x86
+ GOFLAGS=${GOFLAGS//-buildmode=pie}
+ fi
promu build -v || die
./"${PN}" --help-man > "${PN}".1 || die
}
next reply other threads:[~2023-11-26 21:47 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-26 21:47 Robin H. Johnson [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-15 18:14 [gentoo-commits] repo/gentoo:master commit in: app-metrics/node_exporter/ Arthur Zamarin
2025-01-19 15:50 Arthur Zamarin
2025-01-19 14:55 Sam James
2025-01-19 13:10 Arthur Zamarin
2025-01-18 0:30 Jakov Smolić
2025-01-17 19:29 Arthur Zamarin
2024-12-19 15:41 William Hubbs
2024-06-15 19:21 Arthur Zamarin
2024-05-08 16:00 Arthur Zamarin
2024-01-19 18:11 William Hubbs
2024-01-07 6:48 Joonas Niilola
2024-01-07 6:14 Sam James
2023-11-24 12:28 Sam James
2023-09-18 9:55 WANG Xuerui
2023-05-25 16:53 William Hubbs
2023-02-04 19:11 William Hubbs
2023-02-04 19:11 William Hubbs
2022-12-26 5:54 Kenton Groombridge
2022-07-22 23:37 William Hubbs
2022-07-22 23:33 William Hubbs
2022-07-18 2:23 William Hubbs
2022-06-29 7:21 WANG Xuerui
2022-04-05 21:53 Sam James
2022-04-05 21:50 Sam James
2022-01-21 19:13 Sam James
2021-08-25 20:38 Robin H. Johnson
2021-08-15 8:28 Mikle Kolyada
2021-07-16 15:17 Mikle Kolyada
2021-05-12 19:36 Mikle Kolyada
2021-04-07 8:59 Mikle Kolyada
2021-03-09 17:25 William Hubbs
2020-08-08 17:08 Matthew Thode
2020-08-08 17:08 Matthew Thode
2019-12-04 5:34 William Hubbs
2019-12-03 9:48 Michał Górny
2019-11-23 11:06 Manuel Rüger
2019-11-23 11:06 Manuel Rüger
2019-07-15 23:05 Manuel Rüger
2019-06-05 15:08 Manuel Rüger
2019-06-05 15:08 Manuel Rüger
2019-05-10 8:41 Manuel Rüger
2019-05-10 8:41 Manuel Rüger
2019-02-14 12:44 Manuel Rüger
2019-02-14 12:31 Manuel Rüger
2019-02-14 12:31 Manuel Rüger
2018-12-02 0:32 Manuel Rüger
2018-12-02 0:32 Manuel Rüger
2018-10-29 15:27 Tobias Klausmann
2018-07-17 16:44 Manuel Rüger
2018-05-15 20:01 Manuel Rüger
2018-04-27 22:04 Manuel Rüger
2018-04-27 22:03 Manuel Rüger
2018-04-18 14:39 Manuel Rüger
2018-04-10 12:28 Manuel Rüger
2018-03-30 14:31 Manuel Rüger
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=1701035256.9bd2a2d610a131178d15bc55f1c5ef2c7bd63f5f.robbat2@gentoo \
--to=robbat2@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