I am having problems installing JBuilder 6 on Solaris. What should I do?

First, verify that you do not have any of the following problems:

1. Don't forget to check the installation instructions on your CD for possible workarounds to install problems. Just open the "index.html" file in the root of the CD to find the instructions.
   
   
2. You do not have the required patches installed to run JDK 1.3.1. Installing the required patches will solve the majority of install-related problems. Please verify that you have the patches installed from this page.
   
   
3. Check this FAQ.
   
   
4. You are running Solaris 2.6 (5.6) or earlier. JBuilder 6 requires Solaris version 2.7 (5.7) or 2.8 (5.8). Please see the JBuilder 6 System Requirements page for information on supported platforms.
   
   
5. You do not have enough space in your system's temp directory (usually named "/tmp"). You will need approximately 200MB-500MB of space in your temp directory when installing JBuilder on Solaris. Also note that the installer will leave files behind in the temp directory when it finishes. You should delete these files as they can take up quite a bit of space and may prevent other installs from completing.
   
   
6. You have a JDK on your system path. This problem may become apparent if you are logged in as root. You need to remove any JDK entries from your path and then run the installer.
   
   
7. You can try running the actual JBuilder installer (as opposed to the install launcher found in the root of the CD) and specifying the virtual machine for the installer. The "real" JBuilder installer can be found in the /Solaris directory on your JBuilder CD. This will require that you have JDK 1.3 installed first. Here is an example command line (assuming JBuilder 6 Enterprise is being installed):

   ./ent_install.bin LAX_VM /usr/local/jdk1.3/bin/java

   Please note that you must specify the location of the "java" executable in the JDK "bin" directory, not just the JDK home path.
   
   

If you can verify that you don't have any of the above problems, please follow the steps below:

NOTE: These instructions assume that you are logged in as "root" and are using "sh" for your shell. Be sure to adjust the commands for your shell, if different.

You will need the debug output from running the installer on your machine. Here are the steps to get the complete debug output:

1. Open a console.
2. Create an environment variable named "LAX_DEBUG" and set it to true. For example:

   # LAX_DEBUG=true

3. Export "LAX_DEBUG" so that other shells can use it. For example:

   # export LAX_DEBUG

4. Run the installer. Observe the debug output that will be printed to your console window.
5. Copy ALL of this output.
6. Paste the contents to a text file and save. You may exit/kill the installer at this time if it has not already exited.

Now that you have the debug output in a file you need to get it to Developer Support. The best way to do this would be to open a Web Install Support case at:

http://pso.borland.com/devsupport/

Let us know in the case notes that you have a debug output file to send to us. Do NOT paste the debug output into the case notes as it may be too large and could get lost/cut-off.