From: "Dirkjan Ochtman" <djc@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: profiles/arch/amd64/, profiles/arch/x86/, profiles/arch/arm64/
Date: Tue, 15 May 2018 11:48:10 +0000 (UTC) [thread overview]
Message-ID: <1526384824.1628a22c616867e8896346d57f11b0071d7d9e9f.djc@gentoo> (raw)
commit: 1628a22c616867e8896346d57f11b0071d7d9e9f
Author: Georgy Yakovlev <ya <AT> sysdump <DOT> net>
AuthorDate: Mon May 14 18:12:15 2018 +0000
Commit: Dirkjan Ochtman <djc <AT> gentoo <DOT> org>
CommitDate: Tue May 15 11:47:04 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1628a22c
profiles: add default llvm_targets for rust
It's not installable without user invervention
with latest changes.
!!! The ebuild selected to satisfy "dev-lang/rust" has unmet
requirements.
- dev-lang/rust-1.26.0::gentoo USE="-debug -doc (-extended) -jemalloc"
ABI_X86="(64)" LLVM_TARGETS="-AArch64 -AMDGPU -ARM -BPF -Hexagon -Lanai
-MSP430 -Mips -NVPTX -PowerPC -Sparc -SystemZ -X86 -XCore"
Treat it the same way as llvm/clang does.
Not touching musl/uclibc profiles, since they
maintain their own rust ebuild.
Fixes: https://bugs.gentoo.org/655780
profiles/arch/amd64/package.use.force | 4 ++++
profiles/arch/arm64/package.use.force | 4 ++++
profiles/arch/x86/package.use.force | 4 ++++
3 files changed, 12 insertions(+)
diff --git a/profiles/arch/amd64/package.use.force b/profiles/arch/amd64/package.use.force
index d35dfcf8dc5..eecfbb757e4 100644
--- a/profiles/arch/amd64/package.use.force
+++ b/profiles/arch/amd64/package.use.force
@@ -1,6 +1,10 @@
# Copyright 1999-2017 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
+# Georgy Yakovlev <ya@sysdump.net> (14 May 2018)
+# Force the host target to avoid dependency hell
+dev-lang/rust llvm_targets_X86
+
# NP-Hardass <NP-Hardass@gentoo.org> (23 May 2017)
# Packages with optional 64-bit variant
app-emulation/wine-vanilla -abi_x86_64
diff --git a/profiles/arch/arm64/package.use.force b/profiles/arch/arm64/package.use.force
index 35055867c2f..31226f27346 100644
--- a/profiles/arch/arm64/package.use.force
+++ b/profiles/arch/arm64/package.use.force
@@ -1,6 +1,10 @@
# Copyright 1999-2016 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
+# Georgy Yakovlev <ya@sysdump.net> (14 May 2018)
+# Force the host target to avoid dependency hell
+dev-lang/rust llvm_targets_AArch64
+
# Michał Górny <mgorny@gentoo.org> (24 Sep 2016)
# Force the host target to avoid dependency hell
sys-devel/clang llvm_targets_AArch64
diff --git a/profiles/arch/x86/package.use.force b/profiles/arch/x86/package.use.force
index 6d74f7f7c28..c234a241e4f 100644
--- a/profiles/arch/x86/package.use.force
+++ b/profiles/arch/x86/package.use.force
@@ -1,6 +1,10 @@
# Copyright 1999-2016 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
+# Georgy Yakovlev <ya@sysdump.net> (14 May 2018)
+# Force the host target to avoid dependency hell
+dev-lang/rust llvm_targets_X86
+
# Michał Górny <mgorny@gentoo.org> (24 Sep 2016)
# Force the host target to avoid dependency hell
sys-devel/clang llvm_targets_X86
reply other threads:[~2018-05-15 11:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1526384824.1628a22c616867e8896346d57f11b0071d7d9e9f.djc@gentoo \
--to=djc@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