If you configure with a –prefix and then ‘make check’, it will fail unless you’ve done a ‘make install’. Here is the end of a ‘make check’ log showing this problem:

make[4]: Leaving directory /home/duraid/strategoxt-0.17M1pre13893/stratego-front/test' make[3]: Leaving directory/home/duraid/strategoxt-0.17M1pre13893/stratego-front/test’
./../parse/parse-stratego -i prop1.str -o prop.rtree –asfix
[ parse-stratego | error ] repository /opt/strategoxt/share/strategoxt/XTC does not exist
[ parse-stratego | error ] No XTC registration for StrategoRenamed.sdf found
make[2]: *** [check1] Error 1
make[2]: Leaving directory /home/duraid/strategoxt-0.17M1pre13893/stratego-front/test' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory/home/duraid/strategoxt-0.17M1pre13893/stratego-front’
make: *** [check-recursive] Error 1

(making ‘install’ then ‘check’ again, the test suite gets much, much further)

Submitted on 17 December 2005 at 16:14

STR-490, martin:
I agree this is desirable, but it is a lot of work I’m afraid … The checks are scathered all over the place and for most situations you have to think about how to solve it. The build-time XTC repository should solve most of the problems.

For now, scheduling for 0.18, considering the amount of work and the limited impact of the issue.