From: Greg KH <gregkh@linuxfoundation.org>
To: Shuah Khan <shuahkhan@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
mmarek@suse.com, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Ubuntu 16.10 - Linux Kernel build fails - GCC related
Date: Tue, 18 Oct 2016 17:37:55 +0200 [thread overview]
Message-ID: <20161018153755.GA10386@kroah.com> (raw)
In-Reply-To: <CAKocOOOqWU__aQvO43qWSKzc4MBAdqZMM0KzPa4X4e9eQXnsFw@mail.gmail.com>
On Tue, Oct 18, 2016 at 09:24:20AM -0600, Shuah Khan wrote:
> After upgrading to Ubuntu 16.10, I can't build kernels anymore unless
> the following patch is applied to the kernel Makefile. A word of
> caution for anybody that is planning to update their development
> systems.
>
> https://patchwork.ozlabs.org/patch/616621/
>
> Please refer to the Ubuntu 16.10 release notes for more details.
>
> https://wiki.ubuntu.com/YakketyYak/ReleaseNotes#GCC
>
> Ubuntu is recommended applying this patch for building Linux kernels.
> I am not sure this is the right way to go. I am hoping this is
> work-around and patching the kernel Makefile will not be the solution
> going forward.
>
> I haven't seen any patch sent upstream to make this change, so I still
> hope this is a temporary work-around. Maybe be there is patch that
> came through and you are aware of this problem?
Does commit 6d92bc9d483a solve this issue for you? That should have
resolved a -pie issue, back in 4.6, or is this something else?
thanks,
greg k-h
next prev parent reply other threads:[~2016-10-18 15:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 15:24 Ubuntu 16.10 - Linux Kernel build fails - GCC related Shuah Khan
2016-10-18 15:37 ` Greg KH [this message]
2016-10-18 15:48 ` Shuah Khan
2016-10-18 15:56 ` Greg KH
2016-10-18 16:02 ` Shuah Khan
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=20161018153755.GA10386@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.com \
--cc=shuahkhan@gmail.com \
--cc=torvalds@linux-foundation.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.