1105044
On Friday, November 28, 2014 9:07:09 PM UTC+8, Benjamin Smedberg wrote:
> On 11/27/2014 10:38 PM, allencb...@gmail.com wrote:
> > I've reported this in bugzilla. Any one has any workaround?
>
> I commented in the bug
> (https://bugzilla.mozilla.org/show_bug.cgi?id=1105044). This is proba
On 11/27/2014 10:38 PM, allencb...@gmail.com wrote:
I've reported this in bugzilla. Any one has any workaround?
I commented in the bug
(https://bugzilla.mozilla.org/show_bug.cgi?id=1105044). This is probably
due to the MacOS v2 signing work which restructured the bundles. Since
XULRunner is
I've reported this in bugzilla. Any one has any workaround?
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
I am aware of a similar message on another platform. In that case it was caused
by other dependencies missing. XPCOM was ok.
Bob
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
The new XULRunner 34 fails with "Couldn't load XPCOM" error when running
MacOSX. It works fine in Win32. Besides, FF34 works fine too. Anyone any
idea what caused this? XULRunner 33 works fine in MacOSX too. I'm using OS
X Yosemite.
___
dev-pla
5 matches
Mail list logo