Building XULrunner on Mac OS X (Snow Leopard)
DaveB
Mac OS 10.6; Xcode 3; gcc 4.2
We are working on a large product in which we have modified XUL
runner
and a lot of XUL files. The last time we synchronized with the
Mozilla
project was at the end of Febuary, 2008. We have been developing
mostly on Windows and Linux, and have recently tried to get the Mac
build going. The following is the situation:
1. We can build our project just fine on Windows and Linux.
2. We can build Firefox and XULRunner, as gotten from the main
branch,
just fine.
3. Before the 2/2008 merge, the Mac build was working just fine.
4. Having fixed the problem identified after the earlier post, we can
complete the build, but the install-app fails.
The output from this step begins with several hundred messages of the
form
libxpt: File length in header does not match actual length. File may
be corrupt
###!!! ASSERTION: Unable to read an XPT file, turn logging on to see
which file: 'Error', file /Users/daveb/Prince2/mozilla/xpcom/reflect/
xptinfo/src/xptiInterfaceInfoManager.cpp, line 1108
These are followed by a bunch of messages reading
libxpt: File length in header does not match actual length. File may
be corrupt
###!!! ASSERTION: : 'Error', file /Users/daveb/Prince2/mozilla/xpcom/
reflect/xptinfo/src/xptiInterfaceInfoManager.cpp, line 962
These are followed by the expected registration messages beginning
with
*** Registering components in: xpconnect
Finally, there are pairs of messages
###!!! ASSERTION: This is not supposed to fail!: 'Error', file /Users/
daveb/Prince2/mozilla/js/src/xpconnect/src/nsXPConnect.cpp, line 1040
###!!! ASSERTION: Failed to initialize nsScriptSecurityManager:
'NS_SUCCEEDED(rv)', file /Users/daveb/Prince2/mozilla/caps/src/
nsScriptSecurityManager.cpp, line 3372
Has anyone seen a similar situation? Can anyone tell me what logging
capability is referred to in the first messages and how I turn it on?
---Dave
Ted Mielczarek
...
> The output from this step begins with several hundred messages of the
> form
>
> libxpt: File length in header does not match actual length. File may
> be corrupt
> ###!!! ASSERTION: Unable to read an XPT file, turn logging on to see
> which file: 'Error', file /Users/daveb/Prince2/mozilla/xpcom/reflect/
> xptinfo/src/xptiInterfaceInfoManager.cpp, line 1108
>
...
> Has anyone seen a similar situation? Can anyone tell me what logging
> capability is referred to in the first messages and how I turn it on?
>
There appears to be logging here controlled by the MOZILLA_XPTI_STATS
environment variable. It looks like you can set that variable to a filename,
and the logging info will be printed there:
http://mxr.mozilla.org/mozilla-central/source/xpcom/reflect/xptinfo/src/xptiInterfaceInfoManager.cpp#135
(I don't know anything else about this code, I just poked around the file
mentioned in the assertion you pasted.)
-Ted
DaveB
> On Thu, Dec 3, 2009 at 7:34 PM, DaveB <daveb4...@gmail.com> wrote:
>
> ...
>
> > The output from this step begins with several hundred messages of the
> > form
>
> > libxpt: File length in header does not match actual length. File may
> > be corrupt
> > ###!!! ASSERTION: Unable to read an XPT file, turn logging on to see
> > which file: 'Error', file /Users/daveb/Prince2/mozilla/xpcom/reflect/
> > xptinfo/src/xptiInterfaceInfoManager.cpp, line 1108
>
> ...
>
> > Has anyone seen a similar situation? Can anyone tell me what logging
> > capability is referred to in the first messages and how I turn it on?
>
> There appears to be logging here controlled by the MOZILLA_XPTI_STATS
> environment variable. It looks like you can set that variable to a filename,
> (I don't know anything else about this code, I just poked around the file
> mentioned in the assertion you pasted.)
>
> -Ted
Thanks Ted. You are correct about the logging. Unfortunately, turning
is on provided no useful information. I got a line that said "Start
logging", 3 blank lines, and a line that said "End logging." Sigh.
---Dave