Re: [Libreoffice] Build issue with cppu

"surenspost -AT- gmail.com" <surenspost -AT- gmail.com>
Tue, 25 Jan 2011 11:17:26 +0530

Hi Dave,

On Tue, Jan 25, 2011 at 10:42 AM, David Dumaresq <dfdumaresq@gmail.com> wrote:



I suggest you take a look at the advice under The Build Failed... What can I do? here, 
http://wiki.documentfoundation.org/Development/Native_Build

Dave


I already did that and have pasted the output of the individual
rebuild of the module above :) I tried quite a few times with the
individual build. It seems like the build is going through fine, but
the unit tests failing. I didn't know what to do from there.

-- 
regards
Suren
Learning < Doing
Learn By doing.

Context

[Libreoffice] Build issue with cppu · surenspost -AT- gmail.com
- Re: [Libreoffice] Build issue with cppu · David Dumaresq
  - Re: [Libreoffice] Build issue with cppu · surenspost -AT- gmail.com
    - Re: [Libreoffice] Build issue with cppu · Jonathan Aquilina
    - Re: [Libreoffice] Build issue with cppu · David Tardon
      - Re: [Libreoffice] Build issue with cppu · Michael Meeks
      - Re: [Libreoffice] Build issue with cppu · Surendran Mahendran
        
        Re: [Libreoffice] Build issue with cppu · Caolán McNamara
        
        Re: [Libreoffice] Build issue with cppu · Surendran Mahendran
        
        Re: [Libreoffice] Build issue with cppu · Caolán McNamara
        Re: [Libreoffice] Build issue with cppu · surenspost -AT- gmail.com

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.