linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: Will Deacon <will@kernel.org>
Cc: Shaokun Zhang <zhangshaokun@hisilicon.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-tegra <linux-tegra@vger.kernel.org>
Subject: Re: linux-next: Tree for Jun 24 [build failure on arm64]
Date: Wed, 24 Jun 2020 13:29:00 +0100	[thread overview]
Message-ID: <a7ebe7c1-49ae-5bc9-9c4f-fcc693ca3834@nvidia.com> (raw)
In-Reply-To: <20200624122242.GA6270@willie-the-truck>


On 24/06/2020 13:22, Will Deacon wrote:
> On Wed, Jun 24, 2020 at 12:57:23PM +0100, Jon Hunter wrote:
>> On 24/06/2020 11:55, Will Deacon wrote:
>>> diff --git a/arch/arm64/kernel/vdso/Makefile b/arch/arm64/kernel/vdso/Makefile
>>> index 1e5a940532da..97d3d3632093 100644
>>> --- a/arch/arm64/kernel/vdso/Makefile
>>> +++ b/arch/arm64/kernel/vdso/Makefile
>>> @@ -23,8 +23,9 @@ btildflags-$(CONFIG_ARM64_BTI_KERNEL) += -z force-bti
>>>  # potential future proofing if we end up with internal calls to the exported
>>>  # routines, as x86 does (see 6f121e548f83 ("x86, vdso: Reimplement vdso.so
>>>  # preparation in build-time C")).
>>> -ldflags-y := -shared -nostdlib -soname=linux-vdso.so.1 --hash-style=sysv \
>>> -               -Bsymbolic --no-eh-frame-hdr --build-id -n $(btildflags-y) -T
>>> +ldflags-y := -shared -nostdlib -soname=linux-vdso.so.1 --hash-style=sysv       \
>>> +            -Bsymbolic $(call ld-option, --no-eh-frame-hdr) --build-id -n      \
>>> +            $(btildflags-y) -T
>>>  
>>>  ccflags-y := -fno-common -fno-builtin -fno-stack-protector -ffixed-x18
>>>  ccflags-y += -DDISABLE_BRANCH_PROFILING
>>>
>>
>>
>> I am seeing the same build failure and the above does fix it for me.
> 
> Cheers, Jon. I'll get this into -next with your Tested-by.

Thanks, that will be great.

Jon

-- 
nvpublic

  reply	other threads:[~2020-06-24 12:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-24  6:53 linux-next: Tree for Jun 24 Stephen Rothwell
2020-06-24  9:08 ` linux-next: Tree for Jun 24 [build failure on arm64] Shaokun Zhang
2020-06-24 10:55   ` Will Deacon
2020-06-24 11:57     ` Jon Hunter
2020-06-24 12:22       ` Will Deacon
2020-06-24 12:29         ` Jon Hunter [this message]
2020-06-28  0:54     ` Shaokun Zhang
2020-06-24 14:37 ` linux-next: Tree for Jun 24 (scsi -> ata) Randy Dunlap

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=a7ebe7c1-49ae-5bc9-9c4f-fcc693ca3834@nvidia.com \
    --to=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=will@kernel.org \
    --cc=zhangshaokun@hisilicon.com \
    /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).