To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=103772
------- Additional comments from cl...@openoffice.org Wed Jul 29 11:08:26 +0000
2009 -------
The requirement is triggered by changing (mozilla's) configure's default without
adapting accordingly.
The change in question of the seamonkey-source-1.1.14.patch is
- MOZ_ENABLE_COREXFONTS=${MOZ_ENABLE_COREXFONTS-}
+ MOZ_ENABLE_COREXFONTS=${MOZ_ENABLE_COREXFONTS-1}
So instead of linking with pango, one can revert that change.
But unfortunately even vanilla seamonkey 1.1.17 cannot be built with OOo's set
of configure options without additional patch (see attached). The patch is
needed because otherwise the compiler (gcc 4.3.x) will complain about nsresult
and PRUint32 not naming types / or nsIFontEnumerator and result (in the
commented-out function) not being declared in this scope. Probably there are
other ways to solve that problem, but it was the easiest way for me to solve
(not really c++ savy).
But given those problems let me ask:
On what systems has the seamonkey cws been built? More precise: What gcc was
used? Or how would that pangox not be necessary for the devs of the cws? Why was
the MOZ_ENABLE_COREXFONTS-default in configure changed?
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@dba.openoffice.org
For additional commands, e-mail: issues-h...@dba.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org
