From: Shi Weihua <shiwh@cn.fujitsu.com>
To: ltp-list <ltp-list@lists.sourceforge.net>
Subject: [LTP] [PATCH] cpuset: fix a lost compile target in Makefile
Date: Tue, 05 Jan 2010 15:57:53 +0800 [thread overview]
Message-ID: <4B42F101.2070009@cn.fujitsu.com> (raw)
In latest ltp version, the following message occured when run the case of cpuset.
-----
./cpuset_hotplug_test.sh: line 39: ./cpuset_list_compute: No such file or directory
./cpuset_hotplug_test.sh: line 227: ./cpuset_list_compute: No such file or directory
-----
The reason is that cpuset_list_compute.c(in testcases/kernel/controllers/cpuset/
cpuset_hotplug_test/) has not been compiled.
This patch fix it.
Signed-off-by: Shi Weihua <shiwh@cn.fujitsu.com>
---
--- ltp-intermediate-20091209.orig/testcases/kernel/controllers/cpuset/cpuset_hotplug_test/Makefile 2009-12-09 02:48:49.000000000 -0500
+++ ltp-intermediate-20091209/testcases/kernel/controllers/cpuset/cpuset_hotplug_test/Makefile 2010-01-05 10:53:55.000000000 -0500
@@ -25,6 +25,6 @@ top_srcdir ?= ../../../../.
include $(top_srcdir)/include/mk/testcases.mk
include $(abs_srcdir)/../Makefile.inc
-MAKE_TARGETS :=
+LDLIBS += -lpthread
include $(top_srcdir)/include/mk/generic_leaf_target.mk
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next reply other threads:[~2010-01-05 7:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 7:57 Shi Weihua [this message]
2010-01-06 5:55 ` [LTP] [PATCH] cpuset: fix a lost compile target in Makefile 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=4B42F101.2070009@cn.fujitsu.com \
--to=shiwh@cn.fujitsu.com \
--cc=ltp-list@lists.sourceforge.net \
/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