From: "Andreas K. Hüttel" <dilfridge@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/riscv:master commit in: profiles/arch/riscv/
Date: Sat, 20 Apr 2019 18:20:54 +0000 (UTC) [thread overview]
Message-ID: <1555784420.dfd270cc3975c78f11b40685a10fad9ad927d1ce.dilfridge@gentoo> (raw)
commit: dfd270cc3975c78f11b40685a10fad9ad927d1ce
Author: Andreas K. Hüttel <dilfridge <AT> gentoo <DOT> org>
AuthorDate: Sat Apr 20 18:20:20 2019 +0000
Commit: Andreas K. Hüttel <dilfridge <AT> gentoo <DOT> org>
CommitDate: Sat Apr 20 18:20:20 2019 +0000
URL: https://gitweb.gentoo.org/proj/riscv.git/commit/?id=dfd270cc
profiles: No Python 2 here, since it has lots of trouble with two-stage libdir
Signed-off-by: Andreas K. Hüttel <dilfridge <AT> gentoo.org>
profiles/arch/riscv/use.mask | 3 +++
1 file changed, 3 insertions(+)
diff --git a/profiles/arch/riscv/use.mask b/profiles/arch/riscv/use.mask
index 1898783..840b97a 100644
--- a/profiles/arch/riscv/use.mask
+++ b/profiles/arch/riscv/use.mask
@@ -1,2 +1,5 @@
# The required library has not been ported to riscv yet.
seccomp
+
+# Python 2 has a lot of trouble with the two-level libdir.
+python_targets_python2_7
next reply other threads:[~2019-04-20 23:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-20 18:20 Andreas K. Hüttel [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-04-28 19:39 [gentoo-commits] proj/riscv:master commit in: profiles/arch/riscv/ Andreas K. Hüttel
2019-04-28 10:05 Andreas K. Hüttel
2019-04-27 20:03 Andreas K. Hüttel
2019-04-27 19:59 Andreas K. Hüttel
2019-04-21 10:34 Andreas K. Hüttel
2019-04-20 23:37 Andreas K. Hüttel
2019-04-20 18:22 Andreas K. Hüttel
2019-04-20 17:30 Andreas K. Hüttel
2019-04-20 17:28 Andreas K. Hüttel
2019-04-20 17:25 Andreas K. Hüttel
2019-04-20 17:23 Andreas K. Hüttel
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=1555784420.dfd270cc3975c78f11b40685a10fad9ad927d1ce.dilfridge@gentoo \
--to=dilfridge@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