From: Shan Wei <shanwei@cn.fujitsu.com>
To: ltp-list@lists.sourceforge.net
Cc: "Shan Wei" <shanwei@cn.fujitsu.com>, "缪 勰" <miaox@cn.fujitsu.com>
Subject: [LTP] [PATCH] controller: fix the bug of missing compilation for controller cases
Date: Mon, 07 Sep 2009 14:05:13 +0800 [thread overview]
Message-ID: <4AA4A299.1020105@cn.fujitsu.com> (raw)
When doing "./configure && make", I found the controller cases couldn't be compiled.
Because the config.mk file included into testcases/kernel/Makefile lost the definition
of LTP_CHECK_CGROUPSTATS_HEADER, so ltp never enters the controller directory to do "make".
And config.mk file is created by config.mk.in file in fact. In config.mk.in,
LTP_CHECK_CGROUPSTATS_HEADER is lost, it leads to the wrong config.mk.
Add LTP_CHECK_CGROUPSTATS_HEADER in config.mk.in to fix the problem.
Signed-off-by: Miao Xie <miaox@cn.fujitsu.com>
Signed-off-by: Shan Wei <shanwei@cn.fujitsu.com>
---
config.mk.in | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/config.mk.in b/config.mk.in
index 0fcb80a..64e3847 100644
--- a/config.mk.in
+++ b/config.mk.in
@@ -9,3 +9,5 @@ LDFLAGS = @LDFLAGS@
AIO_LIBS = @AIO_LIBS@
SELINUX_LIBS = @SELINUX_LIBS@
CRYPTO_LIB = @CRYPTO_LIB@
+
+LTP_CHECK_CGROUPSTATS_HEADER = @LTP_CHECK_CGROUPSTATS_HEADER@
--
1.5.4.rc3
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next reply other threads:[~2009-09-07 6:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-07 6:05 Shan Wei [this message]
2009-09-07 7:15 ` [LTP] [PATCH] controller: fix the bug of missing compilation for controller cases Subrata Modak
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=4AA4A299.1020105@cn.fujitsu.com \
--to=shanwei@cn.fujitsu.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=miaox@cn.fujitsu.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.