similar to: "Failed to locate the 'texi2pdf' output file"

Hi, Every day a few Bioconductor packages (different ones each day) fail to build, on Windows only, with an error like this: D:\biocbld\bbs-2.13-bioc\meat>D:\biocbld\bbs-2.13-bioc\R\bin\R.exe CMD build --keep-empty-dirs --no-resave-data OrganismDbi [...] Error in find_vignette_product(name, by = "texi2pdf", engine = engine) : Failed to locate the 'texi2pdf' output file (by

Hello, I'm seeing three different vignette-related errors with recent versions of R-3.0.0 alpha. First, with the package BitSeq (http://bioconductor.org/packages/2.12/bioc/html/BitSeq.html), I get the following when trying to build the package: Error: processing vignette ?BitSeq.Rnw' failed with diagnostics: Failed to locate the ?weave? output file (by engine ?utils::Sweave?) for

Hello, I have come across two separate packages that have a Makefile in inst/doc which use the R_HOME variable. In both cases, the path to R_HOME gets munged in such a way that commands that include R_HOME fail on Windows: For example, one Makefile, for the xmapcore package ( https://hedgehog.fhcrc.org/bioconductor/trunk/madman/Rpacks/xmapcore/username/password: readonly) has this:

Dear all, To create a *.pdf file from a *.Rnw file I do: olddir <- getwd(); setwd(outdir); tryCatch({Sweave("QAReport.Rnw"); tools::texi2pdf("QAReport.tex", clean=TRUE) }, finally = setwd(olddir) ); This works fine, however 'clean=TRUE' does only work when: outdir <-

Hi, Why isn't 'R CMD check --force-multiarch' installing the package for all the architectures that are going to be checked? For some packages, it only installs for the default arch ('i386'). Then testing the package for 'x64' fails. For example, Output of R CMD check --force-multiarch fabia_1.5.0.tar.gz: ----------------------------------------------------------- *

Hi, This is a follow up to: https://stat.ethz.ch/pipermail/r-devel/2010-July/057921.html The Bioconductor daily builds have been reporting a lot of strange things lately on Windows using R-2.12. This started 2 or 3 months ago and things are not getting better with recent R-2.12. Here is a sample from today's build results. We use Windows Server 2003 R2 for the 32-bit builds, Windows

Hi, The R-based version of R CMD build doesn't work for me on Windows: E:\biocbld\bbs-2.7-bioc>R\bin\R CMD build meat\Biobase * checking for file 'meat\Biobase/DESCRIPTION' ... OK * preparing 'Biobase': * checking DESCRIPTION meta-information ... OK * cleaning src * installing the package to re-build vignettes Warning in shell(sprintf("%s > %s

I am having a problem using two DLLs with the same name, but obviously located in different directories, in an R session. The troublesome package is the (Bioconductor) Rgraphviz package. It relies on (3rd party software) graphviz and imports functions from (Bioconductor) package graph. Unfortunately, the current stable release of graphviz for Windows

Hi, 'R CMD build' (with R 2.12.0 RC) fails to clean the src/ folder on Windows: D:\biocbld\bbs-2.7-bioc>ls meat/BUS/src BUS.cpp BUS.h D:\biocbld\bbs-2.7-bioc>R\bin\R CMD build meat\BUS * checking for file 'meat\BUS/DESCRIPTION' ... OK * preparing 'BUS': * checking DESCRIPTION meta-information ... OK * cleaning src * installing the package

I checked after this question popped up on Stackoverflow: https://stackoverflow.com/questions/44785961/compile-pdf-in-rstudio-works-but-knit2pdf-does-not-work-in-r-or-rstudio On Windows, texi2pdf looks for the texify.exe of Miktex, but looks in a very wrong place: > Sys.which("texify") texify

Hi, On Windows, with last R-devel tarball (r40647) from ftp://ftp.stat.math.ethz.ch/Software/R/R-devel_2007-02-04.tar.gz I get the following build error: E:\biocbld\bbs-2.0-bioc\R\src\gnuwin32> make ... ... ---------- Making package utils ------------ adding build stamp to DESCRIPTION installing NAMESPACE file and metadata installing R files Error in namespaceExport(ns, exports) :

Hi, Installing from binaries on Windows: > install.packages("multtest") Warning: dependency 'Biobase' is not available trying URL 'http://cran.fhcrc.org/bin/windows/contrib/2.12/multtest_2.6.0.zip' Content type 'application/zip' length 1645590 bytes (1.6 Mb) opened URL downloaded 1.6 Mb package 'multtest' successfully unpacked

Dear all, To make makefiles more portable, it would be useful to have something like R CMD texi2pdf available. It would just call the texi2pdf() function from the tools package. We have a makefile that uses texi2pdf for the vignette in robustbase. With this feature it would work on some more systems. Thanks in advance, Manuel

Hi, So in an interactive R session, R.home() returns the following: > R.home() [1] "D:/biocbld/bbs-3.2-bioc/R" However, if I call it from system2(), I get different results: > system2("R", "-q -e R.home()") > R.home() [1] "D:/biocbld/BBS-3~1.2-B/R" Similarly: > system2("R", "-q -e Sys.getenv('R_HOME')") >

Hello: Changes in R seem to have broken the sos vignette, and I don't know how to fix it. The build on R-forge, "https://r-forge.r-project.org/R/?group_id=235&log=build_src&pkg=sos&flavor=patched", ends as follows: Error in texi2dvi(file = file, pdf = TRUE, clean = clean, quiet = quiet, : Running 'texi2dvi' on 'sos.tex' failed. LaTeX

In the process of updating R to R 2.7 alpha or R 2.7 beta for the BioConductor 2.2 builds on Windows, I have hit a snag because the BioC build system has long path names (e.g. D:\biocbld\bbs-2.2-bioc\R) and these path names are not resolving properly by MiKTeX 2.7 during vignette construction. Take, for example, the attached vignette from Biobase, Bioconductor.Rnw. I have built R from source

Currently Makefiles for vignettes are only supported for .tex files. Could the tools package be modified to allow file extensions to be specified for a vignette engine? Having the pandoc pdf conversion in a Makefile rather than through R would be tidier in some cases. If I specify my vignette engine as ``` tools::vignetteEngine( 'myengine', pattern = '\\.[Rr](md|nw)$',

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

Ah, but I bet you do have that path...try > Sys.which("texify") texify "C:\\PROGRA~2\\MIKTEX~1.9\\miktex\\bin\\texify.exe" > normalizePath(Sys.which("texify")) [1] "C:\\Program Files (x86)\\MiKTeX 2.9\\miktex\\bin\\texify.exe" Cheers, Rich Calaway Microsoft R Product Team 24/1341 +1 (425) 4219919

Hi, On both Unix and Windows there is a mechanism to add variables to the environment when R is started. I noticed that, on Unix, this mechanism is not used when R is started normally at the command line but only when it's started using the 'R CMD' syntax. One problem with this is some lack of consistent cross-platform behaviour. For example: On Linux: $ echo $TEXINPUTS $