running JBuilder on unsupported linux platforms

Thread View: borland.public.jbuilder.linux

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by Jeroen Zwartepoorte Sun, 26 Sep 2004 14:10

#258

Author: Jeroen Zwartepoorte
Date: Sun, 26 Sep 2004 14:10

57 lines
2714 bytes

I'm running linux on a powerbook/powermac (linux/ppc). This platform is
not supported by the JBuilder installer (no binaries for this platform).
You can install JBuilder fine on it by running the install.bin script
manually:

sh install.bin LAX_VM /path/to/java

However, after installation you have no jbuilder script/program you can
use to start jbuilder. I've written a simple Python script which starts
JBuilder. Feel free to modify or use it yourself.

Regards,

Jeroen

p.s. The crimson.jar is a custom jar which contains the org.apache.*
packages from the rt.jar from the Windows JDK. The IBM JDK 1.4.2 for
linux/ppc doesn't contain these packages.

#! /usr/bin/env python

import os, glob, sys

javahome = os.environ.get('JAVA_HOME')
if not javahome or not os.path.isdir(javahome):
    print "JAVA_HOME is not set; without it we can't start JBuilder"
    exit

jbhome = '/home/jeroen/Java/JBuilder2005'
if not os.path.isdir(jbhome):
    print jbhome + " does not exist"
    exit

os.chdir(jbhome + '/bin')

jars  = glob.glob('../lib/*.jar')
jars += glob.glob('../lib/bes/*.jar')
jars += glob.glob('../lib/servers/*.jar')
jars += glob.glob('../lib/ext/*.jar')
jars += glob.glob('../patch/*.jar')

jarcp = ''
for file in jars:
    if file == '../lib/sanctuary.jar':
        continue
    jarcp += file + ':'

jarcp += javahome + '/lib/tools.jar:'
jarcp += '../thirdparty/jakarta-tomcat-5.0.27/common/lib/servlet-api.jar'

bootcp = '../lib/crimson.jar:../lib/javac.jar:../lib/lawt.jar:../lib/XPTreeUIFix.jar:../lib/TabbedPaneFix.jar:../lib/SequencedEventFix.jar:../PopupFixes.jar'

args = ''
for arg in sys.argv[1:]:
    args += arg + ' '

os.system(javahome + '/bin/java -Xbootclasspath/p:' + bootcp + ' -Xms32m -Xmx256m -cp ' + jarcp + ' com.borland.jbuilder.JBuilder ' + args)

Re: running JBuilder 2005 on Gentoo Linux

#264

Author: Randy
Date: Fri, 01 Oct 2004 14:04

30 lines
3647 bytes

My previous install was on redhat, but on a network share so I could just access that under gentoo. The trick is I had to have compatibility libs installed (just like fedora/mandrake). on gentoo, do this (probably as root, or as a user in the portage group:
emerge lib-compat

Next, the installer would start /mnt/cdrom/install_linux.sh, but would claim that it succeded, but would fail, since after the product selection, it would not ask me for what type (full/minimal/custom) for Jbuilder. In the readme on the cd, it mentions then running Disk1/InstData/Linux/VM/install.bin. This failed with

Unpacking the JRE...
Extracting the installation resources from the installer archive...
Configuring the installer for this system's environment...
awk: error while loading shared libraries: libdl.so.2: cannot open shared object file: No such file or directory
dirname: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
/bin/ls: error while loading shared libraries: librt.so.1: cannot open shared object file: No such file or directory
basename: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
dirname: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
basename: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
hostname: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory

Googling this indicates the problem is in the install.bin file. I then copied the disk1 to harddrive, and proceeded to edit the install.bin file Commenting the following (it occurs twice):
export LD_ASSUME_KERNEL

This still failed due to it failing the checksum If you added ONE # and no spaces to each line, for a total of 2 new chars, delete the last char on the line you comment, ie:
#export LD_ASSUME_KERNEL=2.2.
and
#export LD_ASSUME_KERNE

This lets the checksum pass, and ta-da! It installs. When prompted for the 2nd disk, put it in the cdrom and your fine (you may have to mount it if you don't have supermount/all the other stuff) running.) If you're confident in your copy, you could probably comment out the checksum chuck of code too.

Apparently this is a bug that other distros (I've seen suse mentioned, and mandrake, debian) have had with the installer with some other apps. I think it is a fix in the installer to workaround a bug that is now fixed or have read stuff that indicates that at least.

So far, JBuilder seems to run, but I haven't done anything much yet on it. On the gentoo forums there are quite a few successes with jbuilder.

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads