Skip to content
Prev 11561 / 398502 Next

Difficulty with R CMD INSTALL

On Sun, 3 Jun 2001 fharrell at virginia.edu wrote:

            
With what extension?

At that point in the install process we have

    if test -d R; then
      echo " R"
      mkdir -p ${lib}/${pkg}/R
      cat `ls R/*.[RSqrs] R/unix/*.[RSqrs] 2>/dev/null` \
        > ${lib}/${pkg}/R/${pkg}
    fi


This will get stuck if there is an R directory, but the files in it
do not have extensions R S q r or s.  See section 1.1.3 of `Writing R
extensions' for the rules.

That's a bug (getting stuck) fixed in R-devel and hence will be fixed in
1.3.0: from the CVS logs

revision 1.61
date: 2001/05/03 07:18:41;  author: ripley;  state: Exp;  lines: +6 -4
INSTALL failed if dir R was empty or had no suitable files


As a more general comment, R CMD build is intended to be the last stage of
the process, used after R CMD check (which checks that installation works).
When developing a package I tend to INSTALL it several times and run a few
tests each time, then use R CMD check --no-clean to refine it (not
re-installing from scratch each time), and finally R CMD check then R CMD
build.

Brian