Re: [Libreoffice] Build fails in i18npool

Francois Tigeot <ftigeot -AT- wolfpond.org>
Sat, 5 Feb 2011 20:52:19 +0100

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.


Try a git pull in ure and try to build again. I think this should work
again now.


Thanks. I'm not sure if this was fixed by a git pull or some patching I did
in other modules but this works now indeed.

-- 
Francois Tigeot

Context

[Libreoffice] Build fails in i18npool · Francois Tigeot
- Re: [Libreoffice] Build fails in i18npool · Caolán McNamara
  - Re: [Libreoffice] Build fails in i18npool · Francois Tigeot
    - Re: [Libreoffice] Build fails in i18npool · Francois Tigeot
      - Re: [Libreoffice] [PATCH] Build fails in i18npool · Francois Tigeot
        
        Re: [Libreoffice] [PATCH] Build fails in i18npool · Francois Tigeot
        
        [Libreoffice] [PUSHED] Re: [PATCH] Build fails in i18npool · Caolán McNamara
        
        Re: [Libreoffice] [PUSHED] Re: [PATCH] Build fails in i18npool · Francois Tigeot
        Re: [Libreoffice] [PUSHED] Re: [PATCH] Build fails in i18npool · Francois Tigeot
        
        Re: [Libreoffice] [PUSHED] Re: [PATCH] Build fails in i18npool · Caolán McNamara
        Re: [Libreoffice] [PUSHED] Re: [PATCH] Build fails in i18npool · Francois Tigeot

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.