Marc Schwartz (via MN) writes:
On Tue, 2006-09-19 at 22:16 +1000, Robert King wrote:
Here is another thing that might help work out what is happening. If I
use --no-install, ade4 actually fails as well, in the same way as zipfR.
[Desktop]$ R CMD check --no-install ade4
* checking for
On Wed, 2006-09-20 at 13:20 +0200, Kurt Hornik wrote:
Marc Schwartz (via MN) writes:
On Tue, 2006-09-19 at 22:16 +1000, Robert King wrote:
Here is another thing that might help work out what is happening. If I
use --no-install, ade4 actually fails as well, in the same way as zipfR.
Robert King [EMAIL PROTECTED] writes:
I'm testing a FC5 machine for use in a student lab. R 2.3.1 is installed and
seems to work fine. There is one peculiarity - the logins are authenticating
to a server, and a verbose flag is set somewhere, leading to lots of
spurious messages like this
No output from the tools command
Peter Dalgaard wrote:
Robert King [EMAIL PROTECTED] writes:
I'm testing a FC5 machine for use in a student lab. R 2.3.1 is installed
and
seems to work fine. There is one peculiarity - the logins are
authenticating
to a server, and a verbose flag is
Here is another thing that might help work out what is happening. If I
use --no-install, ade4 actually fails as well, in the same way as zipfR.
[Desktop]$ R CMD check --no-install ade4
* checking for working latex ... OK
* using log directory '/home/rak776/Desktop/ade4.Rcheck'
* using
On Tue, 2006-09-19 at 22:16 +1000, Robert King wrote:
Here is another thing that might help work out what is happening. If I
use --no-install, ade4 actually fails as well, in the same way as zipfR.
[Desktop]$ R CMD check --no-install ade4
* checking for working latex ... OK
* using
I'm testing a FC5 machine for use in a student lab. R 2.3.1 is installed and
seems to work fine. There is one peculiarity - the logins are authenticating
to a server, and a verbose flag is set somewhere, leading to lots of
spurious messages like this
request done: ld 0xa227598 msgid 1
which
