From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, X86 ML <x86@kernel.org>
Subject: Re: linux-next: Tree for May 26 (syscalls is85/ia32 on x86_64)
Date: Mon, 26 May 2014 10:41:35 -0700 [thread overview]
Message-ID: <53837CCF.7010807@infradead.org> (raw)
In-Reply-To: <20140526193819.2ba7bc07@canb.auug.org.au>
On 05/26/2014 02:38 AM, Stephen Rothwell wrote:
> Hi all,
>
> The powerpc allyesconfig is again broken more than usual.
>
> Changes since 20140523:
>
I get lots of build errors (and have for the past week of so)
like this:
CC arch/x86/kernel/asm-offsets.s
In file included from ../arch/x86/kernel/asm-offsets.c:27:0:
../arch/x86/kernel/asm-offsets_64.c:15:29: fatal error: asm/syscalls_32.h: No such file or directory
compilation terminated.
make[2]: *** [arch/x86/kernel/asm-offsets.s] Error 1
when CONFIG_X86_X32_ABI is not enabled.
--
~Randy
next prev parent reply other threads:[~2014-05-26 17:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 9:38 linux-next: Tree for May 26 Stephen Rothwell
2014-05-26 17:41 ` Randy Dunlap [this message]
2014-05-26 17:47 ` linux-next: Tree for May 26 (staging/rtl8192ee) Randy Dunlap
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=53837CCF.7010807@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).