On Sun, Feb 06, 2011 at 03:05:43PM +0100, Francois Tigeot wrote:
On Sat, Feb 05, 2011 at 11:52:33PM +0100, Francois Tigeot wrote:
On Sat, Feb 05, 2011 at 08:52:19PM +0100, Francois Tigeot wrote:
On Sat, Feb 05, 2011 at 04:00:39PM +0000, Caolán McNamara wrote:
On Sat, 2011-02-05 at 08:43 +0100, Francois Tigeot wrote:
I can't get the build to stop failing in i18npool. The only error message is
"Exception on createRegistryServiceFactory" and I can't get any more details.
It seems this error is very common; I've found many references to build
failures in i18npool with the createRegistryServiceFactory message. It
appears on both LibreOffice and OpenOffice on all sort of platforms.
The attached patch prints the exception message in saxparser.cxx.
It would be useful to have it in tree.
Sorry, forgot to attach the file.
--
Francois Tigeot
diff --git a/i18npool/source/localedata/saxparser.cxx b/i18npool/source/localedata/saxparser.cxx
index 98d2e5a..6c1b1aa 100644
--- a/i18npool/source/localedata/saxparser.cxx
+++ b/i18npool/source/localedata/saxparser.cxx
@@ -323,9 +323,11 @@ SAL_IMPLEMENT_MAIN_WITH_ARGS(argc, argv)
::rtl::OUString::createFromAscii(argv[4]),
::rtl::OUString::createFromAscii(argv[5]) );
}
- catch ( Exception& )
+ catch ( Exception &e )
{
printf( "Exception on createRegistryServiceFactory\n" );
+ OString o = OUStringToOString( e.Message, RTL_TEXTENCODING_ASCII_US );
+ printf( " Exception message: %s\n", o.pData->buffer );
exit(1);
}
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.