Closed Bug 306992 Opened 19 years ago Closed 19 years ago

chrome not installed correctly with 'make -f client.mk install'

Categories

(SeaMonkey :: Build Config, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 302215

People

(Reporter: wsheets, Unassigned)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20050903 SeaMonkey/1.1a
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20050903 SeaMonkey/1.1a

After building seamonkey(HEAD) from CVS sources, I can run the program with no
problem from the obj/dist/bin directory, but when I run /usr/local/bin/seamonkey
I get error messages (in red) in a (very wide) status bar complaining about
syntax errors in chrome files relating to 'inspector' and 'reporter'.

I know this is a chrome-related error because all I need to do to fix it is
simply copy the chrome files from the obj tree to the /usr/local/lib tree
and the errors disappear.

I've tried copying the files one by one and I still get the error -- only when I
copy *all* the chrome files at the same time does the error disappear.  This is
behavior I don't understand, but I have tried it three times and each time I get
the same results.

BTW, this is new since seamonkey-1.0a.  I can copy the chrome directory from
1.0a to 1.1a and this bug disappears.

Reproducible: Always

Steps to Reproduce:
1.Build seamonkey-1.1a from CVS sources
2.make -f client.mk install (to e.g. /usr/local/lib/seamonkey-1.1a/)
3.Run /usr/local/bin/seamonkey and look for the chrome errors.  (Even
  after running seamonkey as root first.)
nuking chrome/overlays.rdf was sufficient to get it working again.  This has
been reported before, but I had not been able to reproduce before now.  "make
install" was the step I was missing.

*** This bug has been marked as a duplicate of 302215 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Version: unspecified → Trunk
You need to log in before you can comment on or make changes to this bug.