From: Peter Wu <lekensteyn@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: OOT build fails on x86_64 due to missing asm/unisd_64.h
Date: Mon, 15 Jul 2013 21:43:56 +0200 [thread overview]
Message-ID: <11004109.FAIvXteeAc@al> (raw)
In-Reply-To: <ddf0f5a9-a6f1-418f-8b41-41086986c694@email.android.com>
On Monday 15 July 2013 12:40:59 H. Peter Anvin wrote:
> In a clean directory?
That's a fast reply! While trying to reproduce after sending out the mail, I
noticed this line:
$ (cd ~/Linux-src/linux/;git clean -xfd)
Removing arch/x86/include/generated/
warning: failed to remove arch/x86/include/generated/
Somehow that directory got root owned and I was unable to remove it without
using root power. After removing it, the build completes succesfully.
Sorry for the noise!
Thanks,
Peter
> Peter Wu <lekensteyn@gmail.com> wrote:
> >Hi,
> >
> >When I tried to build v3.11-rc1-8-g47188d3 out-of-tree, I get an error
> >about a
> >missing asm/unistd_64.h file. The full build output (`git clean -xfd`
> >was ran
> >before baking the kernel):
> >
> >/home/me/Linux-src/build$ make O=$PWD -C ../linux -j8
> >make: Entering directory `/home/me/Linux-src/linux'
> >/home/me/Linux-src/linux/arch/x86/Makefile:107: CONFIG_X86_X32 enabled
> >but no binutils support
> >make[2]: Nothing to be done for `all'.
> >
> > GEN /tmp/build/Makefile
> > CHK include/generated/uapi/linux/version.h
> >
> >make[2]: Nothing to be done for `relocs'.
> >
> > Using /home/me/Linux-src/linux as source for kernel
> > CHK include/generated/utsrelease.h
> > UPD include/generated/utsrelease.h
> > CC kernel/bounds.s
> > GEN include/generated/bounds.h
> > CC arch/x86/kernel/asm-offsets.s
> >
> >In file included from
> >/home/me/Linux-src/linux/include/uapi/linux/unistd.h:7:0,
> >
> > from /home/me/Linux-src/linux/arch/x86/include/asm/seccomp_64.h:4,
> >
> > from /home/me/Linux-src/linux/arch/x86/include/asm/seccomp.h:4,
> >
> > from /home/me/Linux-src/linux/include/linux/seccomp.h:9,
> >
> > from /home/me/Linux-src/linux/include/linux/sched.h:39,
> >
> > from /home/me/Linux-src/linux/arch/x86/kernel/asm-offsets.c:9:
> >/home/me/Linux-src/linux/arch/x86/include/asm/unistd.h:23:29: fatal
> >error: asm/unistd_64.h: No such file or directory
> >compilation terminated.
> >make[2]: *** [arch/x86/kernel/asm-offsets.s] Error 1
> >make[1]: *** [prepare0] Error 2
> >make: *** [sub-make] Error 2
> >make: Leaving directory `/home/me/Linux-src/linux'
> >
> >
> >
> >As a workaround, I rsync the files that are placed in the source tree:
> >
> >~/Linux-src/linux/arch/x86/include/generated$ rsync -av .
> >/tmp/build/arch/x86/include/generated/
> >sending incremental file list
> >./
> >asm/
> >asm/syscalls_32.h
> >uapi/
> >uapi/asm/
> >uapi/asm/unistd_32.h
> >uapi/asm/unistd_64.h
> >
> >uapi/asm/unistd_x32.h
> >
> >
> >I have encountered this error some releases back, and some others
> >reported
> >this before[1]. If you need more details (.config?), please ask.
> >
> >Regards,
> >Peter
> >
> > [1]: http://lkml.org/lkml/2012/3/19/680
prev parent reply other threads:[~2013-07-15 19:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-15 19:36 OOT build fails on x86_64 due to missing asm/unisd_64.h Peter Wu
2013-07-15 19:40 ` H. Peter Anvin
2013-07-15 19:43 ` Peter Wu [this message]
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=11004109.FAIvXteeAc@al \
--to=lekensteyn@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox