mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Clayton <chris2553@googlemail.com>
To: Gabriel C <nix.or.die@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Linux 5.3.6
Date: Sun, 13 Oct 2019 09:26:56 +0100	[thread overview]
Message-ID: <1b29b820-06e5-fed4-2dd3-a66ceded73c8@googlemail.com> (raw)
In-Reply-To: <CAEJqkgjAMkoiAQeitQ1gdEpmZWvdqQE+fAsQU4W7M7JGxHboyQ@mail.gmail.com>



On 12/10/2019 21:55, Gabriel C wrote:
> Am Sa., 12. Okt. 2019 um 21:16 Uhr schrieb Chris Clayton
> <chris2553@googlemail.com>:
>>
>>
>>> I'm announcing the release of the 5.3.6 kernel.
>>
>>
>> 5.3.6 build fails here with:
>>
>> arch/x86/entry/vdso/vdso64.so.dbg: undefined symbols found
>>   CC      arch/x86/kernel/cpu/mce/threshold.o
>> make[3]: *** [arch/x86/entry/vdso/Makefile:59: arch/x86/entry/vdso/vdso64.so.dbg] Error 1
>> make[3]: *** Deleting file 'arch/x86/entry/vdso/vdso64.so.dbg'
>> make[2]: *** [scripts/Makefile.build:497: arch/x86/entry/vdso] Error 2
>> make[1]: *** [scripts/Makefile.build:497: arch/x86/entry] Error 2
>> make[1]: *** Waiting for unfinished jobs....
>>
> 
> What is your default linker ?
> 
> Also does make LD=ld.bfd fixes that for you ?
> 

Thanks, Gabriel. The default linker is gold, but your suggestion above fixed the build. I think I'll set the default to
LD.bfd.

> See https://bugzilla.kernel.org/show_bug.cgi?id=204951
> 
> BR,
> 
> Gabriel C.
> 

  reply	other threads:[~2019-10-13  8:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191012075902.GA2038794 () kroah ! com>
2019-10-12 19:16 ` Chris Clayton
2019-10-12 20:55   ` Gabriel C
2019-10-13  8:26     ` Chris Clayton [this message]
2019-10-13  7:51   ` Greg KH
2019-10-12  7:59 Greg KH
2019-10-12  7:59 ` Greg KH

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=1b29b820-06e5-fed4-2dd3-a66ceded73c8@googlemail.com \
    --to=chris2553@googlemail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nix.or.die@gmail.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

all inboxes | Powered by JetHome®