From: "Brett Alcox" <brettalcox@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: sys-apps/mission-center/
Date: Tue, 17 Oct 2023 02:43:50 +0000 (UTC) [thread overview]
Message-ID: <1697510590.3df453b5dde93bc54c16a2a113eced09937df4bb.brettalcox@gentoo> (raw)
commit: 3df453b5dde93bc54c16a2a113eced09937df4bb
Author: brettalcox <brettalcox <AT> gmail <DOT> com>
AuthorDate: Tue Oct 17 02:43:10 2023 +0000
Commit: Brett Alcox <brettalcox <AT> gmail <DOT> com>
CommitDate: Tue Oct 17 02:43:10 2023 +0000
URL: https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=3df453b5
sys-apps/mission-center: fixing broken debug build
Signed-off-by: brettalcox <brettalcox <AT> gmail.com>
sys-apps/mission-center/mission-center-0.3.3.ebuild | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/sys-apps/mission-center/mission-center-0.3.3.ebuild b/sys-apps/mission-center/mission-center-0.3.3.ebuild
index 76cfc83f34..66ca90aa98 100644
--- a/sys-apps/mission-center/mission-center-0.3.3.ebuild
+++ b/sys-apps/mission-center/mission-center-0.3.3.ebuild
@@ -364,14 +364,17 @@ BDEPEND="
src_unpack() {
unpack ${P}.tar.bz2
unpack nvtop-${NVTOP_COMMIT}.tar.gz
- mkdir -p "${BUILD_DIR}/src/sys_info_v2/gatherer/src/release/build/native" || die
- mv nvtop-${NVTOP_COMMIT} "${BUILD_DIR}/src/sys_info_v2/gatherer/src/release/build/native" || die
+
+ GATHERER_BUILD_DIR=$(usex debug debug release)
+ mkdir -p "${BUILD_DIR}/src/sys_info_v2/gatherer/src/${GATHERER_BUILD_DIR}/build/native" || die
+ mv nvtop-${NVTOP_COMMIT} "${BUILD_DIR}/src/sys_info_v2/gatherer/src/${GATHERER_BUILD_DIR}/build/native" || die
cargo_src_unpack
}
src_prepare() {
eapply_user
- cd "${BUILD_DIR}/src/sys_info_v2/gatherer/src/release/build/native/nvtop-${NVTOP_COMMIT}" || die
+ GATHERER_BUILD_DIR=$(usex debug debug release)
+ cd "${BUILD_DIR}/src/sys_info_v2/gatherer/src/${GATHERER_BUILD_DIR}/build/native/nvtop-${NVTOP_COMMIT}" || die
find "${S}/src/sys_info_v2/gatherer/3rdparty/nvtop/patches" -type f -name 'nvtop-*' -exec sh -c 'patch -p1 < {}' \; || die
}
next reply other threads:[~2023-10-17 2:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 2:43 Brett Alcox [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-03 15:48 [gentoo-commits] repo/proj/guru:dev commit in: sys-apps/mission-center/ Brett Alcox
2024-09-10 16:10 Takuya Wakazono
2024-09-08 14:29 Takuya Wakazono
2024-09-08 14:29 Takuya Wakazono
2024-09-07 21:42 Blake Batson
2024-05-11 0:46 Brett Alcox
2024-02-11 14:15 Brett Alcox
2023-12-09 16:10 Brett Alcox
2023-12-08 15:15 Brett Alcox
2023-10-18 15:50 Brett Alcox
2023-10-18 13:22 Brett Alcox
2023-10-17 22:56 Brett Alcox
2023-10-14 15:02 Brett Alcox
2023-10-11 12:57 Brett Alcox
2023-10-11 2:14 Brett Alcox
2023-10-05 15:15 Brett Alcox
2023-10-04 17:05 Brett Alcox
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=1697510590.3df453b5dde93bc54c16a2a113eced09937df4bb.brettalcox@gentoo \
--to=brettalcox@gmail.com \
--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