build rule for t0 in open_posix_testsuite
PATCH 1/1 build rule for t0 in open_posix_testsuite
Hi,
I propose two patches (two patterns of fix) for an issue of open_posix_testsuite. I hope either one of them (or more better one someone will write) is committed.
You need to do three steps below in order to run execute.sh of open_posix_testsuite:
1) make build-tests
2) cc -O2 -o t0 t0.c
3) ./execute.sh
I think it's better to include step 2 into step 1 or 3 for convenience. So I wrote two different patches for these cases.
Regards,
Index: ltp/testcases/open_posix_testsuite/Makefile
===================================================================
RCS file: /cvsroot/ltp/ltp/testcases/open_posix_testsuite/Makefile,v retrieving revision 1.25
testcases/open_posix_testsuite/Makefile +3 -3
@@ -76,7 +76,7 @@ # Rule to run a build test # If the .o doesn't export main, then we don't need to link .PRECIOUS: %.test -%.test: %.o +%.test: %.o $(top_builddir)/t0 @COMPLOG=$(LOGFILE).$$$$; \ [ -f $< ] || exit 0; \ { nm -g $< | grep -q ' T main\| D main'; } || \
@@ -96,7 +96,7 @@ # Rule to run an executable test # If it is only a build test, then the binary exist, so we don't need to run .PHONY: %.run-test -%.run-test: %.test $(top_builddir)/t0 $(top_builddir)/t0.val +%.run-test: %.test $(top_builddir)/t0.val @COMPLOG=$(LOGFILE).$$$$; \ [ -f $< ] || exit 0; \ $(TIMEOUT) $< > $$COMPLOG 2>&1; \
@@ -144,7 +144,7 @@ $(top_builddir)/t0.val: $(top_builddir)/t0 echo `$(top_builddir)/t0 0; echo $$?` > $(top_builddir)/t0.val -%.run-test: %.sh $(top_builddir)/t0 $(top_builddir)/t0.val +%.run-test: %.sh $(top_builddir)/t0.val @COMPLOG=$(LOGFILE).$$$$; \ chmod +x $<; \ $(TIMEOUT) $< > $$COMPLOG 2>&1; \
Index: ltp/testcases/open_posix_testsuite/execute.sh
===================================================================
RCS file: /cvsroot/ltp/ltp/testcases/open_posix_testsuite/execute.sh,v retrieving revision 1.3
testcases/open_posix_testsuite/execute.sh +5 -2
@@ -166,8 +166,11 @@ # Maximum five minutes waiting time period to execute a test. If it exceeds, the test case will go into the 'HUNG' category. TIMEOUT_VAL=300 -# if gcc available then remove the below line comment else put the t0 in posixtestsuite directory. -#gcc -o t0 t0.c +if [ ! -x t0 ] +then + cc -O2 -o t0 t0.c +fi + ./t0 0 > /dev/null 2>&1 TIMEVAL_RET=$?
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list
Quoted 8 lines · Seiichi Ikarashi
Hi,
I propose two patches (two patterns of fix) for an issue of
open_posix_testsuite. I hope either one of them (or more better one someone will write) is committed.You need to do three steps below in order to run
execute.shofopen_posix_testsuite:
1) make build-tests
2) cc -O2 -o t0t0.c
I prefer the first patch, as, all build items should be combined and completed before any actual execution.
Regards--
Subrata
Quoted 7 lines
3) ./execute.sh
I think it's better to include step 2 into step 1 or 3 for convenience. So I wrote two different patches for these cases.
Signed-off-by Seiichi Ikarashi <[email protected]>
Quoted 7 lines
Regards,
------------------------------------------------------------------------------
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 [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Ltp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list