From: "Mitani" <mitani@ryobi.co.jp>
To: ltp-list@lists.sourceforge.net
Subject: [LTP] LTP make failed in recent git
Date: Thu, 28 Oct 2010 15:59:45 +0900 [thread overview]
Message-ID: <000001cb766d$b3f5bbd0$1be13370$@co.jp> (raw)
Hi,
I found that "make" of LTP failed with recent git "ltp-332cdb8.tar.gz".
------------
gcc -g -O2 -g -O2 -fno-strict-aliasing -pipe -Wall -I../../../include
-I../../../include -L../../../lib ebizzy.c -lpthread -o ebizzy
make[3]: Leaving directory
`/home/LTP/ltp-dev-20101027/utils/benchmark/ebizzy-0.3'
make[3]: Entering directory
`/home/LTP/ltp-dev-20101027/utils/benchmark/kernbench-0.42'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory
`/home/LTP/ltp-dev-20101027/utils/benchmark/kernbench-0.42'
make[2]: Leaving directory `/home/LTP/ltp-dev-20101027/utils/benchmark'
make[1]: Leaving directory `/home/LTP/ltp-dev-20101027/utils'
make -C "testcases" \
-f "/home/LTP/ltp-dev-20101027/testcases/Makefile" all
make[1]: Entering directory `/home/LTP/ltp-dev-20101027/testcases'
make[2]: Entering directory `/home/LTP/ltp-dev-20101027/testcases/DOTS'
cd src;make
make[3]: Entering directory `/home/LTP/ltp-dev-20101027/testcases/DOTS/src'
mkdir -p ../classes/dots/framework
cd dots/framework;make
make[4]: Entering directory
`/home/LTP/ltp-dev-20101027/testcases/DOTS/src/dots/framework'
javac -d ../../../classes -classpath ../../../classes DotsConfig.java
make[4]: javac: Command not found
make[4]: *** [all] Error 127
make[4]: Leaving directory
`/home/LTP/ltp-dev-20101027/testcases/DOTS/src/dots/framework'
make[3]: *** [framework] Error 2
make[3]: Leaving directory `/home/LTP/ltp-dev-20101027/testcases/DOTS/src'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/home/LTP/ltp-dev-20101027/testcases/DOTS'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/LTP/ltp-dev-20101027/testcases'
make: *** [testcases-all] Error 2
------------
The new directory "DOTS" is going to be compiled, but "java" compiler
not installed.
Perhaps, following revision caused this failure, I think:
http://ltp.git.sourceforge.net/git/gitweb.cgi?p=ltp/ltp.git;a=blobdiff;f=tes
tcases/Makefile;h=f74de50bcd73321a950004027ca1e508ecc07c1b;hp=37c448f12a529e
155abca2d3c4a820a8b10f60a3;hb=6278b69ea79287a1a0d89593b4902aaf2c8c0016;hpb=7
e2cbbd9e762bee21a500ef7afdecec321f3f1cf
------------
-ifneq ($(UCLINUX),1)
-FILTER_OUT_DIRS += audit-test DOTS realtime
+ifeq ($(UCLINUX),1)
+FILTER_OUT_DIRS += DOTS realtime
------------
I don't know right way, but...
In the third line, isn't "+ifneq ($(UCLINUX),1)" right?
Or is it a more right method to install JAVA?
Regards--
-Tomonori Mitani
------------------------------------------------------------------------------
Nokia and AT&T present the 2010 Calling All Innovators-North America contest
Create new apps & games for the Nokia N8 for consumers in U.S. and Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store
http://p.sf.net/sfu/nokia-dev2dev
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next reply other threads:[~2010-10-28 6:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 6:59 Mitani [this message]
2010-10-28 17:44 ` [LTP] LTP make failed in recent git 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='000001cb766d$b3f5bbd0$1be13370$@co.jp' \
--to=mitani@ryobi.co.jp \
--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