[Rd] Locating MiKTeX

2008-11-09 Thread Gabor Grothendieck
I came across this program to locate MiKTeX file:

http://docs.miktex.org/2.7/sdk/findfile_8cpp-example.html

If the exe of this were included with R then it seems it might
provide a reliable way to locate MiKTeX which we don't currently have
since AFAIK there is no adequate registry key for MiKTeX.
Since its a tiny program it would not substantially affect the
R download.

(There is also a perl version of the same program there although
it relies on certain perl packages which would also have to be
present complicating things.)

__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel


Re: [Rd] Locating MiKTeX

2008-11-09 Thread Spencer Graves
Hi, Gabor, et al.: 

 Could you also please ensure 'plflatex wrapper.tex' work with 
whatever MikTeX installation you include, for 'wrapper.tex' mentioned in 
the "Submissions" instructions for R News? 

 This bombed for me when I tried it recently, because I was missing 
multiple LaTeX packages:  When I found one, it asked for another that I 
couldn't easily find.  So I did a maximal install of the latest version 
of MiKTeX.  That involved downloading more that a gigabyte of stuff, 
then cleaning space on my hard drive so I could actually install it.  
The whole process took several days, in between my other work.  It would 
help if it were all part of the standard install. 


 Thanks,
 Spencer 


Gabor Grothendieck wrote:

I came across this program to locate MiKTeX file:

http://docs.miktex.org/2.7/sdk/findfile_8cpp-example.html

If the exe of this were included with R then it seems it might
provide a reliable way to locate MiKTeX which we don't currently have
since AFAIK there is no adequate registry key for MiKTeX.
Since its a tiny program it would not substantially affect the
R download.

(There is also a perl version of the same program there although
it relies on certain perl packages which would also have to be
present complicating things.)

__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel



__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel


Re: [Rd] Locating MiKTeX

2008-11-09 Thread Gabor Grothendieck
MiKTeX automatically downloads additional required packages
that your *.tex files use.  Something is wrong with your installation
if it did not try to do that automatically for you.

Although the following should not be necessary, if you do
want to download and install additional MiKTeX packages
yourself without a massive download just invoke the
MiKTeX package manager by entering at the Windows
command line:

mpm

or, if you don't have MiKTeX on your path you can run

rtools.bat
mpm

where rtools.bat, which is from http://batchfiles.googlecode.com ,
will temporarily add MiKTeX to your path so that you can run mpm
and other MiKTeX tools.


On Sun, Nov 9, 2008 at 11:41 AM, Spencer Graves <[EMAIL PROTECTED]> wrote:
> Hi, Gabor, et al.:
> Could you also please ensure 'plflatex wrapper.tex' work with whatever
> MikTeX installation you include, for 'wrapper.tex' mentioned in the
> "Submissions" instructions for R News?
> This bombed for me when I tried it recently, because I was missing
> multiple LaTeX packages:  When I found one, it asked for another that I
> couldn't easily find.  So I did a maximal install of the latest version of
> MiKTeX.  That involved downloading more that a gigabyte of stuff, then
> cleaning space on my hard drive so I could actually install it.  The whole
> process took several days, in between my other work.  It would help if it
> were all part of the standard install.
> Thanks,
> Spencer
> Gabor Grothendieck wrote:
>>
>> I came across this program to locate MiKTeX file:
>>
>> http://docs.miktex.org/2.7/sdk/findfile_8cpp-example.html
>>
>> If the exe of this were included with R then it seems it might
>> provide a reliable way to locate MiKTeX which we don't currently have
>> since AFAIK there is no adequate registry key for MiKTeX.
>> Since its a tiny program it would not substantially affect the
>> R download.
>>
>> (There is also a perl version of the same program there although
>> it relies on certain perl packages which would also have to be
>> present complicating things.)
>>
>> __
>> R-devel@r-project.org mailing list
>> https://stat.ethz.ch/mailman/listinfo/r-devel
>>
>

__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel


Re: [Rd] problems installing rJava with R-2.8.0

2008-11-09 Thread Joris @ VU
Hello Christian,

I had the same problem with running install.packages("rJava"), exactly
the same error as you. Turned out the solution was changing a 7 into a
6 somewhere ... please allow me to explain :)

Of course the first thing I did, and I suppose you did is follow the
advice of Simon Urbanek, run "R CMD javareconf" as root, or if that
doesn't work "R CMD javareconf -ed". This is the output of that:
===
linux:/usr/lib/jvm # R CMD javareconf -ed
*** JAVA_HOME is not a valid path, ignoring
Java interpreter : /usr/bin/java
Java version : 1.6.0_06
Java home path   : /usr/lib/jvm/java-1.6.0-sun-1.6.0.u6/jre
Java compiler: /usr/bin/javac
Java headers gen.: /usr/bin/javah
Java archive tool: /usr/bin/jar
Java library path:
$(JAVA_HOME)/lib/i386/server:$(JAVA_HOME)/lib/i386:$(JAVA_HOME)/../lib/i386::/usr/java/packages/lib/i386:/lib:/usr/lib
JNI linker flags : -L$(JAVA_HOME)/lib/i386/server
-L$(JAVA_HOME)/lib/i386 -L$(JAVA_HOME)/../lib/i386 -L
-L/usr/java/packages/lib/i386 -L/lib -L/usr/lib -ljvm
JNI cpp flags: -I$(JAVA_HOME)/../include -I$(JAVA_HOME)/../include/linux

Updating Java configuration in /usr/lib/R
Done.
===
Done. That means "everything is ok" ... right? No. Look at the first
line ... "*** JAVA_HOME is not a valid path, ignoring".
I figured that's odd, I had no trouble running "java" or "javac" on my
computer ... so I ran "$JAVA_HOME"
===
linux:/usr/lib/jvm # $JAVA_HOME
bash: /usr/lib/jvm/java-1.6.0-sun-1.6.0.u7: No such file or directory
===
Strange, that seemed to be the correct path ... but upon closer
inspection I realized I didn't have update 7 but update 6, so the
correct path would be "/usr/lib/jvm/java-1.6.0-sun-1.6.0.u6". I used
to have 7 (downloaded from the Sun website) but removed it and
installed the version from the openSUSE repositories instead, I guess
somehow JAVA_HOME was not updated, even after running
"update-alternatives --config javac". Exporing JAVA_HOME manually did
the trick for me, so running as root:
export JAVA_HOME=/usr/lib/jvm/java-1.6.0-sun-1.6.0.u6
Then running "R CMD javareconf " worked without warning this time. And
then running R and "install.package("rJava")" worked without trouble.

Still I'm curious where that magical config.log file is located,
perhaps that would have pointed out my mistake right away.

Best,

Joris

On Wed, Oct 29, 2008 at 17:10, Simon Urbanek
<[EMAIL PROTECTED]> wrote:
>
> On Oct 29, 2008, at 11:51 , Christian Kohler wrote:
>
>> Dear R-developers,
>>
>> I am having trouble installing rJava on R 2.8.0 / debian etch.
>>
>> What goes wrong?
>>
>
> Please send me the config.log. Also make sure you have configured R with
> Java support (sudo R CMD javareconf).
>
> Cheers,
> S
>
>
>>
>>> install.packages("rJava")
>>
>> Warning in install.packages("rJava") :
>>  argument 'lib' is missing: using
>> '/nfs/compdiag/package/R/lib/bioconductor/release_2.3/x86_64'
>> --- Please select a CRAN mirror for use in this session ---
>> Loading Tcl/Tk interface ... done
>> trying URL 'http://cran.rakanu.com/src/contrib/rJava_0.6-0.tar.gz'
>> Content type 'application/x-gzip' length 234704 bytes (229 Kb)
>> opened URL
>> ==
>> downloaded 229 Kb
>>
>> * Installing *source* package 'rJava' ...
>> checking for gcc... gcc -std=gnu99
>> checking for C compiler default output file name... a.out
>> checking whether the C compiler works... yes
>> checking whether we are cross compiling... no
>> checking for suffix of executables...
>> checking for suffix of object files... o
>> checking whether we are using the GNU C compiler... yes
>> checking whether gcc -std=gnu99 accepts -g... yes
>> checking for gcc -std=gnu99 option to accept ISO C89... none needed
>> checking how to run the C preprocessor... gcc -std=gnu99 -E
>> checking for grep that handles long lines and -e... /bin/grep
>> checking for egrep... /bin/grep -E
>> checking for ANSI C header files... yes
>> checking for sys/wait.h that is POSIX.1 compatible... yes
>> checking for sys/types.h... yes
>> checking for sys/stat.h... yes
>> checking for stdlib.h... yes
>> checking for string.h... yes
>> checking for memory.h... yes
>> checking for strings.h... yes
>> checking for inttypes.h... yes
>> checking for stdint.h... yes
>> checking for unistd.h... yes
>> checking for string.h... (cached) yes
>> checking sys/time.h usability... yes
>> checking sys/time.h presence... yes
>> checking for sys/time.h... yes
>> checking for unistd.h... (cached) yes
>> checking for an ANSI C-conforming const... yes
>> checking whether time.h and sys/time.h may both be included... yes
>> configure: checking whether gcc -std=gnu99 supports static inline...
>> yes
>> checking Java support in R... present:
>> interpreter : '/usr/lib/jvm/java-1.5.0-sun/jre/bin/java'
>> archiver: '/usr/lib/jvm/java-1.5.0-sun/bin/jar'
>> compiler: '/usr/lib/jvm/java-1.5.0-sun/bin/javac'
>> header prep.: '/usr/lib/jvm/java-1.5.0-sun/bin/javah'
>>