Closed Bug 152953 Opened 23 years ago Closed 23 years ago

Chrome registration fails in cross-compiled ARM Linux build

Categories

(Core Graveyard :: Skinability, defect)

Other
Linux
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 87965

People

(Reporter: dr, Assigned: bugs)

References

Details

I am attempting to get Mozilla to work on the iPaq, running the Familiar Linux distribution (http://familiar.handhelds.org). I'm running an Embed 0.9.7 build (created from embedding/config), which partially works. One of many problems I'm hitting is that chrome registration seems to fail on startup: *** Chrome Registration of skin: Checking for contents.rdf at jar:resource:/chrome/embed.jar!/skin/classic/communicator/ WARNING: Trying old-style manifest.rdf. Please update to contents.rdf., file nsChromeRegistry.cpp, line 2031 The embed.jar file does contain skin/classic/communicator/contents.rdf, and when I compile it for my i386 host (rather than cross-compiled for arm-linux), I do not get these warnings. Further warnings include: WARNING: chrome: failed to get base url for chrome://global/content/xul.css -- using wacky default, file nsChromeRegistry.cpp, line 543 WARNING: CSSLoaderImpl::LoadSheet: Load of URL 'chrome://global/content/xul.css' failed. Error code: 6, file nsCSSLoader.cpp, line 1291 WARNING: CSSLoaderImpl::LoadAgentSheet: Load of URL 'chrome://global/skin/scrollbars.css' failed. Error code: 6, file nsCSSLoader.cpp, line 168 I suspect the problem might be in libjar, but that's just a first guess.
Blocks: 152955
I've attached a log of assertions to bug 152955, for the big picture...
You want to apply the patch from bug 87965 which was fixed long after 0.9.7 *** This bug has been marked as a duplicate of 87965 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Even if you fix the libjar problem you'll still get warnings since your installed-chrome.txt references chrome jars I don't think you have in an embedding setup. I assume you can live with assertions for development work, otherwise remove installed-chrome.txt references to jars you don't want.
Great! Thanks for the sharp eyes, dveditz :)
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.