Closed Bug 110724 Opened 24 years ago Closed 23 years ago

/usr/bin/mozilla RPM script doesn't locate IBM's JRE properly

Categories

(SeaMonkey :: Build Config, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: manfred.h, Assigned: blizzard)

References

()

Details

The directory structure of the IBM JRE (IBMJava2-JRE-1.3-9.0 on Red Hat Linux 7.2) is different compared to Sun's jre (jre-1.3.1_01-fcs). The start script /usr/bin/mozilla, which is contained in Mozilla's RPMs for Linux, tries to locate the "java" script based on where the plugin is stored; while this works OK for the Sun version, it doesn't for IBM's because IBM have the plugin as well as the "java" script stored in the *same* directory. This is compensated by the following patch: --- ./usr/bin/mozilla.orig Fri Oct 12 09:01:19 2001 +++ ./usr/bin/mozilla Thu Nov 8 12:15:32 2001 @@ -81,22 +81,14 @@ function set_jvm_vars() { JVM_BASE=`basename $JVM_LINK` JVM_DIR=`echo $JVM_LINK | sed -e s/$JVM_BASE//g` - JVM_DIR=${JVM_DIR}../../../bin/ - - # make sure it was found - if [ -z "$JVM_DIR" ]; then - return - fi - - # does it exist? - if [ ! -d "$JVM_DIR" ]; then - return - fi - JVM_COMMAND=$JVM_DIR/java - # does the command exist? - if [ ! -r "$JVM_COMMAND" ]; then - return + if [ ! -r $JVM_COMMAND ]; then + JVM_DIR=${JVM_DIR}../../../bin/ + JVM_COMMAND=$JVM_DIR/java + # does the command exist? + if [ ! -r "$JVM_COMMAND" ]; then + return + fi fi # export this temporarily - it seems to work with old and new
over to the right location
Assignee: asa → joe.chou
Component: Browser-General → OJI
Keywords: patch
QA Contact: doronr → pmac
Hmm ... This is about mozilla/build/package/rpm/SOURCES/mozilla.sh. I do not think this relate to OJI. Let to move this to "Build config".
oddly this is not an oji issue.
Assignee: joe.chou → blizzard
Component: OJI → Build Config
QA Contact: pmac → granrose
Summary: /usr/bin/mozilla script doesn't locate IBM's JRE properly → /usr/bin/mozilla RPM script doesn't locate IBM's JRE properly
Marking new.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Checked in the patch. Thanks!
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.