From: Aaro Koskinen <aaro.koskinen@nokia.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@kernel.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH 2/2] perf: allow to specify custom linker command
Date: Wed, 1 Jul 2015 14:54:43 +0300 [thread overview]
Message-ID: <1435751683-18500-2-git-send-email-aaro.koskinen@nokia.com> (raw)
In-Reply-To: <1435751683-18500-1-git-send-email-aaro.koskinen@nokia.com>
Allow to specify custom linker command. This fixes MIPS64 builds for
64-bit userspace as it will allow to pass a linker using the correct
linker flags for 64-bit ABI (by default GNU binutils ld will assume N32).
Signed-off-by: Aaro Koskinen <aaro.koskinen@nokia.com>
---
tools/perf/Makefile.perf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/perf/Makefile.perf b/tools/perf/Makefile.perf
index 14e823f..a3fbe65 100644
--- a/tools/perf/Makefile.perf
+++ b/tools/perf/Makefile.perf
@@ -108,7 +108,7 @@ $(OUTPUT)PERF-VERSION-FILE: ../../.git/HEAD
$(Q)touch $(OUTPUT)PERF-VERSION-FILE
CC = $(CROSS_COMPILE)gcc
-LD = $(CROSS_COMPILE)ld
+LD ?= $(CROSS_COMPILE)ld
AR = $(CROSS_COMPILE)ar
PKG_CONFIG = $(CROSS_COMPILE)pkg-config
--
2.4.3
next prev parent reply other threads:[~2015-07-01 11:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-01 11:54 [PATCH 1/2] perf: create config.detected into OUTPUT directory Aaro Koskinen
2015-07-01 11:54 ` Aaro Koskinen [this message]
2015-07-01 13:04 ` [PATCH 2/2] perf: allow to specify custom linker command Jiri Olsa
2015-07-03 7:49 ` [tip:perf/urgent] perf tools: Allow " tip-bot for Aaro Koskinen
2015-07-01 13:04 ` [PATCH 1/2] perf: create config.detected into OUTPUT directory Jiri Olsa
2015-07-03 7:49 ` [tip:perf/urgent] perf tools: Create " tip-bot for Aaro Koskinen
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=1435751683-18500-2-git-send-email-aaro.koskinen@nokia.com \
--to=aaro.koskinen@nokia.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.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
all inboxes | Powered by JetHome®