From: "Alexis Ballier" <aballier@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: profiles/arch/amd64-fbsd/clang/
Date: Mon, 3 Oct 2016 17:03:07 +0000 (UTC) [thread overview]
Message-ID: <1475514132.ab7fc44e73fa6e50494d90fe57deb1e283f191d0.aballier@gentoo> (raw)
commit: ab7fc44e73fa6e50494d90fe57deb1e283f191d0
Author: Yuta Satoh <nigoro.dev <AT> gmail <DOT> com>
AuthorDate: Sun Oct 2 09:03:17 2016 +0000
Commit: Alexis Ballier <aballier <AT> gentoo <DOT> org>
CommitDate: Mon Oct 3 17:02:12 2016 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ab7fc44e
profiles/arch/amd64-fbsd/clang: add some variables for clang support.
https://bugs.gentoo.org/show_bug.cgi?id=595878
profiles/arch/amd64-fbsd/clang/profile.bashrc | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/profiles/arch/amd64-fbsd/clang/profile.bashrc b/profiles/arch/amd64-fbsd/clang/profile.bashrc
index a6e226c..f741ccd 100644
--- a/profiles/arch/amd64-fbsd/clang/profile.bashrc
+++ b/profiles/arch/amd64-fbsd/clang/profile.bashrc
@@ -4,5 +4,6 @@
# Check if clang/clang++ exist before setting them so that we can more easily
# switch to this profile and build stages.
-type -P clang > /dev/null && export CC=clang
-type -P clang++ > /dev/null && [ -f /usr/lib/libc++.so ] && export CXX=clang++
+# Some packages will require BUILD_{CC,CXX} variables, bug 595878.
+type -P clang > /dev/null && export CC=clang && export BUILD_CC=clang
+type -P clang++ > /dev/null && [ -f /usr/lib/libc++.so ] && export CXX=clang++ && export BUILD_CXX=clang++
next reply other threads:[~2016-10-03 17:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-03 17:03 Alexis Ballier [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-04-11 22:47 [gentoo-commits] repo/gentoo:master commit in: profiles/arch/amd64-fbsd/clang/ Patrice Clement
2017-06-09 15:57 Anthony G. Basile
2017-03-08 21:30 Michał Górny
2016-09-26 10:44 Alexis Ballier
2016-09-26 10:39 Alexis Ballier
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=1475514132.ab7fc44e73fa6e50494d90fe57deb1e283f191d0.aballier@gentoo \
--to=aballier@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