openoffice-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Patricia Shanahan <p...@acm.org>
Subject Re: Build without doing any tests?
Date Sun, 13 Mar 2016 17:49:39 GMT
It looks as though the attached .pdf image did not get through. Here is 
the data from it:

The error was in main/sal/osl/w32/process.cxx, line 340, null message. 
The assertion is "OSL_ASSERT(g_command_args.m_nCount > 0);"

On 3/13/2016 10:44 AM, Patricia Shanahan wrote:
> Hi Damjan,
>
> I got another one. This is a cygwin build on Windows 8.1.
>
> I'll leave it alone for a bit in case there is more information I should
> capture. It may be possible to attach a debugger to the process.
>
> Here are the last few lines from the build output:
>
>     Creating library
> c:/OpenOfficeDev/Trunk/main/solver/420/wntmsci12/workdir/LinkTarget/Library/ivbaswobj.lib
> and object
> c:/OpenOfficeDev/Trunk/main/solver/420/wntmsci12/workdir/LinkTarget/Library/ivbaswobj.exp
>
> [ build CMP ] sw/util/vbaswobj
> [ build PKG ] sw_misc
> [ build PKG ] sw_uiconfig
> [ build PKG ] sw_xml
> [ build MOD ] sw
> [ build ALL ] top level modules: sw
> [ build ALL ] loaded modules: sw
> [ build CXX ] sw/qa/core/Test-BigPtrArray
> Test-BigPtrArray.cxx
> c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(86) :
> warning C4100: 'bparr' : unreferenced formal parameter
> c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(98) :
> warning C4018: '<' : signed/unsigned mismatch
> c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(102) :
> warning C4100: 'name' : unreferenced formal parameter
> c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(111) :
> warning C4018: '<' : signed/unsigned mismatch
> c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(113) :
> warning C4389: '!=' : signed/unsigned mismatch
> c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(121) :
> warning C4018: '<' : signed/unsigned mismatch
> c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(222) :
> warning C4389: '==' : signed/unsigned mismatch
> c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(224) :
> warning C4018: '<' : signed/unsigned mismatch
> c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(275) :
> warning C4018: '<' : signed/unsigned mismatch
> c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(305) :
> warning C4018: '<' : signed/unsigned mismatch
> c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(337) :
> warning C4018: '<' : signed/unsigned mismatch
> c:/OpenOfficeDev/Trunk/main/sw/qa/core/Test-BigPtrArray.cxx(363) :
> warning C4018: '<' : signed/unsigned mismatch
> [ build LNK ] GoogleTest/sw_bigpointerarray.exe
> Microsoft (R) Incremental Linker Version 9.00.30729.01
> Copyright (C) Microsoft Corporation.  All rights reserved.
>
> c:/OpenOfficeDev/Trunk/main/solver/420/wntmsci12/workdir/CxxObject/sw/qa/core/Test-BigPtrArray.o
>
> [ build CUT ] sw_bigpointerarray
>
>
> On 3/13/2016 10:01 AM, Damjan Jovanovic wrote:
>> It is highly unusual to get a dialog during build. Please send a
>> screenshot next time.
>>
>> "./configure --help" is probably the best - I couldn't find anything
>> better so far.
>>
>>
>> On Sun, Mar 13, 2016 at 6:19 PM, Patricia Shanahan <pats@acm.org> wrote:
>>> I also have no idea which tests - I just know I was greeted this
>>> morning by
>>> an incomplete build and the form of AOO dialog I only see from a debug
>>> build. The build resumed as soon as I answered the dialog.
>>>
>>> I'll try --disable-unit-tests next time I start a build.
>>>
>>> Is there a general document describing all the AOO configure
>>> parameters? If
>>> so, I should read it.
>>>
>>> Thanks,
>>>
>>> Patricia
>>>
>>>
>>> On 3/13/2016 9:11 AM, Damjan Jovanovic wrote:
>>>>
>>>> I am not sure which tests you are talking about and at what stage of
>>>> the build process they occur. The Google Test unit tests don't bring
>>>> up dialogs AFAIK, but can be disabled by passing --disable-unit-tests
>>>> to ./configure. If this happens after starting AOO then see
>>>> https://wiki.openoffice.org/wiki/Non_Product_Build - in brief
>>>> Alt+Shift+Ctrl+D, set "Error" to something other than "MessageBox",
>>>> "OK", exit AOO, back up the .dbgsv.ini somewhere, and from then on
>>>> start AOO with the environment variable DBGSV_INIT set to the path of
>>>> that .dbgsv.ini you backed up.
>>>>
>>>> On Sun, Mar 13, 2016 at 4:57 PM, Patricia Shanahan <pats@acm.org>
>>>> wrote:
>>>>>
>>>>> I am currently building a debug version of AOO, including using
>>>>> --enable-dbgutil. I lost a few hours overnight because it did a
>>>>> test that
>>>>> triggered an assertion dialog, and waited for me to wake up and click
>>>>> "No"
>>>>> to continue.
>>>>>
>>>>> I would prefer to separate building and the tests that are normally
>>>>> done
>>>>> during "build --all", so that I can build while I am away from the
>>>>> computer
>>>>> and test while I'm there to respond to any dialogs.
>>>>>
>>>>> Patricia
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org


Mime
View raw message