Displaying 20 results from an estimated 5000 matches similar to: "R-exts.texi in SVN version 36380"
2003 May 17
1
problem building dvi and pdf documentation on Darwin 10.2.6
I just installed R-1.7.0 on Darwin 6.6 (a.k.a. MacOS 10.2.6).
'make' and 'make check' run without any problems. 'make info'
builds with no complaints, but 'make dvi' and 'make pdf' fail.
I get refman.dvi and refman.pdf OK (with some warnings from
pdftex that some names are referenced that do not exist), but
R-FAQ.{dvi,pdf} fails as shown below. Attempts
2008 Jun 23
1
r-base build: failure to convert R-FAQ to pdf
We have received an email in Ubuntu alerting us that something strange was
going on during the r-base 2.7.1 rc build (see [1]).
It seems that there is an error during the convertion of R-FAQ.texi to pdf.
The following excerpt, taken from [2], shows the problem:
/bin/sh: line 0: test: too many arguments
TEXINPUTS=".:$TEXINPUTS" /usr/bin/texi2dvi --texinfo="@set
UseExternalXrefs
2007 Aug 31
1
compiling R-devel
Hello.
I am in a habit of compiling daily snapshots of R-devel and R-patched on my
Windows XP workstation. I have cygwin environment with up-to-date RTools
and MiKTeX. I run cygwin and MiKTeX upadaters pretty often (every couple
of days) so both of them are reasonably current.
Recently I noticed a small annoyance when compiling R-dvel. It started
happening right after I updated to the new
2015 Oct 09
2
Building manuals are failing now that MikTex 2.9 has removed texi2dvi.exe
According to the MikTex bug reports [1], MikTex 2.9 has removed
texi2dvi.exe last week (on 2015-09-29) as "it was not compatible
(anymore) with the original shell script texi2dvi (GNU Texinfo)." I
found this out the hard way as I just (unknowingly) updated MikTex
this evening, and then, while building R-devel_2015-10-08 on Windows7
64bit using the Rtools 3.3 toolchain (4.9.3 branch), had
2015 Sep 09
2
Build R form source - manuals
I built R form source succesfully on my Fedora 22 box. No errors.
I can read there is an issue with some manuals at build time when
running makeinfo, especially these two:
doc/manual/R-exts.texi
cp doc/manual/R-intro.texi
Some distro have hacks about makeinfo 5 in their build script.
I wonder if some manuals are broken but couldn't see it when running make.
May someone tells me more about
2004 Oct 29
3
R-exts.texi: suggestion for small change to Vignette section (PR#7323)
I recently wrote a vignette, with the following at the top of the .Rnw
file:
%%\VignetteIndexEntry{How to use look up tables for h() functions}
%%\VignetteDepends{sjedmin, spatstat}
Using vExplorer() on this function, I got an error from this part of
getVigInfo():
lines <- grep("^%[[:space:]]*\\\\Vignette", file)
if (length(lines) == 0)
stop("File ", vig,
2015 Oct 22
1
Missing parenthesis in R-exts.texi
Line 1204 (right now) of svn/r-devel/doc/manual/R-exts.texi has
dest <- file.path(R_PACKAGE_DIR, paste0('bin', R_ARCH)
which lacks a closing ) -- two open, only one close right now.
Dirk
[1] I would have reported a bug, but I am aware of a recent and
not-so-friendly response when bugzilla was used to report a typo.
--
http://dirk.eddelbuettel.com | @eddelbuettel | edd at
2000 Apr 24
1
make problems
I'm having trouble making the manuals as per the INSTALL instructions.
Anyone have any hints as to what's wrong?
<123>-> make dvi
DVI/LaTeX documentation: reference index ...
*** Error code 255
make: Fatal error: Command failed for target `refman.dvi'
2005 Nov 12
0
Suggested changes to R-lang.texi and R-exts.texi
Dear all,
I would like to suggest the following changes to the R documentation:
1) R-exts.texi:
Having had my first experience with uploading a package to
ftp://cran.R-project.org/incoming/, I think it would be nice if the
documentation pointed out that one should use ftp and not sftp (at
least on my machine sftp failed to make a connection) and that one
should log in as user
2015 Sep 07
2
Build rpm package for R-MKL
I want to create a clean .rpm package for R built with MKL and ICC. I
follow Fedora instrcutions[0] to create the package. As a base, I use
the R-3.2.2.src.rpm.
I am left with this error:
------------------------------------------
installing R info pages ...
updating '/usr/share/info/dir' ...
make[1]: Leaving directory '/home/poisonivy/rpmbuild/BUILD/R-3.2.2/doc/manual'
+ mv
2017 Jul 03
0
Patch for R-exts.texi
Attached is a patch for R-exts.texi against r72880.
Here are some of the changes I made:
- Fix a broken link:
https://developer.apple.com/library/mac/#documentation/DeveloperTools/Conceptual/InstrumentsUserGuide/Introduction/Introduction.html
->
https://developer.apple.com/library/content/documentation/DeveloperTools/Conceptual/InstrumentsUserGuide/index.html
- Changed a few http
2000 May 18
1
attach (S-style)?
Hi everyone,
Being new to the crowd of R users I am wondering what the equivalent of
attach("/home/bla/hoffmann/R/.RData",2)
(S style) is in R.
What I want is a split of .RData repositories. One in a central place where I keep functions and interesting stuff important for all work I am doing, an several others which contain stuff of an dividual project only. When I start in a
2005 May 14
2
[LLVMdev] Cygwin llvm-gcc build error
Now I believe that I am getting the same error as I was getting last time I
tried to build llvm-gcc.
It may possibly be my Cygwin instillation but am not sure.
makeinfo --split-size=5000000 -I ../../../src/llvm-gcc/gcc/doc -I
../../../src/
llvm-gcc/gcc/doc/include \
-o ../../../src/llvm-gcc/gcc/doc/cpp.info
../../../src/llvm-gcc/gcc/doc/cpp.texi
' in
2004 Oct 29
0
R-exts.texi: suggestion for small change to Vignette section (PR#7325)
>>>>> On Fri, 29 Oct 2004 12:47:46 +0200 (CEST),
>>>>> S J Eglen (SJE) wrote:
> I recently wrote a vignette, with the following at the top of the .Rnw
> file:
> %%\VignetteIndexEntry{How to use look up tables for h() functions}
> %%\VignetteDepends{sjedmin, spatstat}
> Using vExplorer() on this function, I got an error from this part of
2005 May 17
2
[LLVMdev] Cygwin llvm-gcc build error
>Hi Aaron,
>have you got any help on this?
Henrik,
No. This is where I was stuck some months ago.
I do not know makeinfo so was not able to proceed any thurther than
verifying the makeinfo statement did the same thing when done on the command
line.
Basically I am stuck. I do not know whether it was my Cygwin configuration
or something I have done or not done or whether it is a valid
2000 Mar 20
1
ESS Compilation error
Im running R 0.99 on SuSE 6.3 with Linux 2.2.14 and Xemacs 21.1.
When I try to compile ESS the processes stops with an error message:
Making info file `ess.info' from `ess.texi'.
./newfeat.texi:3: itemize requires an argument: the formatter for @item.
./newfeat.texi:9: itemize requires an argument: the formatter for @item.
makeinfo: Removing output file
2005 May 17
0
[LLVMdev] Cygwin llvm-gcc build error
Hi Aaron,
have you got any help on this?
Henrik
>From: "Aaron Gray" Date: Sat, 14 May 2005 18:26:01 +0100
>
>Now I believe that I am getting the same error as I was getting last time I
>tried to build llvm-gcc.
>It may possibly be my Cygwin instillation but am not sure.
>
>
>makeinfo --split-size=5000000 -I ../../../src/llvm-gcc/gcc/doc -I
>../../../src/
2001 Oct 24
1
incompletely built html documentation (PR#1142)
Full_Name: Denis Sunko
Version: 1.3.1
OS: HP-UX 11.0
Submission from: (NULL) (161.53.2.114)
After building and installing R 1.3.1, i find some of the html files missing:
> ls -l /opt/lib/R/doc/manual/
total 0
-rw-r--r-- 1 root sys 0 Oct 17 22:16 R-FAQ.html
-rw-r--r-- 1 root sys 0 Oct 17 22:16 R-admin.html
-rw-r--r-- 1 root sys 0
2016 Apr 19
1
R-exts update for new *check* argument in R 3.3.0
Hello dear dev team,
In the recent devel R-exts manual I cannot find any information about new
option `--ignore-vignettes` to `R CMD check`. I would expect it to be
mentioned somewhere in "1.4.2 Non-Sweave vignettes".
Checked on https://cran.r-project.org/doc/manuals/r-devel/R-exts.html and
https://github.com/wch/r-source/blob/trunk/doc/manual/R-exts.texi
Regards,
Jan Gorecki
2011 Apr 28
1
request for R-exts addition
would it be possible / make sense to copy some of the information in
?news into the R-exts manual, where package writers are most likely (?)
to look for it? The information therein seems more appropriate for the
extensions manual ...
cheers
Ben Bolker