Displaying 20 results from an estimated 500 matches similar to: "r-2.13 fails make check"
2012 Oct 13
0
installation of R (2.14.1 and 2.15.1) fails due to [reg-packages.Rout] Error
Hello,
I'm trying to install R from sources on two Linux machines (both with Suse 12.2):
1.
> uname -a
Linux cs-wsok 3.4.6-2.10-desktop #1 SMP PREEMPT Thu Jul 26 09:36:26 UTC
2012 (641c197) x86_64 x86_64 x86_64 GNU/Linux
2.
> uname -a
Linux csltok.swansea.ac.uk 3.4.6-2.10-desktop #1 SMP PREEMPT Thu Jul 26
09:36:26 UTC 2012 (641c197) x86_64 x86_64 x86_64 GNU/Linux
I am trying version
2020 Feb 14
3
R-3.6.2 make check fails
I am trying to build the latest version of R (3.6.2) on a CentOS system running 7.7.1908.
I have been able to build previous versions of R up to and including 3.5.3 successfully. Starting with 3.6.0
the "make check" step fails with errors relating to "pdflatex" being missing. So, I installed texlive-latex
(and the 100 other rpm dependencies) then tried rebuilding R.
2016 Apr 20
3
Fresh build from source of R-3.2.5 failing "make check" under 64-bit Ubuntu
Hi,
Let me justify building R from source. While I can obtain R built for me
under Ubuntu, I tend to build it from scratch as we use a NFS-shared
build as well as shared R libraries for all the bioinfo staff at this
company. Only one build and one set of packages to ensure uniformity
across all workstations.
My problem is that despite using a pretty standard build process, I am
failing at the
2015 Sep 16
2
R-devel_2015-09-14 throws an error in reg-packages test
Hello.
I have successfully built R on windows scores of times, and have never
come across this problem. For this build, I am using the current 4.6.3
prerelease version of Rtools, Windows7 64 bit, and
R-devel_2015-09-14.tar.gz
When running make check, I get the following error:
running code in 'reg-packages.R' ...make[3]: *** [reg-packages.Rout] Error 1
make[2]: *** [test-Reg] Error 2
2016 Apr 21
0
Fresh build from source of R-3.2.5 failing "make check" under 64-bit Ubuntu [SOLVED]
Testing for an NFS effect on the failure of 'make check':
Try first on /usr/local/
9:42 cd /usr/local/src/
9:42 sudo mkdir R
9:43 sudo chown mdalphin:mdalphin R
9:43 cd R
9:43 gunzip -c /opt/apps/x86_64/R/Archive/R-3.2.5.tar.gz | tar xf -
9:43 cd R-3.2.5/
9:44 ./configure --prefix=/opt/apps/x86_64/R/R-3.2.5 LIBnn=lib
9:44 make
9:57 make check
2009 Oct 23
2
reg-tests-1.R failure with unstable
Hi,
I am getting an error from one of the test files
tests/reg-tests-1.R using the unstable version (r50179).
(i've learned my lessons; this is a clean build.) The tail
of reg-tests-1.Rout.fail is
Loading required package: myTst
building package pkgA ...
installing package pkgA using file pkgA_1.0.tar.gz ...
Error in as.octmode(mode) : invalid digits
Error in install.packages(r, lib =
2013 Feb 08
1
ClassNotFoundException when running distributed job using rJava package
Hi,
I have a MapReduce Java code, which I am calling from R using rJava. I have
prepared the R package and tested that successfully. But when I deployed
the package in a cluster and executed it, I am getting
ClassNotFoundException. If I run the same job directly without integrating
with R, it runs perfectly.
Here is my R code:
library(rJava)
muMstSpark <- function(mesosMaster = NULL, input =
2008 Oct 14
1
problem with update.packages (PR#13161)
On 14 October 2008 at 09:39, Simon Blomberg wrote:
| Hi, is anyone else getting this error? Could this be a bug?:
|
| > update.packages(ask=FALSE)
| Error in read.dcf(pkgpath, fields = fields) :
| Line starting 'unix; ...' is malformed!
|
| > sessionInfo()
| R version 2.8.0 RC (2008-10-12 r46696)
| x86_64-pc-linux-gnu
Confirmed in plain R using the same package built this
2008 Oct 14
1
problem with update.packages (PR#13161)
On 14 October 2008 at 09:39, Simon Blomberg wrote:
| Hi, is anyone else getting this error? Could this be a bug?:
|
| > update.packages(ask=FALSE)
| Error in read.dcf(pkgpath, fields = fields) :
| Line starting 'unix; ...' is malformed!
|
| > sessionInfo()
| R version 2.8.0 RC (2008-10-12 r46696)
| x86_64-pc-linux-gnu
Confirmed in plain R using the same package built this
2016 Feb 10
0
Method from package dependency is not updated due to lazy load?
Hi,
not sure this is a bug or just an unavoidable undesirable side-effect -- or
just me that does not do the right thing.
Consider the code and output below. It creates 2 packages:
* pkgA
* pkgB that creates a method for a generic defined in pkgA
Changes in a method for the generic in pkgA (after re-installing pkgA) are
not reflected in pkgB, unless pkgB is re-installed against the new
2007 Sep 18
1
Re-attaching a package environment drops the attributes
Hi.
contrary to other environments, the attributes of a *package*
environment are dropped (from the new environment) when attach():ing
it to the search() path. This might or might not be surprising, but
have some side effects if rearranging/attaching package environments.
# Example - Regular environments
env <- new.env()
attr(env, "foo") <- "bar"
print(env)
##
2015 Jul 03
1
Are downstream dependencies rebuilt when a package is updated on CRAN?
I was wondering: are the downstream dependencies of a package rebuilt
when a package is updated on CRAN? (I'm referring to the binary
packages, of course.)
The reason I ask is because there are cases where this can cause
problems. Suppose that when pkgB is built, it calls
pkgA::makeClosure(), which returns a closure that refers to a function
in pkgA. Suppose this code is in pkgA 1.0:
2013 Aug 30
2
"False" warning on "replacing previous import" when re-exporting identical object
Hi,
SETUP:
Consider three packages PkgA, PkgB and PkgC.
PkgA defines a generic function foo() and exports it;
export(foo)
PkgB imports PkgA::foo() and re-exports it;
importFrom(PkgA, foo)
export(foo)
PkgC imports everything from PkgA and PkgB:
imports(PkgA, PkgB)
PROBLEM:
Loading or attaching the namespace of PkgC will generate a warning:
replacing previous import by
2009 Mar 31
2
Wishlist: optional svn-revision number tag in package DESCRIPTION file
Hi,
just a little wish :
Could we have one (or maybe more) standardized optional tag(s)
for package DESCRIPTION files to cover svn revision info?
This would be very useful for bug reporting...
I know that any developer is already free to append corresponding lines
to DESCRIPTION files to do something of this sort --- e.g. lines like
LastChangedDate: {$LastChangedDate: 2009-03-31 $}
2002 Nov 18
2
library() help for Windows
Dear R users,
I have just upgraded R v1.5.0 to v1.6.1 for Windows but have trouble loading my library of R only functions (no C calls). After examining the "library" script this difference was found:
(v1.5.0)
which.lib.loc <- dirname(pkgpath)
descfile <- system.file("DESCRIPTION", package = package,
lib.loc = which.lib.loc)
if
2019 Jun 21
2
Suggested Patch: Library returns matching installed packages when typo present
Dear R-core devs,
I hope this email finds you well.
Please see the proposed patch to R-devel below:
Scenario:
When loading a package using `library`, a package may not be found if the cases are not matching:
```
> library(ORG.Hs.eg.db)
Error in library(ORG.Hs.eg.db) :
there is no package called 'ORG.Hs.eg.db'
```
Suggested Patch:
Returns a message matching what
2008 Oct 13
2
problem with update.packages
Hi, is anyone else getting this error? Could this be a bug?:
> update.packages(ask=FALSE)
Error in read.dcf(pkgpath, fields = fields) :
Line starting 'unix; ...' is malformed!
> sessionInfo()
R version 2.8.0 RC (2008-10-12 r46696)
x86_64-pc-linux-gnu
locale:
2009 Aug 17
2
S4 Generics and NAMESPACE : justified warning ?
Dear list,
It seems that a package (pkgB) using another package (pkgA) with S4
generics formed by taking existing functions (for example 'plot') must
not import the existing functions ('plot') in its namespace to avoid
the warning "replacing previous import: plot".
Suppose we use the simple 'import' directive in the name space of
pkgB.
pkgA and pkgB files would
2011 Oct 15
2
.onLoad failing because could not find function "loadMethod"
Hi,
This strange warning happen sometimes when running 'R CMD check':
* checking whether the package can be loaded with stated dependencies
... WARNING
Error : .onLoad failed in loadNamespace() for ?pkgB?, details:
call: length(new("A"))
error: could not find function "loadMethod"
Error: package/namespace load failed for ?pkgB?
Execution halted
2011 Dec 15
1
S4 NAMESPACE method imports and exports do not include (promoted?) generics
In
> R.version.string
[1] "R Under development (unstable) (2011-12-15 r57901)"
section 1.6.6 of 'Writing R Extensions' says
Note that exporting methods on a generic in the namespace will
also export the generic, and exporting a generic in the
namespace will also export its methods.
and
Note that importMethodsFrom will also import any generics defined in