From: Shi Weihua <shiwh@cn.fujitsu.com>
To: subrata@linux.vnet.ibm.com
Cc: ltp-list <ltp-list@lists.sourceforge.net>
Subject: [LTP] [PATCH] Fix "make clean"'s failure in case cpuset
Date: Mon, 13 Jul 2009 16:15:20 +0800 [thread overview]
Message-ID: <4A5AED18.2090201@cn.fujitsu.com> (raw)
In case cpuset, the file cpuset_syscall_test.o was not deleted after "make clean".
The following patch fixed this problem.
Signed-off-by: Shi Weihua <shiwh@cn.fujitsu.com>
---
diff -urpN ltp-full-20090630.orig/testcases/kernel/controllers/cpuset/cpuset_syscall_test/Makefile ltp-full-20090630/testcases/kernel/controllers/cpuset/cpuset_syscall_test/Makefile
--- ltp-full-20090630.orig/testcases/kernel/controllers/cpuset/cpuset_syscall_test/Makefile 2009-06-23 10:18:17.000000000 -0400
+++ ltp-full-20090630/testcases/kernel/controllers/cpuset/cpuset_syscall_test/Makefile 2009-07-13 12:24:01.000000000 -0400
@@ -8,7 +8,8 @@ all:cpuset_syscall_test
cpuset_syscall_test: %: %.o $(LIBOBJECTS)
clean:
- rm -rf cpuset_syscall_test
+ rm -rf cpuset_syscall_test cpuset_syscall_test.o
+ rm -f $(LIBOBJECTS)
install:
@set -e; \
------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next reply other threads:[~2009-07-13 8:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 8:15 Shi Weihua [this message]
2009-07-13 8:22 ` [LTP] [PATCH] Fix "make clean"'s failure in case cpuset Subrata Modak
2009-07-13 16:57 ` Garrett Cooper
2009-07-13 18:09 ` Garrett Cooper
2009-07-13 23:49 ` Shi Weihua
2009-07-14 0:00 ` Garrett Cooper
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=4A5AED18.2090201@cn.fujitsu.com \
--to=shiwh@cn.fujitsu.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=subrata@linux.vnet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox