In order to get a stock or upgrade RedHat 7.1 (i386) system to run Sun JDK 1.3.0_02 the following two changes must be made:

1. Create a symbolic link from /bin/cut to /usr/bin/cut

   ln -s /bin/cut /usr/bin/cut

2. Modify the $JAVA_HOME/bin/.java_wrapper script by adding the following two links after the copyright comments:

   LD_ASSUME_KERNEL=2.2.5
   export LD_ASSUME_KERNEL

Blackdown's 1.3.1 beta may work with Red Hat 7.1 without the above workarounds.
2001-Apr-25 10:22am gyles19@visi.com

Some platforms may need to install ksh (korn shell).
2001-Apr-26 6:04pm gyles19@visi.com

Conectiva 6.0, a Brazailian version of Red Hat, also needs the ncompress package.

2001-Jul-13 10:24am gyles19@visi.com

Sun Bug Parade item

  http://developer.java.sun.com/developer/bugParade/bugs/4441425.html

Known JVM versions that have this problem:

  jdk 1.3.1 RC1

  Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1-rc1-b21)
    Classic VM (build 1.3.1-rc1-b21, green threads, nojit)

Workaround: change the default stack size to any number but "unlimited". e.g.

    ulimit -s 8192

On some Red Hat 7.1 systems: While completing the license dialog, JBuilder dumps core the moment you click the 'Ok' button after entering your keys.

Launching 'jbuilder -verbose -license' eventually displays it as:

SIGSEGV 11 (*) segmentation violation
    si_signo [11]: SIGSEGV: (*) segmentation violation
    si_errno [0]: Success
    si_code [1]: SEGV_MAPERR [addr: 0x1]

        stackpointer=0x49f41b08

Full thread dump Classic VM (J2RE 1.3.0 IBM build cx130-20000815, native threads):
    "Screen Updater" (TID:0x403383e0, sys_thread_t:0x8637b40, state:S, native ID:0x2c0c) prio=4
        at java.lang.Object.wait(Native Method)
        at java.lang.Object.wait(Object.java:421)
        at sun.awt.ScreenUpdater.nextEntry(ScreenUpdater.java:79)

Since the IBM JVM bundled with JB4 is basically crap, simply replace it. I do not know why the bundled JVM dumps core on RH7.1, but I'm not going to waste any time debugging it since there are better JVMs available.

Go download Sun or Blackdown 1.3.1 (your choice.) Install it on your machine somewhere. (If you really wish to stay with IBM's JVM, go to their website and download the latest JVM they offer.)

Make a backup copy of jbuilder4/bin/jdk.config.

Now, edit jbuilder4/bin/jdk.config and replace all paths which refer to the IBM jvm with corresponding paths for the Sun/Blackdown JVM you just installed. Save the new file.

Check your machine's process list with 'ps' and make sure there aren't some defunct java processes left over from the IBM JVM's previous runs. Kill any leftovers you find.

Now you should be able to launch jbuilder -license and successfully complete the license dialog.
2001-Jun-07 8:12pm gyles19@visi.com

I am running 4.0 Enterprise on Redat 7.1 . I discovered the same problem. My current, though not complete fix, is to download the jdk1.3.1b24 from Sun. In jbuilder4/bin edit the jbuilder shell to point to the newly installed java. This will work. To get rid of the annoying font problems:

1> Download the URW fonts from http://www.gimp.org/urw-fonts.tar.gz

2> Untar the file in your X11R6 fonts directory. Usually this is /usr/X11R6/lib/X11/fonts (i.e. tar zxvf urw-fonts.tar.gz)

3> Modify the xfs config file. The file is /etc/X11/fs

4> Add the line /usr/X11R6/lib/X11/fonts/URW to the catalogue. Make sure each line has a comma at the end, except the last line of the catalogue command. Here is how mine looks:

  catalogue = /usr/X11R6/lib/X11/fonts/misc:unscaled,                            

  /usr/X11R6/lib/X11/fonts/75dpi:unscaled,
            /usr/X11R6/lib/X11/fonts/URW,
            /usr/X11R6/lib/X11/fonts/misc,
            /usr/X11R6/lib/X11/fonts/Type1,
            /usr/X11R6/lib/X11/fonts/Speedo,
            /usr/X11R6/lib/X11/fonts/75dpi,
            /usr/share/fonts/default/Type1

5> Restart xfs (i.e. /etc/rc.d/init.d/xfs restart)

BABAAM!!! You're up and running. My only problem thus far is the inability to use the debugging facilities ( which is no change from before ).

PS. If you want to find out what's happening when JBuilder "hangs", run it using the jbuilder/bin script and watch...
2001-Jun-18 7:28pm gyles19@visi.com

  mount -t iso9660 /dev/cdrom /mnt/cdrom

Conjecture: Mandrake's automounter is mounting the platter with an invalid partition type? Manually mounting with the correct type seems to work.
2001-Jun-25 10:59am gyles19@visi.com

   #! /bin/sh --login

fixes his runtime errors.

What this actually fixes, I have no idea.
2001-Jul-13 10:32am gyles19@visi.com

One user had something else. By editting jbuilder4/bin/jbuilder and appendending "-xv" to the very first line, and to line 65's ksh command, it became evident that /bin/sh on his machine didn't recognize the "function" keyword.

The solution we used here was to edit jbuilder4/bin/jbuilder once again, remove the "-xv" we added before, and change the first line to read "/bin/bash" instead of "/bin/sh".

An alternative would have been to symlink /bin/sh to /bin/bash, but since this could have repercussions elsewhere on the system I didn't recommend doing it.
2001-Jul-17 11:38am gyles19@visi.com

Installing JBuilder 5 on Mandrake 8

  http://community.borland.com/article/0,1410,27621,00.html

2002-Feb-05 12:39pm gyles19@visi.com