From: Harald Dunkel <harri@afaics.de>
To: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: 3.3: 2nd build fails with asm/unistd_64.h: No such file or directory
Date: Mon, 19 Mar 2012 23:24:59 +0100 [thread overview]
Message-ID: <4F67B23B.7010209@afaics.de> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi folks,
If I build 3.3 _again_ from the same source tree, then I get a problem
about a missing asm/unistd_64.h. Here is a sample session:
% make -C /export/git/linux-source O=/export/tmp/build_kernel/build clean
make: Entering directory `/export/git/linux-source'
CLEAN .
CLEAN .tmp_versions
make: Leaving directory `/export/git/linux-source'
% make -C /export/git/linux-source clean
make: Entering directory `/export/git/linux-source'
make: Leaving directory `/export/git/linux-source'
% make -C /export/git/linux-source O=/export/tmp/build_kernel/build oldconfig
make: Entering directory `/export/git/linux-source'
HOSTCC scripts/basic/fixdep
GEN /export/tmp/build_kernel/build/Makefile
HOSTCC scripts/kconfig/conf.o
HOSTCC scripts/kconfig/zconf.tab.o
HOSTLD scripts/kconfig/conf
scripts/kconfig/conf --oldconfig Kconfig
#
# configuration written to .config
#
make: Leaving directory `/export/git/linux-source'
% make -C /export/git/linux-source O=/export/tmp/build_kernel/build
make: Entering directory `/export/git/linux-source'
GEN /export/tmp/build_kernel/build/Makefile
scripts/kconfig/conf --silentoldconfig Kconfig
make[2]: Nothing to be done for `all'.
Using /export/git/linux-source as source for kernel
GEN /export/tmp/build_kernel/build/Makefile
CHK include/linux/version.h
CHK include/generated/utsrelease.h
CC kernel/bounds.s
GEN include/generated/bounds.h
CC arch/x86/kernel/asm-offsets.s
In file included from /export/git/linux-source/include/linux/unistd.h:7:0,
from /export/git/linux-source/arch/x86/include/asm/seccomp_64.h:4,
from /export/git/linux-source/arch/x86/include/asm/seccomp.h:4,
from /export/git/linux-source/include/linux/seccomp.h:8,
from /export/git/linux-source/include/linux/sched.h:80,
from /export/git/linux-source/arch/x86/kernel/asm-offsets.c:9:
/export/git/linux-source/arch/x86/include/asm/unistd.h:16: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 `/export/git/linux-source'
AFAICS asm/unistd_64.h was generated in the source directory, even
though I explicitly specified a separate build directory. Is this
expected?
There was no such problem for 3.2.12 and older. "git clean -dfx"
seems to help.
Regards
Harri
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAk9nsjsACgkQUTlbRTxpHjc9ewCfXBfOXhT0Zh89r6N8upv3Dwur
CnAAn1U9qho/XJWO1h5D1NBMXIsBq+Jp
=CJLY
-----END PGP SIGNATURE-----
reply other threads:[~2012-03-19 22:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4F67B23B.7010209@afaics.de \
--to=harri@afaics.de \
--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