Hi Michael,
Michael Meeks schrieb:
Hi Regina,
On Mon, 2011-10-17 at 15:53 +0200, Regina Henschel wrote:
R=c:/git&& O=$R/LO35SEPT/solver/wntmsci12.pro&& W=
$R/LO35SEPT/workdir/wntmsci12.pro&& S=$R/LO35SEPT&& mkdir -p
$W/CppunitTest/&& (PATH="`cygpath -u $S/solver/wntmsci12.pro`/bin:
${PATH}" STAR_RESOURCEPATH=$O/bin/ $O/bin/cppunit/cppunittester.exe
$W/LinkTarget/CppunitTest/test_i18npool_test_breakiterator.dll
--protector unoexceptionprotector.dll unoexceptionprotector
"-env:UNO_TYPES= file:///$O/bin/udkapi.rdb file:///$O/bin/types.rdb"
"-env:UNO_SERVICES=file:///$O/xml/ure/services.rdb
file:///$W/RdbTarget/i18npool_test_breakiterator.rdb"
-env:URE_INTERNAL_LIB_DIR=file:///$O/bin
-env:OOO_BASE_DIR=file:///$O/bin -env:BRAND_BASE_DIR=file:///$O/bin
is the one to re-run, preferably inserting a debugger before the
cppunittester.exe - to see if we can find what went wrong, a stack trace
would be really helpful from wherever it fails there. Perhaps some in
some static instance destructor / atexit tear-down code.
I do not understand, what you expect me to do.
Ah - so the command I paste above (extracted from your log) should be
re-run under cygwin.
In theory if you paste the above line into your cygwin shell - you will
run just that one unit test, and it will fail for you. If that is the
case, then we need to run it under a debugger.
The command results in
OK(4)
Should I do what is advised in the error message:
cd C:/git/LO35SEPT
source ./Env.Host.sh
cd i18npool
/opt/lo/bin/make clean # optional
/opt/lo/bin/make -r
... re-run 'make' from the top-level
Kind regards
Regina
Context
- Re: [Libreoffice] make check fails in i18npool (continued)
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.