mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Langsdorf <mlangsdo@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	peterz@infradead.org
Subject: Re: Build failure on ARM64 for Linux 4.2-rc1 was: Linux 4.2-rc1
Date: Thu, 09 Jul 2015 11:46:04 -0500	[thread overview]
Message-ID: <559EA54C.4060807@redhat.com> (raw)
In-Reply-To: <559BCC8A.1030708@redhat.com>

On 07/07/2015 07:56 AM, Mark Langsdorf wrote:
> On 07/05/2015 03:22 PM, Linus Torvalds wrote:
>> It's Sunday, two weeks have passed, and the merge window is closed. I
>> just pushed out the tag to the git trees, and tar-balls and patches
>> should be mirroring out too.
>
> I'm seeing a build regression on arm64 for tools/perf.
>
> On linux-4.1, it builds fine.
>
> On linux-4.2-rc1, it dies with this relevant message (skipping the
> missing defines, etc):
>
> /home/mlangsdorf/tmp/linux-4.2/include/linux/preempt.h: At top level:
> /home/mlangsdorf/tmp/linux-4.2/include/linux/preempt.h:64:25: fatal
> error: asm/preempt.h: No such file or directory
>   #include <asm/preempt.h>
>
> On both versions, arch/arm64/include/generated/asm/preempt.h
> exists. I'm guessing something changed in the build system so
> that's its not being picked up for 4.2-rc1 but I'm not sure where
> to look.

Hi Peter,

I did a git bisect and it looks like the faulty patch is
d72da4a4d973d8a0a0d3c97e7cdebf287fbe3a99, "rbtree: Make lockless
searches non-fatal". I can't see why it causes my builds to fail,
but if I revert that patch and the related series, then I can
build the kernel and build tools/perf successfully.

Any insight into a less intensive way of fixing my build would
be appreciated.

--Mark Langsdorf

  reply	other threads:[~2015-07-09 16:46 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-05 20:22 Linus Torvalds
2015-07-05 23:01 ` Guenter Roeck
2015-07-07  5:50 ` linux-next: stats (Was: Linux 4.2-rc1) Stephen Rothwell
2015-07-07 12:56 ` Build failure on ARM64 for Linux 4.2-rc1 was: Linux 4.2-rc1 Mark Langsdorf
2015-07-09 16:46   ` Mark Langsdorf [this message]
2015-07-09 16:59     ` Peter Zijlstra
2015-07-13 16:55       ` Mark Langsdorf
2015-07-08 16:32 ` Shuah Khan
2015-07-08 17:05   ` Casey Schaufler
2015-07-08 17:33     ` Shuah Khan
2015-07-08 17:55       ` Casey Schaufler
2015-07-08 17:17   ` Linus Torvalds
2015-07-08 17:29     ` Linus Torvalds
2015-07-08 17:47       ` Casey Schaufler
2015-07-08 18:03         ` Stephen Smalley
2015-07-09  0:58       ` Ming Lei
2015-07-09  3:17         ` Linus Torvalds
2015-07-09  5:00           ` Ming Lei
2015-07-09 13:10           ` Shuah Khan
2015-07-09 13:44             ` Shuah Khan
2015-07-09 13:47               ` Shuah Khan
2015-07-09 14:45               ` Greg Kroah-Hartman
2015-07-09 17:40                 ` Shuah Khan
2015-07-10 16:58                   ` Shuah Khan
2015-07-10 17:11                     ` Linus Torvalds
     [not found]                       ` <55A03A33.8060405@osg.samsung.com>
     [not found]                         ` <CA+55aFzDu9acMKHJFkxzg+1jeHNpGRhmM=pu2z-so5QYTMbvcA@mail.gmail.com>
2015-07-10 21:57                           ` Shuah Khan
2015-07-10 22:36                           ` Ming Lei
2015-07-08 19:00     ` Ingo Molnar

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=559EA54C.4060807@redhat.com \
    --to=mlangsdo@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome