Hello! In Writing R Extensions manual, section "Testing R code"[1] says: "be careful to check if make test-Specific or particularly, cd tests; make no-segfault.Rout" Actually, make test-Specific also needs "cd tests;" in front. [1]http://cran.r-project.org/doc/manuals/R-exts.html#Testing-R-code -- Lep pozdrav / With regards, Gregor Gorjanc ---------------------------------------------------------------------- University of Ljubljana PhD student Biotechnical Faculty Zootechnical Department URI: http://www.bfro.uni-lj.si/MR/ggorjan Groblje 3 mail: gregor.gorjanc <at> bfro.uni-lj.si SI-1230 Domzale tel: +386 (0)1 72 17 861 Slovenia, Europe fax: +386 (0)1 72 17 888 ---------------------------------------------------------------------- "One must learn by doing the thing; for though you think you know it, you have no certainty until you try." Sophocles ~ 450 B.C.
[Gregor Gorjanc]>In Writing R Extensions manual, section "Testing R code"[1] says: >"be careful to check if make test-Specific or particularly, cd tests; >make no-segfault.Rout">Actually, make test-Specific also needs "cd tests;" in front.>[1]http://cran.r-project.org/doc/manuals/R-exts.html#Testing-R-codeAllow me a quick comment about using "cd" in Makefiles, reading by. Whenever possible, prefer "cd DIR && ACTION" to "cd DIR; ACTION". This protects you from ACTION when it has some destructive effect, and DIR either happens to not exist or is just mistyped, in which case ACTION is executed in the current directory. A little good habit that saved me a few times along all those years! :-) -- Fran?ois Pinard http://pinard.progiciels-bpi.ca