| ★ wanayoo — archive 1999 http://www.blackdown.org/java-linux/docs/support/faq-release/FAQ-java-linux-5.html | Nouvelle recherche | Portail wanayoo |
This section discusses aspects of running Blackdown Java on various Linux distributions in detail. Because Blackdown developers have tended to use RedHat and Debian exclusively, mailing list participants are encouraged to contribute as much as they can to this section.
Discussion related to installing Blackdown Java on various versions of Linux.
Last update:
$Id: install.sgml,v 1.2 1999/12/30 12:01:39 stevemw Exp $
This section addresses installs for JDK 1.1.x, but the same principles apply on other versions.
$ cd /usr/local $ tar zxvf /tmp/jdk1.1.6.tar.gz
$ export DISPLAY=:0
$ export PATH=/usr/local/jdk1.1.6/bin:$PATH
$ appletviewer \
/usr/local/jdk1.1.6/demo/awt-1.1/lightweight/OpenlookButtons/example.html
/bin/bash. Also note that if you already have a
CLASSPATH set, you'll probably want
to append .:/usr/local/jdk1.1.6/lib/classes.zip:
to that environment variable.
This ensures that you have the current working-directory in your class search
path, and makes things much easier for you as you test your code.
Of course you may want to add these environment commands to your shell's
startup script, such as $HOME/.bashrc.
Some people may wish to set JAVA_HOME themselves. That way,
you can change all commands following setting that to use it instead,
such as
$ export JAVA_HOME=/usr/local/jdk1.1.6 $ export PATH=$JAVA_HOME/bin:$PATH $ export CLASSPATH=.:$JAVA_HOME/lib/classes.zip
$ java -version
It's simply a lack of time. Volunteers are welcome to roll and offer their own.
Discussion related to specific Linux distributions.
Last update:
$Id: dist-specific.sgml,v 1.4 2000/01/05 18:13:34 srh Exp $
Although we currently have more information about running Blackdown Java on RedHat Linux for x86, many other platforms are running the bits. Please contribute what you know to the FAQ.
There are some problems that have been common to various platforms of Linux. From the README file:
The JDK now depends on having the X printing library, libXp installed with the rest of your X files. This is part of the most recent X11 distributions, so you'll need to upgrade (or, if you are daring, you can just extract the libXp.so* file from the upgrade package for your Linux distribution and install it by hand w/o upgrading everything else, although this is unlikely to work if your X libraries are substantially out of date).
The latest versions of the Blackdown JDK 1.1.x have their own built-in
loader (libdl.so) and libc.so, which will hopefully make them more
robust in most cases. Older versions of the JDK 1.1.5 (especially) are
much more sensitive. Take a look in
$JAVA_HOME/i386/green_threads/ to see these files.
(You may remove them if you feel they are a source of trouble to you.)
Karl Asha maintains a list of JDK-related library issues at:
http://www.blackdown.org/java-linux/docs/libraries.html.
In short, you need glibc-2.0.7 and glibc-devel-2.0.7
or higher on a glibc-based system such as RedHat 5.0 or Debian 2.0.
There are RPMs for these on RedHat Intel systems at
ftp://ftp.redhat.com/pub/redhat/current/updates/i386 or
ftp://ftp.redhat.com/pub/redhat/updates.
For more information about Blackdown Java on RedHat, see section Blackdown Java on RedHat Linux.
For a libc5 system, you need libc.so.5.44
or greater, along with a recent libdl.so. You can find these
at
ftp://tsx-11.mit.edu/pub/linux/packages/GCC.
For an in-depth discussion of this issue, see section What is glibc, and Why Does it Matter?.
This section will hopefully include information about running Blackdown Java on Debian GNU/Linux.
Last update:
$Id: debian.sgml,v 1.1.1.1 1999/12/27 06:13:31 stevemw Exp $
Yes, but you need to be running a version that has the libraries you need.
For now, please see http://www.debian.org/ for more information.
You're welcome to contribute what you know to the FAQ.
This section provides information about running Blackdown Java on RedHat Linux, the most popular distribution of Linux to date.
Last update:
$Id: redhat.sgml,v 1.2 2000/01/16 00:44:42 stevemw Exp $
It depends on which release and which version of a particular package, but yes, several of the developers run Blackdown Java on their RedHat systems.
Yes, RedHat 6.1 is currently the reference distribution for all Blackdown Java products, at least on x86. Other architectures will inevitably involve exceptions.
If you're on RedHat 5.2 and older,
download the glibc and ld updates described under
http://www.redhat.com/support/docs/errata.html.
In any case, it is advisable to stay as current as possible with
the RedHat errata.
According to Sorin Lingureanu <sorin@tuiasi.ro>, JDK RPMs are to be found in ftp://ftp.redhat.com/pub/contrib. Levente Farkas has more information about running the Blackdown JDK on RedHat here: http://anna.inf.u-szeged.hu/java/java-rpm.html.
In addition to the general problems described in section
Environment Variables,
make sure that you don't have conflicting JDK_HOME,
JAVA_HOME, and CLASSPATH environment variables set
from scripts sourced from /etc/profile.d/ at login. This can
especially be a problem when trying multiple versions of the JDK in
succession.
We assume you've read section Blackdown Java for Linux System Requirements and you know you need to upgrade your system.
You'll have to be running RedHat 6.x. The RedHat 6.1 i386 upgrade mechanism worked for the FAQ editor, who was running an updated version of RedHat 5.2.
/etc/X11/XF86Config file will continue to use the
filesystem. Make sure your font path includes the contents suggested
in the new /etc/X11/fs/config file. (See section
What's wrong with my font server?
for more information.Yes, as of 6.0. Please see http://www.redhat.com/support/manuals/RHL-6.0-Manual/install-guide/manual/doc012.html. For more information about TrueType on X11, see Will the Situation with TrueType Fonts Get Better?.
If you've chosen to "upgrade" your RedHat system to 6.x, the font server, and hence, TrueType fonts, won't work by default. You want to follow the instructions for working around this found in the Redhat Install Guide mentioned above. Here's the explanation of what to do from the section "Miscellaneous New Features."
Please Note: Those of you who upgrade will not have this feature until you edit your fontpaths. To do this you must edit the /etc/X11/XF86Config file. Scroll down until you see fontpaths listed. Replace them all with FontPath ``tcp/localhost:7100''. You must also verify that xfs, the X Font Server, is running. By issuing the command /sbin/chkconfig --add xfs you will insure that it starts at system boot time.
This section will hopefully include information about running Blackdown Java on Slackware Linux, one of the earliest distributions.
Last update:
$Id: slackware.sgml,v 1.1.1.1 1999/12/27 06:13:32 stevemw Exp $
For now, please see http://www.slackware.com/ for more information.
You're welcome to contribute what you know to the FAQ.
This section will hopefully include information about running Blackdown Java on SuSE Linux, a distribution with strong commercial support from Europe.
Last update:
$Id: suse.sgml,v 1.2 1999/12/30 12:01:41 stevemw Exp $
For now, please see http://www.suse.com/ for more information.
You're welcome to contribute what you know to the FAQ.
Information about ports to processors compatible with the x86 instruction set. For now, most x86 information is strewn around the FAQ, but as issues clearly in this category arise, we will put them here.
Last update:
$Id: x86.sgml,v 1.2 1999/12/31 10:50:59 stevemw Exp $
Intel (i386) processor port information.
Last update:
$Id: i386.sgml,v 1.3 1999/12/31 10:50:57 stevemw Exp $
Nothing for this section yet.
AMD processor port information.
Last modified:
$Id: amd.sgml,v 1.2 1999/12/31 10:50:56 stevemw Exp $
Nothing at this time.
Cyrix processor port information.
Last modified:
$Id: cyrix.sgml,v 1.2 1999/12/31 10:50:57 stevemw Exp $
Nothing at this time.
This section attempts to provide some additional information about non-Intel versions of the Blackdown JDK. At this time, Karl Asha has a more complete catalog of the different platforms available at http://www.blackdown.org/java-linux/ports.html. Help determining which JDK to download is available in section OK, which version of the JDK should i download?.
Last update:
$Id: non-i386.sgml,v 1.5 1999/12/30 12:01:40 stevemw Exp $
Alpha processor port information.
Last modified:
$Id: alpha.sgml,v 1.1 1999/12/29 07:53:30 stevemw Exp $
Yes, there have been (several 1.1 builds). Please see http://www.blackdown.org/java-linux/ports.html for more information. Uncle George, Uncle George <gatgul@voicenet.com>, also has Alpha ports for download at http://www.voicenet.com/~gatgul/Java.html.
Unfortunately, there isn't any current Alpha information at the time of this writing.
Arm processor port information.
Last modified:
$Id: arm.sgml,v 1.2 1999/12/30 12:01:39 stevemw Exp $
On December 28th, 1999, Scott Hutinger <srh@www.mprojects.wiu.edu> offered this informal status report:
Arm is in limbo currently.
He did say that with time and resources, Blackdown developers would like to pursue the following:
PowerPC processor port information.
Last update:
$Id: ppc.sgml,v 1.3 1999/12/31 10:50:58 stevemw Exp $
There has been for some time. Please see http://khendricks.ivey.uwo.ca/linuxppc/jdk/ for more information.
SPARC processor port information.
Last update:
$Id: sparc.sgml,v 1.6 2000/01/06 11:35:56 stevemw Exp $
Note: this section needs updating.
Our Java 1.1 information is rather dated, but see section What is the currently-supported version of Blackdown Java? for details about the latest supported build.
On June 16, 1998 Johan Vos <johan@sesuadra.org> provided this summary of the current SPARC effort, which is based at http://tinukai.sesuadra.org/~jdk/:
Starting from JDK 1.1.5, the Intel and SPARC ports are based on the same code. The SPARC-specific issues are separated from the other linux-specific issues. Improvements and bug-fixes in the general source code can be implemented without having to re-implement the SPARC-specific code.Johan follows up on 11/09/1998 with this comment:As a consequence, most problems and updates on the Intel-JDK also occur on the SPARC-JDK. I try to synchronize as much as possible with Steve [Byrne]'s ports -- although licensing problems caused the JDK 1.1.6v1 release for SPARC to be a few days after the Intel-release.
[The] JDK for sparclinux systems currently only exist for libc 5 systems. I am working on a port for glibc, but this will be a jdk 1.2 port. . . .
On December 28th, 1999, Eddie C Dost <ecd@skynet.be> wrote:
Sparc does want to support HotSpot, as there is no other JIT available for Sparc Linux at current. So far things look quite good. Porting to i86 should be ok, other archs are harder to get.
Sparc is doing quite well, there where some kernel problems with floating point on Ultra Sparc, and some kernel related signal problems, but these are fixed in the latest 2.2.x and 2.3.x kernels. With these Sparc happily passes the JCK so far at least on RedHat systems (other platforms should be tested soon, problems expected are minor).
On December 28th, 1999, Scott Hutinger <srh@www.mprojects.wiu.edu> pointed out that code for a SPARC JIT 1.1 does exist, although it's Solaris specific, pointing us at the LaTTe: A Fast and Efficient JVM JIT page at http://latte.snu.ac.kr.
He mentioned that Blackdown SPARC developers are interested in LaTTe as well as the HotSpot JIT from Sun. See section Is Sun's HotSpot JIT being ported? for the latest information on general HotSpot support in Blackdown Java.