Displaying 20 results from an estimated 90000 matches similar to: "R CMD texi2pdf"
2013 Oct 08
1
"Failed to locate the 'texi2pdf' output file"
Just thought I would mention that the issue below (and in https://stat.ethz.ch/pipermail/r-devel/2013-April/066318.html) is still not resolved.
It hasn't been a big problem, but it potentially could be, if a critical package were to have this error on release day, then all its dependencies would fail to build, which would probably require us to postpone our release.
See the complete thread
2013 Apr 12
2
"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
2016 Jan 12
3
Small inaccuracy in the Writing R Extensions manual
G'day all,
In Chapter 1.4 (Writing package vignettes) the Writing R Extensions
manual states:
By default @code{R CMD build} will run @code{Sweave} on all
Sweave vignette source files in @file{vignettes}. If
@file{Makefile} is found in the vignette source directory, then
@code{R CMD build} will try to run @command{make} after the
@code{Sweave} runs, otherwise @code{texi2pdf} is run on
2016 Jan 12
1
Small inaccuracy in the Writing R Extensions manual
G'day Duncan,
On Tue, 12 Jan 2016 07:32:05 -0500
Duncan Murdoch <murdoch.duncan at gmail.com> wrote:
> On 11/01/2016 11:59 PM, Berwin A Turlach wrote:
> > G'day all,
> >
> > In Chapter 1.4 (Writing package vignettes) the Writing R Extensions
> > manual states:
> >
> > By default @code{R CMD build} will run @code{Sweave} on all
> >
2013 Aug 30
1
Problem with texi2pdf(..,clean=TRUE)
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 <-
2013 Mar 13
1
Failed to locate 'weave' output file / vignette product does not have a known filename extension
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
2016 Jun 18
0
Error in texi2dvi
On 17/06/2016 10:21 PM, Spencer Graves wrote:
> 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 =
2014 Nov 03
0
Pkg creation: Sweave: multiple files vignette: Error in R CMD check
Hello R-developers!
I am creating a package (using devtools and RStudio) and I would like to split
my vignette into multiple Rnw-files.
As an example I tried the code from:
https://support.rstudio.com/hc/en-us/articles/200486298
(--> Working with multiple Rnw files)
The Rnw-files work fine with "Complie pdf" in RStudio as well as with
Sweave("Master.Rnw").
But, if I try
2016 Jun 18
5
Error in texi2dvi
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
2007 Jun 08
1
Need Help with robustbase package: fitnorm2 and plotnorm2
This is my first post requesting help to this mailing list. I am new
to R. My apologies for any breach in posting etiquette. I am new to
this language and just learning my way around. I am attempting to run
some sample code and and am confused by the error message:
Loading required package: rrcov
Error in fitNorm2(fdat[, "FSC-H"], fdat[, "SSC-H"], scalefac = ScaleFactor) :
2015 Jan 13
0
R CMD build looking for texi2dvi in the wrong place (R-devel)
Dan,
On Jan 12, 2015, at 7:50 PM, Dan Tenenbaum <dtenenba at fredhutch.org> wrote:
> 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.
>
No, you're looking at the wrong package - texi2dvi comes from texinfo which is now mandatory in version 5.2+ located in /usr/local since OS X
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
2015 Mar 25
2
vignette checking woes
I'm having trouble with R CMD check of my quantreg package. All is well
until I get to:
checking running R code from vignettes ...
?rq.Rnw? ... failed
ERROR
Errors in running code in vignettes:
when running code in ?rq.Rnw?
when I see a snippet from the vignette code and then:
Loading required namespace: MatrixModels
When sourcing ?rq.R?:
Error: could not find function
2017 Jun 27
0
texi2pdf doesn't find the correct MikTex installation due to erroneous Sys.which()
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
2015 Mar 26
0
vignette checking woes
> On Mar 26, 2015, at 8:50 AM, Martyn Plummer <plummerM at iarc.fr> wrote:
>
> On Wed, 2015-03-25 at 15:12 -0500, Roger Koenker wrote:
>> Thierry,
>>
>> I have this:
>>
>> if (require(MatrixModels) && require(Matrix)) {
>> X <- model.Matrix(Terms, m, contrasts, sparse = TRUE)
>
> You have this in the current release, which
2015 Jan 13
2
R CMD build looking for texi2dvi in the wrong place (R-devel)
----- Original Message -----
> From: "Simon Urbanek" <simon.urbanek at r-project.org>
> To: "Dan Tenenbaum" <dtenenba at fredhutch.org>
> Cc: "R-devel" <r-devel at r-project.org>
> Sent: Monday, January 12, 2015 5:50:35 PM
> Subject: Re: [Rd] R CMD build looking for texi2dvi in the wrong place (R-devel)
>
> Dan,
>
> On
2015 Jan 27
0
R CMD check message: "The following files should probably not be installed"
Sorry. This, and the description in the ?Writing R Extensions? manual,
leaves me completely mystified. Is it that I have to remove the PDFs
that are created when I run ?R CMD build?, and somehow ensure that
they are rebuilt when the package is installed? Do I need a Makefile?
John Maindonald email: john.maindonald at anu.edu.au<mailto:john.maindonald at anu.edu.au>
phone :
2017 Jun 27
2
texi2pdf doesn't find the correct MikTex installation due to erroneous Sys.which()
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
2011 Jun 27
1
R CMD check --force-multiarch does not install all the archs for testing
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:
-----------------------------------------------------------
*
2011 Oct 31
0
R 2.14.0 is released
The byte pixies have rolled up R-2.14.0.tar.gz (codename "Great Pumpkin") at 9:00 this morning. This is a development release with several new features; see the list below for details.
You can get it from
http://cran.r-project.org/src/base/R-2/R-2.14.0.tar.gz
or wait for it to be mirrored at a CRAN site nearer to you.
Binaries for various platforms will appear in due course.
For