I'm really sorry that I had to disturb you (for nothing) because everything looks fine now ( why ??). After I build again the package with search() in the "Rsq.2.array" examples, I didn't get any Error.
The only things that I changed it's the directory where is build the package. The package directory path is located on a different drive (USB KEY) from where it was build (HARDRIVE).This return the Error. Now I build the package on the same drive (both in the USB KEY). I try it with the last stable version R-2.11.0 and the patched version Patched (2010-04-28 r51857) /media/HAMID$ ~/Desktop/R-2.11.0/bin/R CMD build eqtl/ * checking for file 'eqtl/DESCRIPTION' ... OK * preparing 'eqtl': * checking DESCRIPTION meta-information ... OK * removing junk files * checking for LF line-endings in source and make files * checking for empty or unneeded directories * building 'eqtl_1.1.tar.gz' /media/HAMID$ ~/Desktop/R-2.11.0/bin/R CMD check eqtl_1.1.tar.gz * checking for working pdflatex ... OK * using log directory '/media/HAMID/eqtl.Rcheck' * using R version 2.11.0 (2010-04-22) * using session charset: UTF-8 * checking for file 'eqtl/DESCRIPTION' ... OK * checking extension type ... Package * this is package 'eqtl' version '1.1' * checking package dependencies ... OK * checking if this is a source package ... OK * checking for executable files ... OK * checking whether package 'eqtl' can be installed ... OK * checking package directory ... OK * checking for portable file names ... OK * checking for sufficient/correct file permissions ... OK * checking DESCRIPTION meta-information ... OK * checking top-level files ... OK * checking index information ... OK * checking package subdirectories ... OK * checking R files for non-ASCII characters ... OK * checking R files for syntax errors ... OK * checking whether the package can be loaded ... OK * checking whether the package can be loaded with stated dependencies ... OK * checking whether the package can be unloaded cleanly ... OK * checking for unstated dependencies in R code ... OK * checking S3 generic/method consistency ... OK * checking replacement functions ... OK * checking foreign function calls ... OK * checking R code for possible problems ... OK * checking Rd files ... OK * checking Rd metadata ... OK * checking Rd cross-references ... OK * checking for missing documentation entries ... OK * checking for code/documentation mismatches ... OK * checking Rd \usage sections ... OK * checking Rd contents ... OK * checking data for non-ASCII characters ... OK * checking examples ... OK * checking PDF version of manual ... OK It doesn't really look to be a user autorisation problems. Do you think it's a problem related only to my computer or should I report it as a bug ? thks a lot, ______________________________________________ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel