From: Dave Hansen <haveblue@us.ibm.com>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>, Andi Kleen <ak@muc.de>
Subject: Re: 2.6.23-git11 compile issues
Date: Wed, 17 Oct 2007 10:03:14 -0700 [thread overview]
Message-ID: <1192640594.17464.37.camel@localhost> (raw)
In-Reply-To: <1192635199.14504.2.camel@dyn9047017100.beaverton.ibm.com>
On Wed, 2007-10-17 at 08:33 -0700, Badari Pulavarty wrote:
> Known issue ?
...
> CHK include/linux/version.h
> CHK include/linux/utsrelease.h
> CC arch/x86/kernel/asm-offsets.s
> In file included from arch/x86/kernel/asm-offsets_64.c:7,
> from arch/x86/kernel/asm-offsets.c:4:
> include/linux/crypto.h:20:24: error: asm/atomic.h: No such file or directory
> In file included from include/linux/types.h:14,
> from include/linux/prefetch.h:13,
> from include/linux/list.h:8,
> from include/linux/module.h:9,
> from include/linux/crypto.h:21,
> from arch/x86/kernel/asm-offsets_64.c:7,
> from arch/x86/kernel/asm-offsets.c:4:
I hit the same thing, and fixed it with mrproper as well. I assume this
is a result of the x86 merge.
Andi, is there a way we can detect the old include directories, and
error out? Otherwise, we're going to get a ton more of these reports
when people do incremental patching up to 2.6.24. I've been doing
nightly incremental builds for a year or two, and I think this is the
first time it has actually required manual intervention.
-- Dave
next prev parent reply other threads:[~2007-10-17 17:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 15:33 2.6.23-git11 compile issues Badari Pulavarty
2007-10-17 11:43 ` Andre Haupt
2007-10-17 15:38 ` Ismail Dönmez
2007-10-17 16:17 ` Badari Pulavarty
2007-10-17 18:48 ` J. Bruce Fields
2007-10-17 17:03 ` Dave Hansen [this message]
2007-10-17 19:06 ` Sam Ravnborg
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=1192640594.17464.37.camel@localhost \
--to=haveblue@us.ibm.com \
--cc=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@us.ibm.com \
/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.