[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKwvOdn1BDsYCrjUVDqKyiZA8pvENOWaOvkYN3kcVfWZof9Esw@mail.gmail.com>
Date: Mon, 11 Feb 2019 11:27:20 -0800
From: Nick Desaulniers <ndesaulniers@...gle.com>
To: Masahiro Yamada <yamada.masahiro@...ionext.com>
Cc: Nathan Chancellor <natechancellor@...il.com>,
Michal Marek <michal.lkml@...kovi.net>,
Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Sedat Dilek <sedat.dilek@...il.com>
Subject: Re: [PATCH 3/4] Makefile: lld: tell clang to use lld
On Mon, Feb 11, 2019 at 7:33 AM Masahiro Yamada
<yamada.masahiro@...ionext.com> wrote:
>
> On Sat, Feb 9, 2019 at 2:27 AM Nick Desaulniers <ndesaulniers@...gle.com> wrote:
> >
> > On Thu, Feb 7, 2019 at 9:51 PM Nathan Chancellor
> > <natechancellor@...il.com> wrote:
> > >
> > > On Thu, Feb 07, 2019 at 02:01:51PM -0800, ndesaulniers@...gle.com wrote:
> > > > This is needed because clang doesn't select which linker to use based on
> > > > $LD but rather -fuse-ld=$(LD). This is problematic especially for
> > > > cc-ldoption, which checks for linker flag support via invoking the
> > > > compiler, rather than the linker.
>
> What do you mean by 'problematic' ?
>
> I see no build error in
> arch/arm64/kernel/vdso/Makefile, at least.
>
> Clang uses BFD linker by default,
> which may not match to the $(LD) passed in.
>
> Is this what you mean?
Right, when using a linker other than BFD, we want cc-ldoption to tell
us whether that linker supports a linker flag or not.
--
Thanks,
~Nick Desaulniers
Powered by blists - more mailing lists