Date: prev next · Thread: first prev next last
2015 Archives by date, by thread · List index


I managed to get it to work. I just end up deleted everything and started
fresh.

Sorry for the inconvenience.

-Gio

On Sat, Feb 28, 2015 at 6:48 PM, Giovanni Caligaris <
giovannicaligaris@gmail.com> wrote:

Hello again,

I've tried just about everything.

I tried building from scratch again and unziping the Pootle files on the
'translations' folder before the build. That didn't work.
I tried make clean && make and that didn't work either.
I tried 'make translations' and it build one POT file but didn't make any
effect.
So far it only looks like my first build back when I was at 15% (on
pootle).

I am getting two errors but I'm not sure if it has anything to do with the
translation

I don't know what it could be.















*File tested,Execution Time
(ms)msobrightnesscontrast.docx,/home/test/core/sw/qa/extras/ooxmlimport/ooxmlimport.cxx:2213:testMsoBrightnessContrast::Importequality
assertion failed- Expected: 56374- Actual  : 74306File tested,Execution
Time
(ms)picture-with-schemecolor.docx,/home/test/core/sw/qa/extras/ooxmlimport/ooxmlimport.cxx:1989:testPictureWithSchemeColor::Importequality
assertion failed- Expected: �- Actual  : File tested,Execution Time
(ms)math-malformed_xml.docx,33*













*ooxmlimport.cxx:2213:AssertionTest name:
testMsoBrightnessContrast::Importequality assertion failed- Expected:
56374- Actual  : 74306ooxmlimport.cxx:1989:AssertionTest name:
testPictureWithSchemeColor::Importequality assertion failed- Expected: �-
Actual  : Failures !!!Run: 173   Failure total: 2   Failures: 2   Errors: 0*












*Error: a unit test failed, please do one of:export
DEBUGCPPUNIT=TRUE            # for exception catchingexport
CPPUNITTRACE="gdb --args"    # for interactive debugging on Linuxexport
VALGRIND=memcheck            # for memory checkingand retry using: make
CppunitTest_sw_ooxmlimport/home/test/core/solenv/gbuild/CppunitTest.mk:81:
recipe for target '/home/test/core/workdir/CppunitTest/sw_ooxmlimport.test'
failedmake[1]: ***
[/home/test/core/workdir/CppunitTest/sw_ooxmlimport.test] Error
1Makefile:243: recipe for target 'build' failedmake: *** [build] Error 2*




On Fri, Feb 27, 2015 at 7:50 AM, Andras Timar <timar74@gmail.com> wrote:

On Fri, Feb 27, 2015 at 11:06 AM, Giovanni Caligaris
<giovannicaligaris@gmail.com> wrote:
Sorry for the amateur questions, i'm not really a developer.

I just went back and ran

cd core
./autogen.sh with-lang=gug
make
(files already on translations folder)

But it didn't seem to do the trick.

I was wondering if you could guide me how to do it.


Maybe dependencies are not set correctly, I don't know... I've never
built LibreOffice like this myself. When you ran make, did you see
your language dependent targets (RES, XCU, UI, etc.) rebuilt? If it's
a dependency problem, then you can always 'make clean' things, and
then make again. Maybe it's an overkill to issue a toplevel make
clean, and rebuild everything from scratch. For example, if you want
to rebuild sw onyl, then 'make sw.clean && make sw' will do the trick.

Best regards,
Andras




-- 
To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be deleted

Context


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.