From: Sam Ravnborg <sam@ravnborg.org>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Badari Pulavarty <pbadari@us.ibm.com>,
lkml <linux-kernel@vger.kernel.org>, Andi Kleen <ak@muc.de>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
Andi Kleen <ak@suse.de>
Subject: Re: 2.6.23-git11 compile issues
Date: Wed, 17 Oct 2007 21:06:35 +0200 [thread overview]
Message-ID: <20071017190635.GA11837@uranus.ravnborg.org> (raw)
In-Reply-To: <1192640594.17464.37.camel@localhost>
On Wed, Oct 17, 2007 at 10:03:14AM -0700, Dave Hansen wrote:
> 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.
Hi Dave.
I cooked up the following patch - can you try it out in your
environment.
I wonder if this is that simple since no-one have done it before??
Sam
diff --git a/Makefile b/Makefile
index ed65de7..136d7c2 100644
--- a/Makefile
+++ b/Makefile
@@ -903,14 +903,24 @@ prepare: prepare0
export CPPFLAGS_vmlinux.lds += -P -C -U$(ARCH)
-# FIXME: The asm symlink changes when $(ARCH) changes. That's
-# hard to detect, but I suppose "make mrproper" is a good idea
-# before switching between archs anyway.
-
-include/asm:
- @echo ' SYMLINK $@ -> include/asm-$(SRCARCH)'
- $(Q)if [ ! -d include ]; then mkdir -p include; fi;
- @ln -fsn asm-$(SRCARCH) $@
+# The asm symlink changes when $(ARCH) changes.
+# Detect this and ask user to run make mrproper
+
+include/asm: FORCE
+ $(Q)set -e; asmlink=`readlink include/asm | cut -d '-' -f 2`; \
+ if [ -L include/asm ]; then \
+ if [ "$$asmlink" != "$(SRCARCH)" ]; then \
+ echo "ERROR: the symlink $@ points to asm-$$asmlink but asm-$(SRCARCH) was expected"; \
+ echo " save .config and run 'make mrproper' to fix it"; \
+ exit 1; \
+ fi; \
+ else \
+ echo ' SYMLINK $@ -> include/asm-$(SRCARCH)'; \
+ if [ ! -d include ]; then \
+ mkdir -p include; \
+ fi; \
+ ln -fsn asm-$(SRCARCH) $@; \
+ fi
# Generate some files
# ---------------------------------------------------------------------------
prev parent reply other threads:[~2007-10-17 19:09 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
2007-10-17 19:06 ` Sam Ravnborg [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=20071017190635.GA11837@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=ak@muc.de \
--cc=ak@suse.de \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pbadari@us.ibm.com \
--cc=tglx@linutronix.de \
/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