similar to: make check fails tools-Ex in 2.5.0

Full_Name: Mike Pacey Version: 2.5.1 OS: SUSE SE Linux 9.3 Submission from: (NULL) (194.80.32.10) Versions 2.5.0 and 2.5.1 currently fail "make check" on my system due to a silent failure in the call to Rd_db("base"): ----- > ### Name: Rdutils > ### Title: Rd Utilities > ### Aliases: Rd_db Rd_parse > ### Keywords: utilities documentation > > ### **

Hi, I am reporting what seems to be a trivial error in one of the test files (this has been failing for a few days for me): Collecting examples for package 'tools' Running examples in package 'tools' Error: testing 'tools' failed Execution halted gmake[3]: *** [test-Examples-Base] Error 1 gmake[3]: Leaving directory `/usr/local/share/R-devel/tests/Examples' gmake[2]:

Hi folks, I suspect this is a request for a sanity check than a bug report: I've been successfully compiling an optimised version of R for several years using the Intel compiler and MKL. I've just test-run the new Intel 15.0 compiler suite, and I'm seeing a few numeric failures that I don't see using the same build method with Intel 13.0. I've attached the output of

System details: -------------- Sun Blade 1000, Solaris 8, Sun ONE Compiler Suite (rebranded Forte 7), R versions 1.6.0 and 1.6.2 - suspect others are affected, too Problem description: ------------------- Using the recommended env var setting from p.15 of the Admin Guide, the configure script fails the sgemm sunperf test, even though the sunperf libraries are available Not linking with

On Mon, 14 Jan 2019 16:27:04 -0500 Gilbert Soucy <gsoucy at 36pix.com> wrote: > Yes, I have tried testparam. All is OK . Note that I can write > anything for unix charset and testparm does not complain. > > Load smb config files from /etc/samba/smb.conf > rlimit_max: increasing rlimit_max (1024) to minimum Windows limit > (16384) Processing section

Good morning, we recently observed a problem with importing S3 generics from a foreign package (without namespace), defining a S3 method in a package _with_ namespace and the `cleanEx()' function which is automatically generated and executed before examples are run by R CMD check. To be more precise. Package `strucchange' defines a S3 generic sctest <- function(x, ...)

Dear R developers, When building/checking my package (in R 2.6.1 under windows) I run into some messages that I do not completely understand and that do not give me precise enough leads to pinpoint where the error in my package is. I would be very grateful for any suggestions. Did anyone else encounter the same problem before? When building or installing the package, I get the message (no error

Hello, I am trying to get rsync-3.0.0pre10 --iconv option working between two linux hosts in local network. The client host is running Fedora Core 4 (kernel 2.6.17) and is using iso8859-1 character set. LANG=en_US The daemon host is running Centos 5 (kernel 2.6.18) and is using utf-8 character set. LANG=en_US.UTF-8 Rsync is transferring files properly without --iconv switch: fc4: (connected

Hi, We found a (to our eyes) strange behaviour that might be a bug. First a little bit of context. The 'units' package allows us to set the unit using both SE or NSE. E.g., these both work in the same way: units::set_units(1:10, "?m") #> Units: [?m] #> [1] 1 2 3 4 5 6 7 8 9 10 units::set_units(1:10, ?m) #> Units: [?m] #> [1] 1 2 3 4 5 6 7 8 9 10

Hi (Duncan?), The other day I noticed some characters will cause errors in R CMD CHECK because of parse_Rd(), and AFAIK, these chars include '%', '{' and '}'. For example, note the comments in the example section: %~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~% \name{testfun} \Rdversion{1.1} \alias{testfun} \title{ A Test } \description{ A test } \usage{ testfun() } \value{ NULL }

Hello all, I have problems with sending data names via rsync including german characters like ??, ?, ??. The daemon running on a SLES10. The Rsync version is: 3.0.3, Protocol version:30. My Client is a Windows XP machine with Rsync: 3.0.4 (or alternative 3.0.6), Protocol version:30. For the conversion between both machines I use the ??iconv=850,UTF-8? ? switch. chcp told me that 850 is my

Am Mittwoch, 25. April 2018, 15:31:50 CEST schrieb Ali SIMON via samba: > Thanks Jeremy, > > i'm analyzing this with the application team, we'll see what we can > find. > > I was hoping to find a way for the samba4 server to behave like > > samba3 (as in ignoring bad characters and replacing them with an > > underscore character), which in the end resulted in

>From "Writing R Extensions": "Only ASCII characters (and the control characters tab, formfeed, LF and CR) should be used in code files." So I am afraid you cannot use ?m. Gabor On Mon, Feb 18, 2019 at 3:36 PM I?aki Ucar <iucar at fedoraproject.org> wrote: > > Hi, > > We found a (to our eyes) strange behaviour that might be a bug. First > a little

Hi all, This has been very frustrating for me trying to get this acts_as_ferret working well on a Fedora box. On my mac it works great, no problems with locale, but when I put the code live on my Fedora server, it complains about the locale setting (Error occured at <analysis.c>:498 Error: exception 2 not handled: Error decoding input string. Check that you have the locale set

Full_Name: Mike Pacey Version: 2.6.0 OS: SuSe Linux 9.3 x86_64 Submission from: (NULL) (194.80.32.10) A "vanilla" version of R configures and compiles without a problem on my system. Switching to using the PGI compiler configures correctly (see the values at the bottom fo thismessage), but compilation aborts with: pgcc -I../../src/extra/zlib -I../../src/extra/bzip2

Hello One of my packages, untb_1.3-2, passes R CMD check under MacOSX (and apparently the systems used in the package check summary page on CRAN) but fails with the following message on R-2.6.0.tgz compiled last night on my (home) linux box. I hasten to add that I have never seen this error before on home-compiled pre-releases of R-2.6.0. Can anyone help me understand what is going on?

I have a file which contains non-ASCII characters (umlauts, accented characters, etc.) both in its filename as well as its content. The only way I have been able to see these characters is inside vim, where they are displayed correctly no matter what I have LANG set to. My default LANG is en_US.utf8, but I have tried de_DE.utf8, de_DE.iso88591, and various others. In the output of a

I must be missing something obvious here: According to the help page for read.spss, the reencode option is only active when R is run under a UTF-8 locale. read.spss can only import the SPSS file when run under a iso88591(5) locale, under a UTF-8 locale I get: Error in read.spss("wo.sav") : error reading system-file header In addition: Warning message: In read.spss("wo.sav")

Full_Name: Mike Pacey Version: 2.0, 1.9.x OS: Solaris 8 Submission from: (NULL) (194.80.32.8) Symptoms: -------------- It seems the latest version of the Sun Compiler Suite (Forte 9) has compatability issues with R's configure script. Starting with a fairly vanilla configure (I'm using 1.9.1 here, but I've replicated the problem on 1.9.0 and 2.0.0): % export CC=cc % export F77=f95

Full_Name: Madeleine Yeh Version: 1.9.1 OS: AIX 5.2 Submission from: (NULL) (151.121.225.1) After compiling R-1.9.1 on AIX 5.2 using the IBM cc compiler, I ran the checks. One of them failed. Here is the output from running the check solo. root@svweb:/fsapps/test/build/R/1.9.1/R-1.9.1/tests/Examples: ># ../../bin/R --vanilla < stats-Ex.R R : Copyright 2004, The R