Dear all,
I have had the same problem as stated before, even with SUN's jdk
installed, and therefore enable to install any of 'iplots',
'rJava' or
'JGR' packages.
It seemed however that the R CMD javareconf couldn't catch the path of
my actual jdk.
The following worked for me by forcing the JAVA_HOME environment variable:
env JAVA_HOME=/my/path/to/my/very/own/sun/jdk1.6.0_17
/my/path/to/my/very/own/favourite/version/of/R-2.10.0/bin/R CMD javareconf
and then, everything runs smoothly for the install of the previous packages.
Hope this helps.
Cheers,
Leo.
--
/*******************************************/
/* Leonor Palmeira, PhD */
/* */
/* +32 4 3664269 */
/* mlpalmeira at ulg.ac.be */
/* */
/* Bat. B43BIS Immunologie et vaccinologie */
/* Boulevard de Colonster 20 */
/* 4000 Liege, Belgique */
/*******************************************/
#################
Previous Message :
It's almost always the same with failing builds:
On 31 January 2009 at 11:41, Stefan Th. Gries wrote:
[...]
Java home path : /usr/lib/jvm/java-6-openjdk/jre
[...]
This clearly states that you have the JRE -- ie the __run-time__
environment. The Builds-Depends [1] are for the package openjdk-6-jdk -- ie
the 'java development kit'. Install that, re-run 'sudo R CMD
javareconf' and
try again.
Dirk
[1] The second-best thing about having Debian packages, besides giving you
the binaries, is that they give you the essentially fail-safe recipe for
building them, including the list of ingredients encoded in the
Build-Depends: line of debian/control. You get that via the .diff.gz
--
Three out of two people have difficulties with fractions.
