#!/usr/bin/perl

($Revision,$RevisionDate) =
  ('$Id: JBCheck,v 1.13 2001/10/19 15:42:28 joi Exp $' =~ /v ([\d+\.]+) (\d+\/\d+\/\d+) /);
$DEBUG=0;
@notInterestingList = ("Red Hat 6.2");  # mostly for my reference. Not used in code yet.
$Interesting = 1;  # controls the appearance of the usageLog string at the end of the log.
$sawJB4IBMWarning = 0;
$sawGETNEWJVM=0;
$warningCount=0;
@summary = ();
$WARNING = 
"\n------------------------------------------------------------------------------\n" .
"WARNING";

$dashLine = <<EOF; 

------------------------------------------------------------------------------

EOF
$usageLog = <<EOF;

To send me a debuggable log, enter the following, one line per shell or 
perl prompt:

  script /tmp/JBCheck.log
  perl -d ./JBCheck -d
  t
  c
  q
  exit
  (You may want to edit the log to remove any passwords that might be visible
   in the fstab debug output.)
  mail -s "JBcheck.log" gyles19\@visi.com </tmp/JBCheck.log && echo "Mail sent."

EOF

$usageString =
  &header() .
  <<EOF . $usageLog . &credits();
Usage: ./JBCheck [-4]
or     perl JBCheck [-4]

This script inspects your Linux machine and looks for issues which can cause
the JBuilder4/5 installer to fail, or which are known to cause problems for
JBuilder's bundled JVM.

Parameters:
   -4   Inspect for JBuilder 4 compatibility.  Defaults to JBuilder 5.
   -d   Prints extra debugging information
   -h   Prints this usage information.

This script has been tested on Red Hat 6.2.  

EOF


require "getopt.pl";
&Getopt();
if ($opt_h) {
  print $usageString;
  exit 1;
}
if ($opt_d) {
  $DEBUG=1;
  print "Debug output enabled.\n";
}
print &header();

$needTMPSpace{"JB4"} = 240;  # Enterprise Installer space needs on /tmp
$needTMPSpace{"JB5"} = 250;  # Enterprise Installer space needs on /tmp
$isRedHat = 0;
$isMandrake = 0;
$MandrakeRelease = 0.0;
$isSMPKernel = 0;
$RedHatRelease = 0.0;

$JBVersion = "";

if ($opt_4) {
  $JBVersion = "JB4";
} else {
  $JBVersion = "JB5";
}
print "Checking for $JBVersion requirements.\n";
# print "JB4: ", &isJB4(), " JB5: ", &isJB5(),"\n";

if ( &isJB4() ) {
  print &JB4IBMWarning();
  $warningCount++;
  push(@summary,"JB4 IBM JVM has broken debugger. Replace it.");
} elsif ( &isJB5() ) {
  print &JB5SoundWarning();
  push(@summary,"Tools | Audio, disable audio support");
  $warningCount++;
} else {
}

&rpmqa();
&checkKernel24();
&checkKernelSMP();
&checkDistribution();
&checkForCommand("/usr/bin/uncompress","ncompress-4.2.4-15");
&checkForCommand("/usr/bin/cut", "textutils-2.0e-6");
&checkForCommand("/bin/dd", "fileutils-4.0-21");
&checkForCommand("/bin/df", "fileutils-4.0-21");
&checkForCommand("/bin/ls", "fileutils-4.0-21");
&checkForCommand("/usr/bin/dirname","sh-utils-2.0-5");
&checkForCommand("/bin/basename","sh-utils-2.0-5");
&checkForLocale();
&checkDiskSpace();
&checkFonts() if &checkDisplay();
&checkBash();
&checkKsh();
&checkNoExec();
&checkKDE();
&checkForKawa();
&checkForJava();
&checkForUsrBinJava();

#ZZZ
print <<EOF;
$dashLine
Checks completed.  Warnings printed: $warningCount
EOF
$i=1;
foreach $whine (@summary) {
  print $i++, ":\t",$whine,"\n";
}
print $dashLine,"\n";

print &credits();
if ($Interesting) {
  print "You have a distribution I don't have.  Would you consider
sending me a debuggable log so I can see how this script (mis)behaves
on your platform?\n";
  print $usageLog;
}
exit 0;

#################################################################

sub checkForCommand {
  my $cmd = shift;
  my $package = shift;

  print "Checking for ", $cmd, "...";
  if (-x "$cmd" ) {
    print "OK.\n";
  } else {
    print "Oops!\n";
    my @foo = split(/\//, $cmd);
    my $cmd2 = pop(@foo);
    my $unc = `which $cmd2`;
    if (-x "$unc") {
      print <<EOF;
$WARNING: Your $cmd2 binary is not in the correct spot.  Suggest a symlink:
  ln -s $unc $cmd
$dashLine
EOF
      push(@summary,"Symlink $cmd2");
    } else {
      $warningCount++;
      print <<EOF;
$WARNING: Your system has no '$cmd2' command.  This is provided in
package $package (on Red Hat 6.2.)  This needs to be installed
before JB's installer will function.

If you find the command *is* present on your system, figure out
why this script couldn't find it on your PATH.  
$dashLine
EOF
      push(@summary,"Install $cmd2 (in package $package)");
    }
  }
}


#################################################################

sub LD_ASSUME_KERNEL {
    $warningCount++;
    push(@summary,"Export LD_ASSUME_KERNEL=2.2.5, or install new jVM");
    print <<EOF;
$WARNING:  The JVM Bundled with $JBVersion may not like your glibc packages without
a ld workaround.  If JB dumps core when launched, or hangs, edit the
script file $JBVersion/jdk1.3/bin/java and insert the following lines near
the top:

  export LD_ASSUME_KERNEL=2.2.5

This creates a shell Environment variable which will trigger a workaround
in the system loader that bypasses some problems in the threading system.
(I think...)

This environment variable is a control for the linux 'ld' loader,
the critter responsible for loading commands into ram and adding linkages
to system libraries.  LD_ASSUME_KERNEL tells 'ld' to use older behavior
for this process, behaviors the JVM seems to depend on.

The newest Sun 1.3.1 and the newest 1.3.0 and 1.3.1 kernels from blackdown
do not need this.  (But I'm not certain exactly which build of Blackdown
1.3.0 fixed this issue.  Earlier betas of Blackdown 1.3.0 needed this
workaround, later ones did not.)  IBM 1.3.0 needs this, too.
$dashLine
EOF
}


#################################################################

sub GETNEWJVM {
    $sawGETNEWJVM=1;
    return <<EOF;
$WARNING:  You will need to download one of the following JVMs and
install it before proceeding.

Sun JDK 1.3.1: http://java.sun.com/j2se/1.3/download-linux.html
Sun JDK 1.3.0: http://java.sun.com/j2se/1.3.0/
Blackdown 1.3.0 FCS: ftp://metalab.unc.edu/pub/linux/devel/lang/java/blackdown.org/JDK-1.3.0/i386/FCS/j2sdk-1.3.0-FCS-linux-i386.tar.bz2
Blackdown 1.3.1 FCS: ftp://metalab.unc.edu/pub/linux/devel/lang/java/blackdown.org/JDK-1.3.1/i386/FCS/j2sdk-1.3.1-FCS-linux-i386.tar.bz2
IBM 1.3.0: http://www6.software.ibm.com/dl/dklx130/dklx130-p

To install Blackdown's bz2 files, install rpm package bzip2-0.9.5d-2.rpm (or
whatever bzip2 package your platform offers.
$dashLine
EOF
}


#################################################################

sub checkDiskSpace {
  my @data = `df -m /tmp`;
#  @data = <<EOf;
#Filesystem           1M-blocks      Used Available Use% Mounted on
#/dev/hda11                  99        99         0 100% /tmp
#EOf
  print "Checking free space on /tmp...";
  print "\nDEBUG: " , @data if $DEBUG;
  foreach (@data) {
    ($dev,$blocks,$used,$avail,$percent,$mounted) = (/(\S)+\s+(\d+)\s+(\d+)\s+(\d+)\s+(\d+)\%\s+(\S+)/);
    next unless ($dev && $blocks);
    if ($avail < $needTMPSpace{$JBVersion} ) {
       $warningCount++;
       print "Oops!\n";
       push(@summary,"export IATEMPDIR=/path/to/bigger/tmp/dir or free space on /tmp");
       print <<EOF;
$WARNING: $JBVersion installer needs $needTMPSpace{$JBVersion} free space on /tmp.
Your /tmp seems to contain only $avail meg free.  This needs to be addressed
before proceeding.

Alternatively, you can create a temporary directory on some other partition,
and use an InstallAnywhere environment variable to point to it:

  export IATEMPDIR=/path/to/new/tmp/dir
$dashLine
EOF
    } else {
       print "OK.\n";
    }
    return;
  }
  print "Oops!\n";
  $warningCount++;
  push(@summary,"Verify free space on /tmp");
  print <<EOF;
$WARNING: I can not check /tmp for $needTMPSpace{$JBVersion} free space. You
need to check it manually.
$dashLine
EOF
}


#################################################################

sub rpmqa {
  print "Gathering rpm package list...";
  @rpm = `which rpm`;
  chomp(@rpm);
  $rpm = join("",@rpm);
  if (-x "$rpm") {
     print "Found $rpm, OK.\n";
     @rpmqa = `rpm -q -a`;
     print scalar @rpmqa, " rpm packages are present.\n";
     print "\nDEBUG: ", @rpmqa if $DEBUG;
  } else {
    print "Failed. No RPM?\n";
    $warningCount++;
    push(@summary,"Send info to gyles19\@visi.com about your rpm equivalent.");
    print <<EOF;
$WARNING: I can't find the 'rpm' command.  Some tests will not run properly
on this platform.   Please contact me at gyles19\@visi.com and tell me
what this platform is, how it can be identified, and what command can be
used to identify the versions of packages.

Presently I'm using "grep /etc/issue" to identify the distribution and
version, and "rpm -q -a" to list all installed packages.  I need to know
functional equivalents for your platform.
$dashLine
EOF
  }
}


#################################################################

sub checkDisplay {
  print "Checking for DISPLAY variable...";
  $DISPLAY = $ENV{"DISPLAY"};
  print "DISPLAY=$DISPLAY  ";
  local($needhost) = <<EOF;
The Sun JVM requires the DISPLAY variable provide a host name.
For example, my workstation's name is "joi.aravox.com" so my DISPLAY 
variable must be defined on my linux machine with a command of the form:

  export DISPLAY=joi:0.0

EOF

  if ($DISPLAY eq "" ) {
    print "Oops!\n";
    $warningCount++;
    push(@summary,"export DISPLAY=`uname -n`:0.0");
    print <<EOF;
$WARNING:  Your shell's DISPLAY variable is not set.  The JBuilder
installer is an X11 application which will need this variable to be
set.  JBuilder will also need to have this variable set.

$needhost
$dashLine
EOF
    $DISPLAY=`uname -n`;
    chomp($DISPLAY);
    $DISPLAY.=":0.0";
    print "DISPLAY variable set to $DISPLAY\n";
  } else {
    ($host,$screen) = ($DISPLAY  =~ /([^:]+)?\:(\d+(\.\d+)?)/);
    if ($host eq "" ) {
      print "Oops!\n";
      print $needhost;
      $host=`uname -n`;
      chomp($host);
      $DISPLAY=$host .":" . $screen;
      print "DISPLAY variable set to $DISPLAY\n";
      push(@summary,"export DISPLAY=`uname -n`:0.0");
    } else {
      print "Ok!\n";
    }
  }
}

#################################################################

sub checkFonts {
  print "Checking for urw-fonts package...";
  if (grep(/urw-fonts/,@rpmqa)) {
    print "OK.\n";
  } else {
    print "Oops!\n";
    print <<EOF;
Your machine does not contain the urw-fonts package.  This package
contains the symbol font the JVM will be looking for.
$dashLine
EOF
  }

  $XLSFONTS = join("",`which xlsfonts`);
  chomp($XLSFONTS);
  unless (-x $XLSFONTS ) {
    $warningCount++;
    push(@summary,"Verify presence of urw-fonts package");
    print <<EOF;
$WARNING:  I can't find xlsfonts, so I can't see what
fonts your X11 server offers to Java and JBuilder.
$dashLine
EOF
  } else {
    @fonts = `$XLSFONTS -display $DISPLAY`;
    print "Your X11 server offers " , scalar(@fonts), " fonts.\n";
    print "Checking that X11 has a symbol font...";
    if (grep(/symbol/,@fonts)) {
      print "OK.\n";
    } else {
      print "Oops!\n";
      $warningCount++;
      push(@summary,"Verify presence of urw-fonts package or whatever offers the symbol font");
      print <<EOF;
$WARNING:  Your X11 service does not list symbol as an available
font.  The JVM will complain about this font but should still
launch.  Some glyphs may not display without this font.
$dashLine
EOF
    }
  }
}


#################################################################

sub checkBash {
  print "Trying to check for /bin/sh ...";
  if (-l "/bin/sh") {
    if (-s "/bin/bash" == -s "/bin/sh" ) {
      print "OK. /bin/sh is a symlink to /bin/bash.\n";
    } else {
      print "Oops!\n";
      $warningCount++;
      push(@summary,"Fix /bin/sh -> /bin/bash symlink");
      print <<EOF;
$WARNING: /bin/sh is a symlink but it does not point to /bin/bash.
This may break the linux installer.
$dashLine
EOF
    }
  } elsif ( -s "/bin/bash" == -s "/bin/sh" ) {
    print "\nOdd.  /bin/sh looks like bash but it's not a symlink.\n";
  }
}


#################################################################

sub checkKsh {
  print "Checking for ksh...";
  if (-x "/bin/ksh" || -x "/usr/bin/ksh" ) {
    print "OK.\n";
  } else {
    print "Oops!\n";
    $warningCount++;
    push(@summary,"Enterprise installers need ksh shell (pdksh package)");
    print <<EOF;
$WARNING:  One of the Enterprise Installers will want to use korn shell (ksh.)
This does not seem to be present on your machine.  You may need to come back
and install package pdksh-5.2.14-2 or better.
$dashLine
EOF
  }
}


#################################################################

sub checkNoExec {
  print "Checking for noexec cdrom mount...";
  if (open(FSTAB,"</etc/fstab") ) {
    my @foo = <FSTAB>;
    close(FSTAB);
    my @iso = grep(/iso/,@foo);
    print "\nDEBUG: ", @iso if $DEBUG;
    if (scalar @iso == 0 ) {
      print "Oops!\n";
      $warningCount++;
      push(@summary,"If installing from cdrom, mount -t iso9660 or fix /etc/fstab");
      print <<EOF;
$WARNING: You don't seem to have any iso9660 devices in your /etc/fstab.
You will need to mount your jbuilder cdrom manually, if you have one.

Possible commands:
 mount -t iso9660 -o "noauto,owner,ro" /dev/cdrom /mnt/cdrom
 mount -t iso9660 -o "noauto,owner,ro" /dev/hdc /mnt/cdrom
$dashLine
EOF
    } else {
      my @bar=();
      foreach (@iso) {
         if (/noexec/) {
	         @bar = split;
           print "Oops!\n";
           $warningCount++;
           push(@summary,"Remove 'noexec' keyword in /etc/fstab cdrom entry if you plan to launch the installer from the cdrom");
           print <<EOF
$WARNING!  Device $bar[0] has noexec option in /etc/fstab.
You will not be able to launch the installer from this device until
you remove the 'noexec' or mount the cdrom manually as root.

Possible commands:
 mount -t iso9660 -o "noauto,owner,ro" /dev/cdrom /mnt/cdrom
 mount -t iso9660 -o "noauto,owner,ro" /dev/hdc /mnt/cdrom
$dashLine
EOF
         } else {
           print "iso9660 device " , $bar[0], " is OK.\n";
         }
      }
    }
  } else {
    print "Oops!\n";
    $warningCount++;
    push(@summary,"Couldn't read /etc/fstab");
    print <<EOF;
$WARNING: unable to read /etc/fstab to check for noexec on your cdrom.
$dashLine
EOF
  }
}


#################################################################

sub checkKDE {
  my @kdebase = grep(/kdebase-[\d\.]+/,@rpmqa);
  my @kdevers = ();
  print "Checking for KDE version...";
  foreach (@kdebase) {
    ($ver) = (/kdebase-([\d\.]+)/);
    print "KDE Version $ver, ";
    push(@kdevers,$ver)  if $ver;
  }
  if ($ver =~ /^1\./) {
     print "$ver OK.\n";
  } elsif ($ver =~ /^2\.2\.1/) {
     print "$ver OK.\n";
  } elsif ($ver =~ /^2\./) {
     print "$ver Oops!\n";
     $warningCount++;
     push(@summary,"KDE version may cause you problems.");
     print <<EOF;
$WARNING: Some versions of KDE are incompatible with the bundled JVM.
You should either update the JVM or install KDE 2.2.1 or better.
$dashLine
EOF
    unless ($sawGETNEWJVM ) { 
      $warningCount++;
      push(@summary,"Install newer JVM");
      print &GETNEWJVM();
      print &jdkConfig();
    }
  } else {
    print "$ver OK? (Unexpected version number, no recommendations.)\n";
  }
#kdebase-1.1.2-33
}


#################################################################

sub checkDistribution {
  print "Checking for known Linux distributions...";
  if (open(ISSUE,"</etc/issue")) {
    @issue = <ISSUE>;
    close(ISSUE);
    print "\nDEBUG: ", @issue if $DEBUG;
    if ( &checkRedHat() ) {
    } elsif ( &checkMandrake() ) {
    } else {
      print "Unrecognized distribution.\n";
      print "/etc/issue contains:\n", @issue, "\n";
    }
  } else {
   print "Unable to read /etc/issue\n";
  }
}

sub checkRedHat {
    my $foo = join("",grep(/Red Hat/,@issue));
    $isRedHat = 1 if $foo;
    ($RedHatRelease) = ($foo =~ /\s+([\d\.]+)/);
    if ($isRedHat) {
      print " release $RedHatRelease\n";
    } else {
      return 0;
    }
    if ($RedHatRelease eq "7.0") {
      $warningCount++;
      push(@summary,"Update glibc packages from Red Hat.");
      print <<EOF;
$WARNING: Stock installations of Red Hat 7.0 contain broken glibc packages.
You must download and install all recommended glibc updates.
See this Borland FAQ for some pointers (probably out of date by now:)

http://community.borland.com/article/0,1410,26034,00.html
$dashLine
EOF
      print &ulimitInfo();
      push(@summary,"ulimit -s 2048");
      $warningCount++;
    }
    if ($RedHatRelease eq "6.2") {
      print "Red Hat 6.2.  Good!\n";
      $Interesting = 0;  # the only one I'm not collecting logs for
    } elsif ($RedHatRelease eq "7.1" && 
             &isJB4() && 
             ! $sawGETNEWJVM) {
      print &GETNEWJVM();
      print &jdkConfig();
      push(@summary,"Install newer JVM");
    }
    return $isRedHat;
}

#################################################################

sub checkMandrake {
    my $foo = join("",grep(/Mandrake/,@issue));
    $isMandrake = 1 if $foo;
    ($MandrakeRelease) = ($foo =~ /release ([\d\.]+)/);
    if ($isMandrake) {
      print " release $MandrakeRelease\n";
    } else {
      return 0;
    }
    if ($MandrakeRelease eq "8.0") {
#      print &ulimitInfo();   # printed in Kernel check now.
       $warningCount++;
       push(@summary,"Manually mount your Enterprise cdrom with mount -t iso9660 /dev/cdrom /mnt/cdrom");
       print <<EOF;
$WARNING:  Mandrake 8.0 should be updated to the June FREQ or later.
GA Mandrake 8.0 out of the box seems to have more problems.

You may need to manually remount your cdrom with:

  \$ umount /mnt/cdrom
  \$ mount -t iso9660 /dev/cdrom /mnt/cdrom

(The automounter seems to to mount the JBuilder platter incorrectly, so
do it manually.)

Mandrake 8.0 seems to require Sun 1.3.1 or IBM 1.3.0-8 or better.
Blackdown's latest 1.3.0 or 1.3.1 may also work.

Be sure to use the "LAX_VM /path/to/new/jdk/bin/java" parameters on
all installers you launch.
$dashLine
EOF
    }
    return $isMandrake;
}

#################################################################

sub ulimitInfo {
  return <<EOF;
$WARNING: Distributions using kernel 2.4.3.  

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

Bash command:
  ulimit -s 2048

Tcsh command:
  limit stacksize 2048
$dashLine
EOF
}

#################################################################

sub checkForKawa {
  print "Checking for Kawa packages...";
  if (grep(/kawa/i,@rpmqa)) {
    print "Oops!  Kawa is present!\n";
    $warningCount++;
    push(@summary,"rpm --erase `rpm -q -a | grep kawa`");
    print <<EOF;
$WARNING:  Your machine appears to have Kawa installed.  Kawa is a clean-room
implementation of java which is incomplete.  Kawa's binaries and libraries are
installed in /usr/bin and /usr/lib and will appear earlier on the system paths
where they will conflict with Sun/IBM/Blackdown installations.  You should
remove all kawa packages before proceeding.

Suggested command:

  rpm -q -a | grep -i kawa | xargs rpm --erase
$dashLine
EOF
  } else {
    print "No Kawa found.  OK.\n";
  }
}


#################################################################

sub checkForLocale {
  my $loc = $ENV{"LANG"};
  print "Checking locale..." , $loc, "...";
  if ( $loc =~ /^en/i ) {
    print "English.  OK.\n";
  } else {
    $Interesting = 1;
    print "Oops!\n";
    $warningCount++;
    push(@summary,"Non-english Locale may cause problems with serial/key entry");
    print <<EOF;
$WARNING:  Your current locale is set to $loc.  If your serial number or
registration key contains special characters, particularly the question mark
"?", then you may experience difficutlies completing the license dialog.

This problem is caused by a bug in JDK 1.3 (and may have been fixed in
JDK 1.3.1 and 1.4.)  To work around this JVM bug, temporarily change your
locale to en_US (US English) and launch "jbuilder -license" to re-enter the
license dialog.  Once you have successfully closed the dialog, exit JBuilder
and restore you locale to its original setting.
$dashLine
EOF

  }
}


#################################################################

sub checkKernel24 {
#
# need to verify this one
#
  print "Checking kernel version...";
  $kernel = `uname -a`;
  if ($kernel =~ /2\.4\./) {
    print "2.4.x kernel! \n";
    print &GETNEWJVM();
    push(@summary,"Install newer JVM");
    print &jdkConfig();
    if ( &isJB4() ) {
      print &LD_ASSUME_KERNEL();
    } elsif ( &isJB5() ) {
      print &LD_ASSUME_KERNEL();
  
    }
    if ($kernel =~ /2\.4\.3/ ) {
      print &ulimitInfo(); 
      push(@summary,"ulimit -s 2048");
      $warningCount++;
    }
  } else {
    print "Not a 2.4 kernel. OK.\n";
  }
}


#################################################################

sub checkKernelSMP {
  print "Checking for SMP kernel...";
  if ($kernel =~ /SMP/i) {
    $isSMPKernel = 1;
    print "SMP found. "; 
    if ( &isJB4() ) {
      $warningCount++;
      push(@summary,"JB4's IBM JVM is unusable on SMP kernels. Replace it.");
      print <<EOF;
$WARNING:  The JDK bundled with JB4 is IBMs and is not compatible with
SMP (multiprocessor) kernels.  You must replace download and install a newer
JVM which specifically states it is compatible with your kernel.
Sun JDK 1.3.0 is the first Sun JDK which is known to support SMP kernels.
Blackdown 1.3.0 may support them as well.
$dashLine
EOF
    }
  } else {
    print "Not SMP. OK.\n";
  }
}

sub JB4IBMWarning {
  $sawJB4IBMWarning = 1;
  return <<EOF;
$WARNING:  The IBM JDK bundled with JB4 is known to have a broken debugger.
After installing JBuilder, you are strongly encouraged to either download
the latest release of IBM 1.3.0, install it on your machine, and edit
jbuilder4/bin/jdk.config to adjust all paths to point to the replacement
JDK.  Do not delete the bundled JDK itself, you may need it if you later need
support from Borland Devsupport.

The IBM JVM is also much less tolerant of glibc upgrades.  Check the JVM's
readme/install instructions carefully to compare its requirements to your
machine's configuration.  

The JB4 JVM does not run at all on 2.4.x kernels and must be replaced.

Sun's 1.3.0 will also work, but JB4 will exhibit some keyboard oddities with
the escape, del, and backspace keys under some conditions.  I believe, but
don't know for certain, that these oddities are caused either by bugs in 
the replacement JDK, or by workaround code placed in JB4 to adjust for
bugs in the original IBM JDK.
$dashLine
EOF
}

#################################################################

sub JB5SoundWarning {
  return <<EOF;
$WARNING:  JB5 contains new audio support which can cause problems for
some users.  The most common symptom of this problem is the JVM dumping core
immediately after a build finishes.  The cause is that JBUilder's new audio
features are enabled by default, and the default sound settings will play a
tone if there are any errors or warnings found in the build.  (It may also
play a tone upon build completion, I haven't studied it closely 'cause my
own machine dumps core!)

While the JVM is writing the core file, JBuilder itself may appear to be
totally unresponsive.  This is because it takes a long time for the kernel
to create a 250meg core file!  Give it five minutes or so to complete and 
the wedged JBuilder IDE will disappear by itself.

The core files stem from a system audio library, so I do not know if the
problem is in the system library, or in the JVM's use/misuse of that library.

To eliminate this problem, launch JBuilder and visit 

  Tools | IDE Settings | Audio

and disable all audio support.  This will disable the new audio feature
within JBuilder 5 without affecting any other sound settings on your
dekstop.

This problem is known to occur on Red Hat 6.2 with KDE 1.1.2,
Red Hat 7.x with KDE, and Mandrake 8.0 with WindowMaker 0.64.0.
$dashLine
EOF
}

#################################################################

sub isJB5 {
  return $JBVersion eq "JB5";
}

#################################################################

sub isJB4 {
  return $JBVersion eq "JB4";
}


#################################################################

sub checkForJava {
  print "Checking for existing JVM...  ";
  $java = join("",`which java`);
  chomp($java);
  if (-x "$java") {
    @java = `$java -version 2>&1`;
    $javaversion = join("", @java);
    print "Found one...\n";
    $warningCount++;
    push(@summary,"$java on path, may confuse installers or conflict with JBuilder. \n\tTo force its use, try \"./install.bin LAX_VM $java\"");
    print <<EOF;
$WARNING: Java executable found on your PATH at $java.

$javaversion

This might confuse the installer if the installer believes it can run on
this verson of java but this version is too old (or too new.) 

You can force the installer to use this JVM by invoking the installer with
extra parameters like this:

  ./install.bin LAX_VM $java

If you're running installers manually, you may need to use the 
  LAX_VM $java
parameters for every installer, not just the first one you use.

If you have difficulties installing the samples and documentation packages,
then you need to launch those installers with LAX_VM pointing at the java
command located in jbuilder5/jdk1.3/bin/java instead.  These installers seem
to (stupidly) assume that jbuilder is located relative to the first JVM they
find on your shell's PATH, even if it isn't JBuilder's JVM.  You may need to
temporarily remove other JVMs from your path for these installers to 
function properly.

$dashLine
EOF

  } else {
    "Java not found on path. OK, we'll use the installer's bundled JVM.\n";
  }
}


#################################################################

sub checkForUsrBinJava {
  print "Checking for /usr/bin/java...";
  if (-x "/usr/bin/java" ) {
    $warningCount++;
    push(@summary,"Suggest removal of /usr/bin/java.");
    print <<EOF;
$WARNING: There is a /usr/bin/java executable on your system.  On Linux
this java is usually Kawa, which is known to cause conflicts with other JVMs
due to it and its libraries being on the default system path.  

Please investigate this java and remove it if necessary.  (If the installer
finds it and dies, assume it's a problem.  If JBuilder dumps core or complains
about libjvm.so, libjava.so, etc, then removal is necessary.)
$dashLine
EOF
    print `/usr/bin/java -x`;
    print `$rpm -q -f /usr/bin/java`;
  } else {
    print "Not found.  OK.\n";
  }
}


#################################################################

sub header {
  return <<EOF;
JBCheck Version $Revision ($RevisionDate)
Copyright 2001 Joi Ellis, all rights reserved.

EOF
}

#################################################################

sub credits {
  return <<EOF;

This tool is an unofficial work-in-progress.  If you have any suggestions
for improvement, please mail the output and your comments to gyles19\@visi.com.
I am particularly interested in results on non-Red Hat and non-English
platforms.

My thanks to the following for donating debug logs and suggestions:
  Herb Greenma, hyrum\@kenobi, johnnyb\@picard, Klaus Kuehn, will sipsey, 
  Josh Fletcher, Eduardo Goncalves


EOF
}

#################################################################

sub jdkConfig {
  push(@summary,"May need to edit jbuilder5/bin/jdk.config");
  $warningCount++;
  return <<EOF;
WARNING: If you need to replace JBuilder's own JDK (as opposed to using
LAX_VM to run the installer on a different JDK) then you must edit the
following file:

  jbuilder5/bin/jdk.config

It contains the following lines:

  # Set the path for the JDK
  javapath /home/joi/jbuilder5/jdk1.3/bin/java
  # Add the tools.jar
  addpath /home/joi/jbuilder5/jdk1.3/lib/tools.jar
  vmparam -Xverify:none

You must change both the 'javapath' line and the 'addpath' line to point
JBuilder's launcher at the java command and the tools.jar for the new JDK.
If you neglect to change the path to tools.jar, the debugger will not be
accessible at all.


EOF
}