From: Milian Wolff <milian.wolff@kdab.com>
To: linux-perf-users@vger.kernel.org
Subject: Building perf with clang
Date: Fri, 01 Apr 2016 23:19:05 +0200 [thread overview]
Message-ID: <2572584.yi1Xp0m2mb@agathebauer> (raw)
[-- Attachment #1: Type: text/plain, Size: 604 bytes --]
Hey all,
I usually use clang to build my code, and have configured CC and CXX globally
for that purpose. When I forget to unset that before I run "make" in the perf
folder, I get into serious trouble as that is not supported at all.
So, can that be fixed, either by making perf buildable with clang, or by
enforcing GCC within the Makefile if clang is not supported? Or at least error
out early if clang would be used?
Thanks
--
Milian Wolff | milian.wolff@kdab.com | Software Engineer
KDAB (Deutschland) GmbH&Co KG, a KDAB Group company
Tel: +49-30-521325470
KDAB - The Qt Experts
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5903 bytes --]
next reply other threads:[~2016-04-01 21:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 21:19 Milian Wolff [this message]
2016-04-01 22:16 ` Building perf with clang Arnaldo Carvalho de Melo
2016-04-02 21:33 ` Milian Wolff
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=2572584.yi1Xp0m2mb@agathebauer \
--to=milian.wolff@kdab.com \
--cc=linux-perf-users@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).