Skip to content

Rd2dvi --pdf

4 messages · Matthew Fero, Brian Ripley, Simon Urbanek

#
I know this has been addressed before, but I'm not sure I understand the prior comments.  

Does the R Mac binary installer include the latex components necessary to run the 'R CMD Rd2dvi --pdf' command?  If so, where should it be located, because I'm getting the error, "/Library/Frameworks/R.framework/Resources/bin/Rd2dvi: line 233: /usr/texbin/pdflatex: No such file or directory".   If not, any suggestions on an easy way to install a lightweight, compatible latex distribution?

Thanks,

Matthew
#
On Mon, 4 Jan 2010, Matthew Fero wrote:

            
No.  See the FAQ, specifically section 2.1 and

http://cran.r-project.org/bin/macosx/RMacOSX-FAQ.html#TeX-suite-of-tools-for-documentation-_0028optional_0029

Note that these days the 'R Mac binary installer' contains much less 
than it used to, basically just R (not Tcl/Tk for example).
Unfortunately the CRAN binary of R (which I presume you are using) 
hardocodes the path to the TeX distribution (to values appropriate to 
MacTeX).  Depending on the architecture you are using, look in the 
file named like 
/Library/Frameworks/R.framework/Resources/etc/i386/Renviron and either 
edit the file or set the appropriate environment variables 
appropriately.

MacTeX is not 'lightweight' but you do need quite a lot (including 
fonts) to process Rd format.  So unless you install a comprehensive 
distribution or have one that updates itself on the fly, you are 
likely to spend a lot of time chasing down additional TeX packages.

  
    
2 days later
#
On Jan 5, 2010, at 0:56 , Matthew Fero wrote:

            
No, see FAQ 2.1.8
Not really - MacTex is the current standard and the binary you have  
(is that a nightly build?) requires that one (or something at those  
paths).

Cheers,
Simon
#
On Jan 5, 2010, at 1:31 , Prof Brian Ripley wrote:

            
Hmm.. this is a bug - since R 2.9.x they are supposed to be stripped  
of paths but apparently in the 2.10.1 Leopard installer they have not  
(I'll verify it at the next release to make sure they are). The only  
binaries that don't strip paths are the nightly builds as they don't  
post-process the values determined by configure (hence my assumption  
that it was a nightly build).

Thanks,
Simon