similar to: 2.7.0 beta (rev 45263) failing 'make vignettes'

Displaying 20 results from an estimated 1000 matches similar to: "2.7.0 beta (rev 45263) failing 'make vignettes'"

2005 Oct 11
1
Hmisc latex function
I'm using R 2.2.0 on an up-to-date version of Fedora Core 4 with the latest version of Hmisc. When I run an example from the latex function I get the following: > x <- matrix(1:6, nrow=2, dimnames=list(c('a','b'),c('c','d','enLine 2'))) > x c d enLine 2 a 1 3 5 b 2 4 6 > latex(x) # creates x.tex in working directory sh:
2008 Oct 16
2
Xen 3.3 compile error - (LaTeX)
Hello, I''m having some problems compiling xen 3.3. Compiling ends by generating docs (latex). HW: AMD Phenom(tm) 9550 Quad-Core Processor 8GB RAM Debian GNU/Linux 4.0 \n \l 2.6.26.5 #1 SMP Sun Oct 5 19:36:29 CEST 2008 i686 GNU/Linux make[1]: Leaving directory `/home/adrian/xen-3.3.0/stubdom'' sh ./docs/check_pkgs && make -C docs install || true make[1]: Entering
2009 Sep 06
3
[Hmisc] Latex to pdf
I would like to print some tables and figures to a PDF device on a CentOS 5 vps. However, I cannot seem to get the latex function from Hmisc working. I followed the example, and got an error: sh: xdvi: command not found. I tried installing the 'tetex-xdvi' linux package, and now it returns: Error: Can't open display. I guess the reason for this is that the machine is a VPS terminal, so
2005 Oct 02
1
Problem Sweaving vignettes: MiKTeX's texi2dvi reports errors
Hi, I am trying to create a Bioconductor package. Everything installs and checks fine. Now I'm on my last step, which is to create a vignette. I'm trying to test the Sweave process, to make sure I can build a vignette. I am stuck at the texi2dvi stage, which fails when I try to process the example Sweave-test-1.tex file. I am using Windows binary R distributions, and have the same
2004 Aug 04
0
RE: Does tcltk matter for the plot
Hi Paul, I use executable codes of tex and latex from http://aixpdslib.seas.ucla.edu/packages/tetex.html) and compile the original R-1.9.1 source codes using C for AIX compiler V6.0 and Fortran for AIX compiler 7.1.1 and generate 64 bit R environments. It works well. Kexiao -----Original Message----- From: Paul Murrell [mailto:p.murrell at auckland.ac.nz] Sent: Monday, August 02, 2004 6:10
2007 Jun 21
2
Need Help: User Defined R Functions in Sweave/Latex
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
2004 Dec 29
3
Windows vignettes, shQuote, texi2dvi
I noticed a shQuote fix for Windows in the svn logs. Just wanted to point out that this will favorably affect texi2dvi on Windows which previously used UNIX quoting and so generated an incorrect Windows command. (Note that texi2dvi is used when creating vignettes.) Another problem is that the recommended tex distribution for Windows, fptex, does not have texi2dvi in the first place. The
2005 Jan 21
2
* creating vignettes ... ERROR
Dear R developers, I had some problem when building package: for exemple when building the package e1071 available from CRAN, I get the following message error: * checking for file 'e1071/DESCRIPTION' ... OK * preparing 'e1071': * cleaning src * running cleanup * creating vignettes ... ERROR /usr/lib/R/bin/texi2dvi: pdflatex exited with bad status, quitting.
2008 Jul 16
1
Checking package vignettes: WARNING
Hi, I want to have a "vignette" in one of my R packages. Hence, I added an Sweave file into the /inst/doc subdirectory of this package. Unfortunately, 'R CMD check' gives a warning: ========================================== [...] * checking tests ... OK * checking package vignettes in 'inst/doc' ... WARNING --- f?hre texi2dvi auf Vignetten aus * creating
2013 Sep 24
1
recordPlot() on non-interactive graphics device?
Hi. Q. Is there a way to record a plot using grDevices::recordPlot() without opening an interactive (=visible GUI window) graphics device (not even for a flash of a second)? Related: help("recordPlot", package="grDevices") says: "These functions record and replay the displaylist of the current graphics device." Is the intention that recordPlot() should be able to
2018 Apr 02
3
recordPlot/replayPlot not working with saveRDS/readRDS
The documentation for recordPlot says the following: > As of R 3.3.0, it is possible (again) to replay a plot from another R session using, for example, saveRDS and readRDS. However, I haven't been able to save and restore a plot displaylist and have it work within the same R session, using R 3.4.3 or 3.3.3. Here's an example: # Save displaylist for a simple plot
2008 Apr 07
1
How to include a vignette with my package?
I want to include a vignette with a package I wrote. I did follow the "Writting R extentions" document step by step, but went I run "Rcmd build", an error occurs. It goes like this: " * creating vignettes ... ERROR . . . . :7: Emergency stop L7L ==> Fatal error occurred, no output PDF file produced!texify: pdflatex failed for some reason <see log file>.
2018 Apr 03
1
[FORGED] recordPlot/replayPlot not working with saveRDS/readRDS
>>>>> Paul Murrell <paul at stat.auckland.ac.nz> >>>>> on Tue, 3 Apr 2018 09:41:56 +1200 writes: > Hi What you are doing "wrong" is loading a recordedplot > into the same session that it was created in. The > saveRDS()/readRDS() works if you save in one R session and > then read in a different R session. The
2011 Mar 25
1
Rd2pdf and Rd2dvi don't find texi2dvi
Hello everybody I'm am trying to build a pdf out of the Rd files that i wrote for a package, so that I can attach it to my thesis. if i Run Rd2pdf (or Rd2dvi) I get this error massage: Hmm ... looks like a package Converting Rd files to LaTeX . Creating pdf output from LaTeX ... Error in texi2dvi("Rd2.tex", pdf = (out_ext == "pdf"), quiet = FALSE, : Running
2015 Jan 13
2
R CMD build looking for texi2dvi in the wrong place (R-devel)
R CMD build fails with recent R-devel because it is looking for texi2dvi in /usr/local/bin, but on this system, MacTex has installed it in /usr/bin. $ R CMD build IRanges * checking for file 'IRanges/DESCRIPTION' ... OK * preparing 'IRanges': * checking DESCRIPTION meta-information ... OK * cleaning src * installing the package to build vignettes * creating vignettes ... ERROR
2007 May 21
1
dev.interactive() changes
On 5/5/07, Prof Brian Ripley <ripley at stats.ox.ac.uk> wrote: [...] > You meam as in > > o dev.interactive() regards devices with the displaylist enabled > as interactive, and packages can register the names of their > devices as interactive via deviceIsInteractive(). > > ? Quick follow up: the displaylist based detection is working well, but
2010 Aug 19
1
texi2dvi: option "clean" also deletes the generated pdf file
Dear expeRts, below are two examples of using texi2dvi. The problem becomes clear from the second example: on cleaning, texi2dvi also deletes the generated .pdf file. Is there a solution? Cheers, Marius ## Example 1: texi2dvi cleans fine, without deleting the generated .pdf require(tools) sink(file="myLaTeXFile1.tex") cat("\\documentclass{article}\n")
2016 May 13
1
LaTeX errors new with R 3.3.0
Hello: I could use help understanding an error reported by "R CMD build sos" that's new with R 3.3.0: Error in texi2dvi(file = file, pdf = TRUE, clean = clean, quiet = quiet, : Running 'texi2dvi' on 'sos.tex' failed. LaTeX errors: ! Undefined control sequence. l.1 \Sconcordance {concordance:sos.tex:sos.Rnw:% The control sequence at
2011 Dec 07
1
running texi2dvi without running bibtex
Dear all, I was hoping someone may know a way of running texi2dvi while ignoring bibtex errors, or any other work around (such as not running bibtex at all, if possible). The context is that I have an R program that does some calculations and writes a table into various folders, one per country for several countries. I have a latex file that takes the table as an input, and this latex file is
2011 Mar 21
1
texi2dvi / egrep issue shows (a.o.) up in R-alpha
L.S. I noticed weird tools::texi2dvi behaviour on R-alpha when specifying an absolute path to the .tex file. The same phenomenon also appears to occur on R-2.12.2, so maybe the issue is independent of R. I hope I did not overlook any important information. Best, Tobias > require(tools) Loading required package: tools > getwd() [1] "/home/tobias" >