From: Randy Dunlap <rdunlap@infradead.org>
To: Piotr Karbowski <piotr.karbowski@gmail.com>,
linux-kernel@vger.kernel.org, X86 ML <x86@kernel.org>,
"K. Y. Srinivasan" <kys@microsoft.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: Unable to link 4.3-rc1: undefined reference to `native_machine_crash_shutdown'
Date: Mon, 14 Sep 2015 14:50:33 -0700 [thread overview]
Message-ID: <55F74129.3020702@infradead.org> (raw)
In-Reply-To: <55F73DB7.7010206@gmail.com>
On 09/14/15 14:35, Piotr Karbowski wrote:
> Hello,
>
> I wanted to try on the 4.3-rc1 kernel and it fails during linking with undefined reference to `native_machine_crash_shutdown'
>
> # make
> CHK include/config/kernel.release
> CHK include/generated/uapi/linux/version.h
> CHK include/generated/utsrelease.h
> CHK include/generated/bounds.h
> CHK include/generated/timeconst.h
> CHK include/generated/asm-offsets.h
> CALL scripts/checksyscalls.sh
> CHK include/generated/compile.h
> CHK kernel/config_data.h
> LINK vmlinux
> LD vmlinux.o
> MODPOST vmlinux.o
> GEN .version
> CHK include/generated/compile.h
> UPD include/generated/compile.h
> CC init/version.o
> LD init/built-in.o
> arch/x86/built-in.o: In function `hv_machine_crash_shutdown':
> mshyperv.c:(.text+0x7514c): undefined reference to `native_machine_crash_shutdown'
> Makefile:927: recipe for target 'vmlinux' failed
> make: *** [vmlinux] Error 1
>
> The dot config is as follow (stripped hashes and empty lines):
> [deleted]
This has been happening for awhile now and has been reported several times.
Also there have been 2 or 3 patches posted to fix it... so what will it take
to get a fix merged? anyone?
thnx,
--
~Randy
next prev parent reply other threads:[~2015-09-14 21:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-14 21:35 Unable to link 4.3-rc1: undefined reference to `native_machine_crash_shutdown' Piotr Karbowski
2015-09-14 21:50 ` Randy Dunlap [this message]
2015-09-15 15:19 ` Piotr Karbowski
2015-09-15 15:23 ` KY Srinivasan
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=55F74129.3020702@infradead.org \
--to=rdunlap@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=piotr.karbowski@gmail.com \
--cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.