Prof Brian Ripley wrote:
> Where is 'a' installed?
>
> You may need to set R_LIBS: R CMD check is not looking in any of your
> startup files such as ~/.Renviron.
Thanks! That worked. (And in fact, I now see it in "Writing R Extensions").
-Tim
>
> I don't believe this is a Windows/Unix issue,
Where is 'a' installed?
You may need to set R_LIBS: R CMD check is not looking in any of your
startup files such as ~/.Renviron.
I don't believe this is a Windows/Unix issue, but rather one of the local
R environment.
On Sat, 9 Jun 2007, Tim Bergsma wrote:
> Duncan,
>
> Yes, that was a typo o
Duncan,
Yes, that was a typo on line three. Sorry.
$version.string
[1] "Version 2.3.1 (2006-06-01)".
Thanks,
Tim.
Duncan Murdoch wrote:
> On 08/06/2007 4:01 PM, Tim Bergsma wrote:
>> I normally work in Windows, but make my packages under Unix. My
>> package 'b' suggests my package 'a'. R
On 08/06/2007 4:01 PM, Tim Bergsma wrote:
> I normally work in Windows, but make my packages under Unix. My package
> 'b' suggests my package 'a'. R CMD check fails for 'b', even though 'a'
> is installed: "Packages required but not available: b". What do I have
> to do to make 'a' available,
I normally work in Windows, but make my packages under Unix. My package
'b' suggests my package 'a'. R CMD check fails for 'b', even though 'a'
is installed: "Packages required but not available: b". What do I have
to do to make 'a' available, besides R CMD INSTALL 'a'? I'm not
spotting the