Closed Bug 967230 Opened 11 years ago Closed 10 years ago

No longer able to start the browser if CWD doesn't contain libicudata.52.dylib

Categories

(Firefox Build System :: General, defect)

x86
macOS
defect
Not set
blocker

Tracking

(Not tracked)

RESOLVED FIXED
mozilla30

People

(Reporter: bzbarsky, Assigned: ehsan.akhgari)

References

Details

(Keywords: regression)

Attachments

(1 file)

With a build from rev 2efbd5388bc7:

  mozilla% ../obj-firefox/dist/NightlyDebug.app/Contents/MacOS/firefox
  XPCOMGlueLoad error 4:0 for file /Users/bzbarsky/mozilla/vanilla/mozilla/../obj-firefox/dist/NightlyDebug.app/Contents/MacOS/libicuuc.52.dylib:
  Library not loaded: libicudata.52.dylib
  Referenced from: /Users/bzbarsky/mozilla/vanilla/obj-firefox/js/src/intl/icu/target/lib/libicuuc.52.1.dylib
  Reason: image not found
  Couldn't load XPCOM.

With a current tip build:

  /Users/bzbarsky/mozilla/inbound/obj-firefox/dist/NightlyDebug.app/Contents/MacOS
  XPCOMGlueLoad error 4:0 for file /Users/bzbarsky/mozilla/inbound/obj-firefox/dist/NightlyDebug.app/Contents/MacOS/libicuuc.52.dylib:
  Library not loaded: libicudata.52.dylib
  Referenced from: /Users/bzbarsky/mozilla/inbound/obj-firefox/dist/NightlyDebug.app/Contents/MacOS/libicuuc.52.dylib
  Reason: image not found
  Couldn't load XPCOM.

If I repeat that with cwd either ../obj-firefox/dist/NightlyDebug.app/Contents/MacOS/ or ../obj-firefox/dist/bin (still running the same binary from NightlyDebug.app), the build starts.

So it looks like we're using a cwd-relative path to look for libicudata.52.dylib?

This _may_ need --enable-shared-js.  Checking now.

Note that we're apparently only copying the .52.dylibs into dist/bin, not the .52.1.dylibs.  But the second error above doesn't mention .52.1 anywhere.
A current tip opt build gives the second error above too.
Er, I lied.  With the "current tip" build the error above is from running it slightly differently.  In particular, that one is if I do:

  mozilla% /Users/bzbarsky/mozilla/vanilla/obj-firefox/dist/NightlyDebug.app/Contents/MacOS/firefox

instead of using a relative path to the objdir.
I have a fix which I cannot land because the tree is closed.
Assignee: nobody → ehsan
Component: JavaScript Engine → Build Config
Attached patch Fix (deleted) — Splinter Review
Keywords: checkin-needed
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla30
Product: Core → Firefox Build System
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: