From: Xiaoguang Wang <wangxg.fnst@cn.fujitsu.com>
To: Mats Liljegren <mats.liljegren@enea.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] Problems compiling
Date: Mon, 14 Apr 2014 11:57:02 +0800 [thread overview]
Message-ID: <534B5C8E.1070500@cn.fujitsu.com> (raw)
In-Reply-To: <20140411183712.7ca33b6c@mats-desktop>
Hi,
On 04/12/2014 12:37 AM, Mats Liljegren wrote:
> I recently updated my master branch of my ltp git repository, but I now
> have a compile error:
>
> make[6]: Entering directory `/nfs/hosts/sestonas06/homes/mlil/git/ltp/testcases/kernel/mem/lib'
> make[6]: ../../../../../testcases/kernel/mem/lib/Makefile: No such file or directory
>
> Anyone else having this problem?
Yeah, I also met this problem.
I guess it may be "testcases/kernel/mem/include/libmem.mk" causing this issue.
I can reproduce this fail by following steps:
1, cd testcases/kernel/mem/lib
rm libmem.a
2, then back to testcases/kernel/mem/hugetlb/hugemmap
make
I got the similar error message:
make -C ../../../../../testcases/kernel/mem/lib -f "../../../../../testcases/kernel/mem/lib/Makefile" all
make[1]: Entering directory `/root/ltp-dev/testcases/kernel/mem/lib'
make[1]: ../../../../../testcases/kernel/mem/lib/Makefile: No such file or directory
make[1]: *** No rule to make target `../../../../../testcases/kernel/mem/lib/Makefile'. Stop.
make[1]: Leaving directory `/root/ltp-dev/testcases/kernel/mem/lib'
make: *** [../../../../../testcases/kernel/mem/lib/libmem.a] Error 2
In testcases/kernel/mem/include/libmem.mk:
MEM_SRCDIR := $(top_srcdir)/testcases/kernel/mem
LIBMEM_SRCDIR := $(MEM_SRCDIR)/lib
MEM_DIR := $(top_builddir)/testcases/kernel/mem
LIBMEM_DIR := $(MEM_DIR)/lib
LIBMEM := $(LIBMEM_DIR)/libmem.a
FILTER_OUT_DIRS := $(LIBMEM_DIR)
CFLAGS += -I$(MEM_SRCDIR)/include
LDLIBS += $(NUMA_LIBS) -lmem -lltp
LDFLAGS += -L$(LIBMEM_DIR)
$(LIBMEM_DIR):
mkdir -p "$@"
$(LIBMEM): $(LIBMEM_DIR)
$(MAKE) -C $^ -f "$(LIBMEM_SRCDIR)/Makefile" all
MAKE_DEPS += $(LIBMEM)
See the target $(LIBMEM). Since we have executed make command using the "-C" option, we do
not need to specify a make file with relative path. We can just
execute like that: $(MAKE) -C $^ -f "Makefile" all in this case.
Here the true reason is that when we change directory to $(LIBMEM_DIR), $(LIBMEM_SRCDIR)/Makefile
is not a valid path.
Regards,
Xiaoguang Wang
>
> Best regards
> Mats Liljegren
>
> ------------------------------------------------------------------------------
> Put Bad Developers to Shame
> Dominate Development with Jenkins Continuous Integration
> Continuously Automate Build, Test & Deployment
> Start a new project now. Try Jenkins in the cloud.
> http://p.sf.net/sfu/13600_Cloudbees
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list
>
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2014-04-14 3:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-11 16:37 [LTP] Problems compiling Mats Liljegren
2014-04-14 3:57 ` Xiaoguang Wang [this message]
2014-04-14 8:34 ` [LTP] [PATCH] testcases/kernel/mem: Fixed compile error Mats Liljegren
2014-04-14 16:09 ` [LTP] [PATCH] partrt_nohz_full: Get noHz mask from RT partition instead of boot parameter Mats Liljegren
2014-04-14 16:12 ` [LTP] Problems compiling chrubis
[not found] ` <0247700D01F14443B9209F90AD938CC524515766@sestoex05.enea.se>
2014-04-14 16:51 ` chrubis
[not found] ` <20140414185950.4945a644@mats-desktop>
2014-04-14 17:05 ` chrubis
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=534B5C8E.1070500@cn.fujitsu.com \
--to=wangxg.fnst@cn.fujitsu.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=mats.liljegren@enea.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