similar to: 1.7.1 make check fails (PR#3282)

Displaying 20 results from an estimated 8000 matches similar to: "1.7.1 make check fails (PR#3282)"

2002 Sep 18
1
problem with make fullcheck on Sparc Solaris 8
I have been trying out R-1.6.0 tarballs (2002-9-10 and 2002-9-17) on: arch sparc os solaris2.8 system sparc, solaris2.8 status beta major 1 minor 6.0 year 2002 month 09 day 17 language R As you see form above, R-1.6.0 compiles fine and works. However, when I "make fullcheck" I get the following error: running code in 'tools-Ex.R' ... OK
2003 Oct 01
1
R-1.7.1 for Redhat 9
Dear, I have problems with installing R-1.7.1 for Redhat 9. When I applied `./configure' and `make', I get the following error: make check make[1]: Entering directory `/volume1/scratch/jallemee/R-1.7.1/tests' make[2]: Entering directory `/volume1/scratch/jallemee/R-1.7.1/tests' make[3]: Entering directory `/volume1/scratch/jallemee/R-1.7.1/tests/Examples' make[4]: Entering
2001 Sep 14
3
R Installation problem: 'make check' errors
Hi All, I'm trying to install R from source on an Intel machine running Linux (RedHat 6.2) and I am getting errors (Error 139, Error 2, and Error 1) on 'make check'. Perhaps I've forgotten something basic? --------------------------------------------------------------------- Here's what I've done: /configure --prefix=/home1/froth/R --enable-R-shlib --with-tcltk
2004 Feb 15
2
build problems on Fedora Core 1
Hello... I tried to build R-devel today on Fedora Core 1 (with gcc 3.3.2) but I am running into a couple of errors. On the same system R-1.8.1 compiles just fine, as did a previous version of R-devel. This is what I did: # change LANG as default in FC1 is UTF-8 export LANG=en_US.ISO8859-1 export LANGVAR=en_US.ISO8859-1 # get fresh sources and configure mkdir R-devel rsync -vrC
2002 Jul 11
1
dyn.load tcl/tk (PR#1774)
<<insert bug report here>> ------------------------------------------------------ Error: R : Copyright 2002, The R Development Core Team Version 1.5.1 (2002-06-17) R is free software and comes with ABSOLUTELY NO WARRANTY. You are welcome to redistribute it under certain conditions. Type `license()' or `licence()' for distribution details. R is a collaborative project with
2004 Oct 20
1
Unable to compile dovecot with Solaris 9 and Forte C
Just a "heads up". I tried to search mailinglist archives and wiki, but found no similar configurations. Dovecot is unbuildable with the following configuration: SunOS mail 5.9 Generic_112233-08 sun4u sparc SUNW,Sun-Fire-V210 cc: Forte Developer 7 C 5.4 2002/03/09 config.log output from ./configure is at: http://iso.ego.fi/misc/dovecot_1.0-test50.log I guess I'll have to bend
2004 May 03
1
./configure on SunOS does not run to completion
OS: SunOS human 5.9 Generic_112233-12 sun4u sparc SUNW,Sun-Fire-480R I run ./configure --prefix=/non/standard/path ... and it stops at the line checking for xmkmf... /usr/openwin/bin/xmkmf Sincerely Eryk
2003 Aug 07
5
gregmisc
Hi How do I install "gregmisc" packages? I did- % sudo R > install.packages("gregmisc") . . > barplot2() but, Error: couldn't find function "barplot2" -- atuya Mac OSX 10.2.6 R 1.7.1
2005 Sep 26
1
Make check fails on d-p-q-r-tests.R...
Hi, R-2.1.1 OS: OpenBSD-current (3.8) on i386 Compiler:gcc version 3.3.5 (propolice) Thread model: single configure \ --with-readline \ --with-tcltk \ --with-tcl-config=/usr/local/lib/tcl8.4/tclConfig.sh \ --with-tk-config=/usr/local/lib/tk8.4/tkConfig.sh \ --with-libpng \ --with-jpeglib \ --with-zlib \ --with-bzlib \ --with-pcre \ --with-libiconv-prefix=/usr/local/
2001 Apr 26
3
Installing smooth.spline command
Hello I have installed R-0.90.1 on my Linux (Redhat 6.2) machine, unfortunately I am not able to use a number of commands like e.g. smooth.spline and predict.smooth.spline. The error messages being given by is: Error: Object "smooth.spline" not found With the command library() I have checked or the libraries for the smoothing functions are there, as shown below. -------- >
1999 Jun 09
4
packages with FORTRAN code
Recent sensible changes to the dynload mechanism have made an old problem resurface: how should we deal with packages which contain Fortran code and may need to be linked against additional libraries such as -lf2c? The current consensus is that extra Fortran libraries maybe needed are handled via the make variable FLIBS, and that `-lf2c' or `-lg2c' are added by default if g77 is used.
2003 Oct 29
2
/usr/lib/R/library vs /usr/local/lib/R/site-library
I would appreciate getting a clarification of /usr/lib/R/library vs /usr/local/lib/R/site-library. I am running R 1.8 on Debian Linux. On one occasion doing update.packages() resulted in versions of one or more libraries being placed in one of these directories without removing the old version, and the old version took precedence over the new. I'm sorry I did not save the steps I used. I
1999 May 03
0
compilation of R-0.63.3 on alpha (PR#183)
This is a multipart MIME message. --==_Exmh_981436288450 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Hi ! I have problems compiling R successfully on a DEC-UINX 4.0E. I have applied the recommended config.site, which I enclose. As can be seen from the compilation log there are linking errors... I did a 'make check' which fails for the R
2000 Feb 17
2
Installation of rpm file on Suse Linux 6.2 (PR#449)
Full_Name: Luzi P. Schucan Version: R-base-0.90.1-2.i386.rpm OS: Linux Submission from: (NULL) (141.84.136.129) I just wanted to install the rpm package with rpm --v -i [file], and here is the log: (I DID run it as root!!) (the important thing is in the end: there must be a bug in the post install script. The problem is, that it does install all the files, but it doesn't correctly hang the
2003 Sep 25
1
rpmbuild of src.rpm error
I received an error trying to build R-1.7.1-src.rpm on RH9.0.93 (Severn) and I was wondering if anybody could tell me what is going on with the manual error. + cp -pr 'doc/manual/R-*.pdf' /var/tmp/R-root/usr/share/doc/R-1.7.1 cp: cannot stat `doc/manual/R-*.pdf': No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.78384 (%doc) Processing files: R-debuginfo-1.7.1-1 +
2003 Jun 24
3
R-1.7.1 regression test failure on alphaev68-dec-osf5.1
I'm attempting to compile and install R version 1.7.1 for my statistical geneticists. It seems to compile correctly -- that is, it compiles without errors -- but the regression test is failing in the following manner: =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > ## log > stopifnot(all.equal(log(1:10), log(1:10, exp(1)))) > stopifnot(all.equal(log10(30), log(30, 10))) >
2003 Jul 29
1
OpenBSD-alpha and R-1.7.1 problem
I'm trying to get R running on OpenBSD/alpha. I've applied some configure patches which I've previously sent to the R-devel list to allow R to compile on an OpenBSD ELF platform (which OpenBSD/alpha is, as the i386 port soon will be). The patched source compiles without problems, and appears to run and perform properly apart from two (possibly unrelated) problems. 1) On startup
2003 Jul 31
1
R on Solaris 9
I am attempting an install of R-1.7.1 on a Sun Solaris 9 box. It is a V880. It has 8 processors at 950MHz each and 32 Gb of physical memory. I can './configure' and after, I get the following: ---------------------------------------------------------------------------- ------------ R is now configured for sparc-sun-solaris2.9 Source directory: . Installation
2002 Nov 20
4
Improving R Editing: New JEdit Edit Mode for R
Hi all, I have created a new edit mode file for the editor JEdit (http://www.jedit.org) based on the file from Zed Shaw. The difference between his and my file is that mine can be used as a spell checker. It does not highlight all functions but provides syntax highlighting for the base package (keyword types 1 and 2) and 26 additional packages (boot, class, cluster, ctest, eda, foreign, grid,
2003 Sep 25
2
Bugs compiling R-1.7.1 with Intel compilers icc and ifc (PR#4295)
Bugs compiling R-1.7.1 with Intel compilers icc and ifc, on x86-computer (Pentium IV) and linux operating system Hello, as there aren't many reports about that issue, I'll give a little report here. (Hope I don't bother anyone) The best thing about using icc and ifc are the warnings, because it is said that the Intel compilers are stricter and give more precise warnings than gcc.