search for: basepkgs

...| !is.null(attr(as.environment(x), "path"))) package <- sub("^package:", "", package[keep]) } pkgDesc <- lapply(package, packageDescription) if (length(package) == 0) stop("no valid packages were specified") basePkgs <- sapply(pkgDesc, function(x) !is.null(x$Priority) && x$Priority == "base") z$basePkgs <- package[basePkgs] if (any(!basePkgs)) { z$otherPkgs <- pkgDesc[!basePkgs] names(z$otherPkgs) <- package[!basePkgs] } loadedOnly <- loa...

On Thu, 11 Jan 2024 09:30:55 +1300 Simon Urbanek <simon.urbanek at R-project.org> wrote: > That said, WHICH is a mess - it may make sense to switch to the > command -v built-in which is part of POSIX (where available - which > is almost everywhere today) which would not require an external tool This is a bit tricky to implement. I've prepared the patch at the end of this

On 2015-12-18 02:29, Simon Urbanek wrote: > Michael, > > I got access to PDP AIX so I can try to replicate your problem. Can you, please, share exactly your setup - AIX version and well as how exactly you installed the compilers (=where from)? I can then try to replicate it. AFAICS there is no official binary for gfortran nor gcc 4.7 so it must be some 3rd party - which could also be a

Hi, It's unfortunate that with recent revisions of R 2.13 (this appeared in revision 54640, March 2), 'R CMD build' now removes empty dirs in the package. People might have good reasons for having empty dirs in their packages. For example, in Bioconductor, we have some tools to automatically generate annotation packages and those tools are implemented in software packages that use

Dear list, I'm following the instructions provided here to compile R 64 bit on AIX 6.1. I did export OBJECT_MODE=64 export CC="gcc -maix64 -pthread" export CXX="g++ -maix64 -pthread" export FC="gfortran -maix64 -pthread" export F77="gfortran -maix64 -pthread" export CFLAGS="-O2 -g -mcpu=power6" export FFLAGS="-O2 -g -mcpu=power6"

I recently got a request to add head() and tail() methods for Surv objects, which is quite reasonable, but not unlike other requests for logLik,? vcov, extractAIC, ...?? What they all have in common is that are methods added since creation of the survival package, and that I didn't know they existed. To try and get ahead of the curve, is there a way to list names of all of the default

Hi, This problem started as of r73472 ("Merged in the rest of the basic ALTREP framework."); I tested r73471 and it did not exist. I'm building R devel on Ubuntu 16.04.3 LTS (64-bit), with the following flags: CC="gcc -std=gnu99 -fsanitize=address -fno-omit-frame-pointer" CFLAGS="-fno-omit-frame-pointer -g -O2 -Wall -pedantic -mtune=native" and using

I have been struggling with this error message - and think I finally understand it's context. Start Line by line debugging shows me the function works: ... > saveRDS(val, mapfile) > val $variables $variables$IANA_HTTP_status_code_db [1] 0 1256 $variables$IANA_URI_scheme_db [1] 1256 3458 $variables$table_of_HTTP_status_codes [1] 4714 830 $references named list() $compressed

Hi, I am getting the following error # (R-2.9.1/src/library/methods): gmake front /bin/sh: 0403-057 Syntax error at line 1 : `;' is not expected. gmake: *** [front] Error 2 However, I am not sure what script sh is trying to execute at this point. I am building on AIX 5.3. Cheers, Loris -- Dr. Loris Bennett Computer Centre Freie Universit?t Berlin Berlin, Germany

Full_Name: Rodney Sparapani Version: 2.9.2 OS: Solaris 10 Submission from: (NULL) (141.106.121.40) There are a few issues with building on Solaris (and UNIX in general, I suppose). 1. on line 50686 of configure, I'm seeing some trouble: lib=`echo ${lib}|sed -e s:${JAVA_HOME}:\$\{JAVA_HOME\}:g` Evidently, $lib contains colons which will confuse sed, so you can work around this like:

Please note that if I don't specify those variables, then R 32 bit compiles fine. Thanks. -- Vinh On Thu, Oct 8, 2015 at 6:50 PM, Vinh Nguyen <vinhdizzo at gmail.com> wrote: > Dear list, > > I'm following the instructions provided here to compile R 64 bit on > AIX 6.1. I did > > export OBJECT_MODE=64 > export CC="gcc -maix64 -pthread" > export

Dear R-Support Team: I am fully aware that you are all extremely busy and forward this request as brief and clear as possible: Thank you for the comprehensive Documentation for R-4.3.1 (very helpful) A limitation seems to have emerged, using SuSE SP15.4 (kernel: 5.14.21-150400.22) on an INTEL Skylake-e SERVER, applying both the GNU and Intel (2023.0.0) compilers. a) The

Hope I am not sounding too much like a broken record - as far as 64-bit build on AIX is concerned. ** Short - 32-bit builds complete normally, 64-bit builds stop at "installing 'sysdata.rda'" with message: Error: Line starting 'Package: tools ...' is malformed! Execution halted *** Longer... I could file a bug - Importance, showstopper - but I would prefer to better

I have been looking further and need some help with: tools:::sysdata2LazyLoadDB("/data/prj/cran/R-3.2.3/src/library/tools/R/sysdata.rda","../../../library/tools/R") Error: Line starting 'Package: tools ...' is malformed! Details: root at x065:[/data/prj/cran/64/R-3.2.3/src/library/tools]export | egrep "PATH|HOME" HOME=/