similar to: R-3.6.2 make check fails

You're definitely missing bits of texlive. Lots of "missing file: mf" in your debug logs. I think you need to start with installing texlive-metafont. Alternately, there are pre-built R 3.6.2 packages for EL-7 here: https://koji.fedoraproject.org/koji/buildinfo?buildID=1421894 I cannot push them as official updates to EPEL because of the catch-22 created by R's dependency on

Thanks. Here are my results for the commands you list: > which pdflatex /bin/pdflatex > rpm -qf /usr/bin/pdflatex texlive-latex-bin-bin-svn14050.0-43.20130427_r30134.el7.noarch > cat /etc/redhat-release CentOS Linux release 7.7.1908 (Core) > rpm -qi texlive-latex-bin-bin-svn14050.0-43.20130427_r30134.el7.noarch Name : texlive-latex-bin-bin Epoch : 2 Version :

On Fri, 14 Feb 2020, Barris, Wes wrote: > 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. "make check" continues to fail.

>>>>> G?bor Cs?rdi <csardi.gabor at gmail.com> >>>>> on Thu, 8 Jan 2015 17:18:27 -0500 writes: > Dear all, > I am getting an R CMD check warning about the PDF manual. I am having a > hard time finding out what is wrong, here is the log of the Rd2pdf call. > The full check (and other) log is at >

Could someone tell me how to end the trouble I'm encountering when running latex on the .tex file produced by Sweave()? Sweave() seems to process the example file (http://www.ci.tuwien.ac.at/~leisch/Sweave/example-1.Snw) without problems, and the file example-1.tex produced is the same as in the Sweave manual. However, when I run latex on example-1.tex, many error messages and requests for

Dear all, I am getting an R CMD check warning about the PDF manual. I am having a hard time finding out what is wrong, here is the log of the Rd2pdf call. The full check (and other) log is at https://api.travis-ci.org/jobs/46373922/log.txt?deansi=true if anybody is interested, and the package itself is here: https://github.com/metacran/r-builder/tree/bintex/rbuildertest Thanks, Best, Gabor

Hi all I am trying to build an R package, which I have successfully done many times before, but have an error I cannot trace. I hope someone can help me. Here's is some edited output (full output below if it is useful): pdunn2 at PDunnUbuntu:~/DSdata$ R CMD build GLMsData * checking for file 'GLMsData/DESCRIPTION' ... OK * preparing 'GLMsData': * checking DESCRIPTION

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

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

Suppose I have a function funcA() in package pkgA that requires function funcB() from another package pkgB under certain circumstances. Those circumstances are rare though, so I put package pkgB under 'Suggests', and use this in funcA() when those circumstances do arise: if (require("pkgB", quietly=TRUE)) { pkgB::funcB(...) } else { stop("Please install package

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

On 05/29/2018 04:53 PM, Dirk Eddelbuettel wrote: > I noticed it with a local, not-public package -- but it appears to apply with > any source package. I replicated with pkgKitten straight off CRAN and after > checking that it has a six page manual there. I'm having trouble reproducing this one. In my fresh CentOS 7 VM, I can pull the pkgKitten source down, and run R CMD Rd2pdf

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

Tom, On 30 May 2018 at 11:34, Tom Callaway wrote: | On 05/29/2018 04:53 PM, Dirk Eddelbuettel wrote: | > I noticed it with a local, not-public package -- but it appears to apply with | > any source package. I replicated with pkgKitten straight off CRAN and after | > checking that it has a six page manual there. | | I'm having trouble reproducing this one. In my fresh CentOS 7 VM, I

I am only reporting this because it is the current release branch and not devel. R-2.13 from svn revision 55957 builds fine, but fails make check. This happened with a fresh svn checkout 12 hours ago and it still happens as of now. Two days ago I could build R-2.13 and it passed make check on the same system, so I doubt it is a system problem. But just in case my system details are a fresh

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

Dear all, I want to start my post by expressing my sincere gratitude for all the help this group has given me in Sweave/Latex/R. The tools are excellent and so is the community! On to the question. My Sweave code is intended to make lots of plots and create a *.pdf document. Sweave is perfect for this. The only problem is that I find myself using the same R code, within my Sweave input file

Hi Sebastian, On Thursday, 23 August 2018 16:45:27 CEST Sebastian Meyer wrote: > The `-l` option for some `zypper` subcommands is short for > `--auto-agree-with-licenses` and not available on the `zypper rm` command. > No problem with the patch, just one question: can it happen that zypper may decide to install packages when removing others, e.g. to keep some other

On a CentOS 7 machine, I am at a loss with respect to an inability to run a full R CMD check as anything involving tex files ends in tears. We followed the README at CRAN and installed a large number of tex-live packages on this machine. But when a manual is created, we end up with what follows below. Here, I chopped some of the error messages, the key seems to be 'Insufficient extension

Hi, The following command: R CMD Rd2pdf --no-preview --output=./tmp.pdf --title=test genefu-package.Rd run against this file: https://hedgehog.fhcrc.org/bioconductor/trunk/madman/Rpacks/genefu/man/genefu-package.Rd (username: readonly; password: readonly) produces a very verbose error (see below) with R version 2.15.0 alpha (2012-03-07 r58622). The .Rd file has these lines in it: Version: \tab