From stefan.theussl at wu-wien.ac.at  Tue Apr 29 10:45:51 2008
From: stefan.theussl at wu-wien.ac.at (Stefan Theussl)
Date: Tue, 29 Apr 2008 10:45:51 +0200
Subject: [Rd] R-Forge SVN repositories: R CMD build/check error on
 Windows machines
In-Reply-To: <eb555e660804281522s7b8565e9o308a5864a733e12c@mail.gmail.com>
References: <4815F9C8.80209@wu-wien.ac.at> <48163158.2050802@stats.uwo.ca>	
	<alpine.LFD.1.10.0804282218510.18306@gannet.stats.ox.ac.uk>
	<eb555e660804281522s7b8565e9o308a5864a733e12c@mail.gmail.com>
Message-ID: <4816E03F.8030904@wu-wien.ac.at>

Deepayan Sarkar wrote:
> On 4/28/08, Prof Brian Ripley <ripley at stats.ox.ac.uk> wrote:
>   
>> The difference is in INSTALL, not build/check.
>>
>>  You are right that the Unix INSTALL was changed in r25808 (Aug 2003), but
>> AFAICS this was not documented at the time in [O]NEWS, nor anywhere else.
>>
>>  Can you point me to the documentation you used to implement this?
>>     
>
> FWIW, the NEWS for 2.5.0 [1] has
>
>     o	R CMD build now takes the package name from the DESCRIPTION
> 	file and not from the directory.  (PR#9266)
>
> and that does seem to work on Windows.
>   
Indeed, this works but with the side effect of getting the error message

Error in findpack(package, lib.loc) : there is no package called 'pkg'
Calls: <Anonymous> -> findpack
Execution halted
make[2]: *** [lazyload] Error 1
make[1]: *** [all] Error 2
make: *** [pkg-pkg] Error 2
*** Installation of pkg failed ***

which comes from R CMD INSTALL as Brian Ripley pointed out already.
Nevertheless, the package gets built and you can handle the tarball with 
no further problems as always.

Stefan
> [1] https://stat.ethz.ch/pipermail/r-announce/2007/000828.html
>
> -Deepayan
>



[Rd] R-Forge SVN repositories: R CMD build/check error on Windows machines
Stefan Theussl