Closed Bug 150219 Opened 22 years ago Closed 22 years ago

wrapper shell script fails to resolve symbolic link in its name

Categories

(SeaMonkey :: Build Config, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 57866

People

(Reporter: Marco.Franzen, Assigned: netscape)

Details

Attachments

(1 file)

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.0.0) Gecko/20020529
BuildID:    2002052918

The wrapper shell script mozilla contains two bugs, each of which alone prevents
it work out how to set MOZILLA_FIVE_HOME.
Firstly, it gives up without setting "found" flag on it last loop round just
when it is done.
Secondly, relative link targets need to be interpreted from the directory where
the link is.

Reproducible: Always
Steps to Reproduce:
1. Install moz 1.0 release in (say) /usr/local/mozilla/1.0
2. ln -s ../mozilla/1.0/mozilla /usr/local/bin
3. unset MOZILLA_FIVE_HOME
4. /usr/local/bin/mozilla   


Actual Results:  Cannot find mozilla runtime directory. Exiting.

Expected Results:  Successfully launch the browwer with MOZILLA_FIVE_HOME set to
the directory where the script physically lives. That is the link target if the
path name under which it was invoked is a symbolic link (etc if that target is a
symlink again etc).
This fixes it for me.
-> CLS
Assignee: Matti → seawood
Component: Browser-General → Build Config
QA Contact: imajes-qa → granrose

*** This bug has been marked as a duplicate of 57866 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
v dup
actually marking verified.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: