From: Sam Ravnborg <sam@ravnborg.org>
To: Mike Galbraith <efault@gmx.de>, Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH] x86: delete vsyscall files during make clean
Date: Wed, 17 Oct 2007 22:06:30 +0200 [thread overview]
Message-ID: <20071017200630.GH11837@uranus.ravnborg.org> (raw)
In-Reply-To: <1192608832.30373.5.camel@Homer.simpson.net>
make clean failed to delete a few files in
x86/kernel. This is because kbuild does not
see the correct/full kernel/Makefile.
As a workaround until the Makefiles are merged specify
the files to be deleted in the common Makefile.
Reported by Mike Galbraith <efault@gmx.de>
Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
Cc: Mike Galbraith <efault@gmx.de>
---
diff --git a/arch/x86/kernel/Makefile b/arch/x86/kernel/Makefile
index 45855c9..3857334 100644
--- a/arch/x86/kernel/Makefile
+++ b/arch/x86/kernel/Makefile
@@ -3,3 +3,7 @@ include ${srctree}/arch/x86/kernel/Makefile_32
else
include ${srctree}/arch/x86/kernel/Makefile_64
endif
+
+# Workaround to delete .lds files with make clean
+# The problem is that we do not enter Makefile_32 with make clean.
+clean-files := vsyscall*.lds vsyscall*.so
next prev parent reply other threads:[~2007-10-17 20:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-12 4:48 2.6.23.git build error Mike Galbraith
2007-10-12 21:31 ` Sam Ravnborg
2007-10-13 3:34 ` Mike Galbraith
2007-10-13 5:40 ` Giacomo Catenazzi
2007-10-13 7:16 ` Sam Ravnborg
2007-10-13 7:35 ` Mike Galbraith
2007-10-13 8:17 ` Sam Ravnborg
2007-10-13 9:44 ` Thomas Gleixner
[not found] ` <1192608832.30373.5.camel@Homer.simpson.net>
2007-10-17 20:06 ` Sam Ravnborg [this message]
2007-10-17 20:09 ` [PATCH] x86: delete vsyscall files during make clean Thomas Gleixner
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=20071017200630.GH11837@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®