evoab2

Stephan Bergmann <sbergman -AT- redhat.com>
Tue, 06 Nov 2012 10:54:08 +0100

On 11/06/2012 09:20 AM, Lionel Elie Mamane wrote:

On Mon, Nov 05, 2012 at 10:38:16PM -0800, julien2412 wrote:

I gave a try to your patch. I applied it then "make connectivity", I got
this:

/home/julien/compile-libreoffice/libo/solenv/gbuild/ComponentTarget.mk:63:
*** gb_Deliver_deliver: file does not exist in solver, and cannot be
delivered:
/home/julien/compile-libreoffice/libo/solver/unxlngx6/xml/component/i18npool/util/i18npool.component.


That's yet another error, not sure where it comes from. Try "make i18npool".


"make connectivity.all" should have prevented that

Context

Building failure in connectivity/source/drivers/evoab2 · julien2412
- Re: Building failure in connectivity/source/drivers/evoab2 · Lionel Elie Mamane
  - Re: Building failure in connectivity/source/drivers/evoab2 · Lionel Elie Mamane
    - Re: Building failure in connectivity/source/drivers/evoab2 · Stephan Bergmann
  - Re: Building failure in connectivity/source/drivers/evoab2 · julien2412
    - Re: Building failure in connectivity/source/drivers/evoab2 · Lionel Elie Mamane
      - Re: Building failure in connectivity/source/drivers/evoab2 · Stephan Bergmann
      - Re: Building failure in connectivity/source/drivers/evoab2 · Stephan Bergmann
        
        Re: Building failure in connectivity/source/drivers/evoab2 · julien2412
        
        Re: Building failure in connectivity/source/drivers/evoab2 · Caolán McNamara

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.