From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Aaro Koskinen <aaro.koskinen@iki.fi>
Cc: Alexey Brodkin <Alexey.Brodkin@synopsys.com>,
linux-arch@vger.kernel.org,
Vineet Gupta <Vineet.Gupta1@synopsys.com>,
Aaro Koskinen <aaro.koskinen@nokia.com>,
Jiri Olsa <jolsa@kernel.org>, Paul Mackerras <paulus@samba.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Revert "perf tools: Allow to specify custom linker command"
Date: Tue, 14 Jul 2015 10:46:23 -0300 [thread overview]
Message-ID: <20150714134623.GH2885@kernel.org> (raw)
In-Reply-To: <20150713202406.GB5020@blackmetal.musicnaut.iki.fi>
Em Mon, Jul 13, 2015 at 11:24:06PM +0300, Aaro Koskinen escreveu:
> Hi,
>
> On Mon, Jul 13, 2015 at 02:10:53PM +0300, Alexey Brodkin wrote:
> > This reverts commit 5ef7bbb09f7b
> > ("perf tools: Allow to specify custom linker command").
> >
> > LD is a pre-defined variable in GNU Make. I.e. it is always defined.
> > Which means there's no point to check "LD ?= ..." because it will never
> > succeed. And so LD will be either that explicitly passed to make like
> > this:
> > ------->8-------
> > make LD=path_to_my_ld ...
> > ------->8-------
> > or default value, which is host's "ld".
> >
> > Latter leads to failure of cross-linkage because instead of cross linker
> > "$(CROSS_COMPILE)ld" host's "ld" is used.
> >
> > As for commit which is reverted here:
> > [1] Usually for selection of non-default flavour of CPU core/options
> > linker flags are used like "-mtune=xxx" or "-mMyCPUType" etc.
> >
> > [2] Still to implement ability to use "ld" that differs from
> > "$(CROSS_COMPILE)ld" one will need to add new makefile variable like
> > TARGET_LD and then check if $(TARGET_LD) is not specified on make
> > invocation then use "$(CROSS_COMPILE)ld".
> >
> > But for now to fix cross-building of perf this revert is enough.
>
> Hmm. You are probably right, my build system always exports LD with
> correct linker for cross builds so perhaps that's why I this "worked"
> for me when testing. Sorry.
So, I think this is an "Acked-by: Aaro Koskinen <aaro.koskinen@iki.fi>"
for the revert, right?
> I guess the correct fix would be [1], i.e. there should be some new
> variable to pass flags to ld command.
>
> Or maybe [2], could we use make "origin" function? If LD is "default",
> then use "$(CROSS_COMPILE)ld", otherwise use what the user passed?
When you guys get to some conclusion, please submit a new patch, for now
I am taking the revert with the (implied) Acked-by Aaro, ok?
- Arnaldo
next prev parent reply other threads:[~2015-07-14 13:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 11:10 [PATCH] Revert "perf tools: Allow to specify custom linker command" Alexey Brodkin
2015-07-13 20:24 ` Aaro Koskinen
2015-07-14 6:31 ` Jiri Olsa
2015-07-14 9:05 ` [PATCH] perf tools: Really allow to specify custom CC, AR or LD Alexey Brodkin
2015-07-18 3:22 ` [tip:perf/urgent] " tip-bot for Alexey Brodkin
2015-07-14 13:46 ` Arnaldo Carvalho de Melo [this message]
2015-07-14 14:00 ` [PATCH] Revert "perf tools: Allow to specify custom linker command" Alexey Brodkin
2015-07-14 14:45 ` acme
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=20150714134623.GH2885@kernel.org \
--to=acme@kernel.org \
--cc=Alexey.Brodkin@synopsys.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=a.p.zijlstra@chello.nl \
--cc=aaro.koskinen@iki.fi \
--cc=aaro.koskinen@nokia.com \
--cc=jolsa@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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