All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Ignat Korchagin <ignat@cloudflare.com>
Cc: stable@vger.kernel.org, Ivan Babrou <ivan@cloudflare.com>,
	Daniel Dao <dqminh@cloudflare.com>
Subject: Re: Building 4.14 LTS kernel with GCC 8
Date: Thu, 11 Oct 2018 09:29:10 +0200	[thread overview]
Message-ID: <20181011072910.GA19751@kroah.com> (raw)
In-Reply-To: <CALrw=nHjMec_0s2rRu52UaJaD8T6CBsULpXqagDVVUb7V3LXdg@mail.gmail.com>

On Tue, Oct 09, 2018 at 02:07:15PM +0100, Ignat Korchagin wrote:
> Hello,
> 
> We were trying to build 4.14 kernel with GCC 8, but perf failed to
> compile. The upstream tree seems to have necessary commits to support
> GCC 8, but they were not ported to 4.14 branch. With backporting the
> following commits we were able to restore perf compilation and compile
> a working 4.14 kernel with GCC 8.2:
> 
> 6810158d526e483868e519befff407b91e76b3db: perf annotate: Use asprintf
> when formatting objdump command
> b7a313d84e853049062011d78cb04b6decd12f5c: perf tools: Fix python
> extension build for gcc 8
> 77f18153c080855e1c3fb520ca31a4e61530121d: perf tools: Fix snprint
> warnings for gcc 8
> 06c3f2aa9fc68e7f3fe3d83e7569d2a2801d9f99: perf utils: Move
> is_directory() to path.h

Why is this last commit needed?

I've applied the other 3 now.

thanks,

greg k-h

  reply	other threads:[~2018-10-11 14:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-09 13:07 Building 4.14 LTS kernel with GCC 8 Ignat Korchagin
2018-10-11  7:29 ` Greg KH [this message]
2018-10-11 10:12   ` Ignat Korchagin
2018-10-11 10:17     ` Greg KH
2018-10-11 10:26       ` Ignat Korchagin
2018-10-16 16:28         ` Ignat Korchagin
2018-10-16 16:42           ` Greg Kroah-Hartman

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=20181011072910.GA19751@kroah.com \
    --to=greg@kroah.com \
    --cc=dqminh@cloudflare.com \
    --cc=ignat@cloudflare.com \
    --cc=ivan@cloudflare.com \
    --cc=stable@vger.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.