To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=63927





------- Additional comments from [EMAIL PROTECTED] Thu Aug 21 08:05:33 +0000 
2008 -------
Applying slight modifications (fixing obvious errors; making sure *all* internal
libraries relevant for startup are actually detected as internal) of
<http://svn.gnome.org/viewvc/ooo-build/trunk/patches/dev300/speed-local-link.diff?revision=12380&view=markup>
and
<http://svn.gnome.org/viewvc/ooo-build/trunk/patches/dev300/speed-local-link-except.diff?revision=12937&view=markup>
to DEV300m29, building unxlngi6.pro with the Sun Hamburg tool chain, and
executing soffice on a random Ubuntu box (Linux v20z-so3 2.6.15-29-server #1 SMP
Mon Sep 24 17:37:57 UTC 2007 i686 GNU/Linux) with RTL_LOGFILE set appropriately,
then whether OOO_DISABLE_INTERNAL is unset or =1 does not seem to make any
difference.  The resulting log files all look more or less like

 opening log file 1219305051.526439 seconds past January 1st 1970
 corresponding to 6 ms after timer start
 Process id is 14911
 000006 1 | : PERFORMANCE - enter Main()
 001729 1 | : PERFORMANCE - enter Application::Execute()
 001729 1 { PERFORMANCE - DesktopOpenClients_Impl()
 001734 1 } PERFORMANCE - DesktopOpenClients_Impl()
 closing log file at 005519

@mmeeks:  Am I missing something (e.g., is the patch only useful for specific
tool chains or OS versions)?

---------------------------------------------------------------------
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to