Re: Unit Tests failing when built with clang 12

[slacka]

I just did a git pull and UITest_calc_tests9 is passing on master. I'm
bisecting the fix now. 



--
Sent from: 
http://document-foundation-mail-archive.969070.n3.nabble.com/Dev-f1639786.html
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Unit Tests failing when built with clang 12

[slacka]

Yes, I just verified that you'll need an --enable-optimized build to
reproduce this failure. When I built with clang 12 + --enable-debug, all
unit tests passed. 



--
Sent from: 
http://document-foundation-mail-archive.969070.n3.nabble.com/Dev-f1639786.html
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Missing _sysconfigdata_m_linux_i686-linux-gnu.py

[slacka]

Does the master branch build under the same configuration? I do not see this
or any issue building i686 master under Arch Linux 32 or Cent OS 7.  



--
Sent from: 
http://document-foundation-mail-archive.969070.n3.nabble.com/Dev-f1639786.html
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

[Libreoffice-commits] core.git: sw/qa

[slacka (via logerrit)]

 sw/qa/extras/layout/layout.cxx |   20 ++--
 1 file changed, 14 insertions(+), 6 deletions(-)

New commits:
commit 85b29e0be7bbade080c2978aef598839a89cfd3e
Author: slacka 
AuthorDate: Thu Dec 26 21:14:36 2019 -0500
Commit: Noel Grandin 
CommitDate: Fri Dec 27 13:26:50 2019 +0100

Fix 32-bit gcc Unit Test Failures

This relaxes the tests to work around a precision error with gcc7-9.
No issue with 32-bit clang.

Change-Id: I0222bc91243e461408b4e611953355492975ff4d
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/85857
Tested-by: Jenkins
Reviewed-by: Noel Grandin 

diff --git a/sw/qa/extras/layout/layout.cxx b/sw/qa/extras/layout/layout.cxx
index 5274bef2b8a0..8825d2e77513 100644
--- a/sw/qa/extras/layout/layout.cxx
+++ b/sw/qa/extras/layout/layout.cxx
@@ -2379,11 +2379,16 @@ CPPUNIT_TEST_FIXTURE(SwLayoutWriter, testTdf126244)
 assertXPath(pXmlDoc, 
"/metafile/push[1]/push[1]/push[1]/push[4]/push[1]/font[1]", "orientation",
 "0");
 // Test the second level of vertical category axis labels orientation. The 
second level orientation should be vertical.
-assertXPath(pXmlDoc, 
"/metafile/push[1]/push[1]/push[1]/push[4]/push[1]/font[5]", "orientation",
-"900");
+sal_Int32 nRotation
+= getXPath(pXmlDoc, 
"/metafile/push[1]/push[1]/push[1]/push[4]/push[1]/font[5]",
+   "orientation")
+  .toInt32();
+CPPUNIT_ASSERT(nRotation >= 899 && nRotation <= 900);
 // Test the third level of vertical category axis labels orientation. The 
third level orientation should be vertical.
-assertXPath(pXmlDoc, 
"/metafile/push[1]/push[1]/push[1]/push[4]/push[1]/font[7]", "orientation",
-"900");
+nRotation = getXPath(pXmlDoc, 
"/metafile/push[1]/push[1]/push[1]/push[4]/push[1]/font[7]",
+ "orientation")
+.toInt32();
+CPPUNIT_ASSERT(nRotation >= 899 && nRotation <= 900);
 }
 
 CPPUNIT_TEST_FIXTURE(SwLayoutWriter, testTdf127304)
@@ -2397,8 +2402,11 @@ CPPUNIT_TEST_FIXTURE(SwLayoutWriter, testTdf127304)
 xmlDocPtr pXmlDoc = dumpAndParse(dumper, *xMetaFile);
 CPPUNIT_ASSERT(pXmlDoc);
 // Test the first level of horizontal category axis labels orientation. 
The first level orientation should be vertical.
-assertXPath(pXmlDoc, 
"/metafile/push[1]/push[1]/push[1]/push[3]/push[1]/font[1]", "orientation",
-"900");
+sal_Int32 nRotation
+= getXPath(pXmlDoc, 
"/metafile/push[1]/push[1]/push[1]/push[3]/push[1]/font[1]",
+   "orientation")
+  .toInt32();
+CPPUNIT_ASSERT(nRotation >= 899 && nRotation <= 900);
 // Test the second level of horizontal category axis labels orientation. 
The second level orientation should be horizontal.
 assertXPath(pXmlDoc, 
"/metafile/push[1]/push[1]/push[1]/push[3]/push[1]/font[5]", "orientation",
 "0");
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits

Re: [ABANDONED] Re: Build fail on Libgpg-error on Windows with gawk 5.0

[slacka]

We are still using libgpg-error v1.27 but the latest version on their
download page is 1.36. Can we update this tarball so that new LODE installs
can work again? 

https://gnupg.org/download/index.html#libgpg-error




--
Sent from: 
http://document-foundation-mail-archive.969070.n3.nabble.com/Dev-f1639786.html
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: [TDF infra] Announcing Gitiles VCS browser (gitweb replacement) and https:// anon git URIs

[slacka]

Thanks Guilhem! I like the look of gitiles, but they both need better
integration. Could you add hyperlinks to referenced commit messages and to
bugzilla?

cgit:
https://cgit.freedesktop.org/libreoffice/core/commit/?id=048b8e45813f6a19a4ff56e1d676fe9450325cd2
gitiles:
https://gerrit.libreoffice.org/plugins/gitiles/core/+/048b8e45813f6a19a4ff56e1d676fe9450325cd2
gitweb:https://gerrit.libreoffice.org/gitweb?p=core.git;a=commit;h=048b8e45813f6a19a4ff56e1d676fe9450325cd2

Note how gitiles is missing both and gitweb does not link to the bug
tracker. 



--
Sent from: 
http://document-foundation-mail-archive.969070.n3.nabble.com/Dev-f1639786.html
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Cppcheck: Reduction of False Positives: Manual Approach

[slacka]

The goal of my manual approach was to configure Cppcheck to minimize false
positives. In doing so, I was forced to only scan the Linux code base, as
only Linux has Linux system headers and does not have Window's or BSD's...
So I am not surprised that some valid issues were not reported. 

There are many knobs I could tweak. For example, since my last post, I
discovered I could remove the "-DNDEBUG" to scan the debug code path. I
could also remove the "-j 4" option to allow Cppcheck to scan for unused
functions.  I don't know what is most useful, and what valid issues were not
being reported.  This is why I have asked the ML for feedback. 

So if a dev wants give me some guidance, I could continue tweaking, or as
you suggested, we could run 2 reports. 
1) a limited Linux only scan with few false positives (ala my manual
approach), and 
2) a general scan with many false positives (the current Cppcheck Report).  

If you try to limit the false positives with include locations without also
limiting configuration, Cppcheck gets overloaded and generates tens of
thousands of "too many configuration" errors. 



--
Sent from: 
http://document-foundation-mail-archive.969070.n3.nabble.com/Dev-f1639786.html
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: can't build libreoffice !

[slacka]

After I move the source folder around, I run a `./autogen.sh`to clean
everything up so commands like 'make clean' work again.



--
Sent from: 
http://document-foundation-mail-archive.969070.n3.nabble.com/Dev-f1639786.html
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: make check always fail

[slacka]

Rahul,
Please take a few minutes  to include the relevant details before emailing
several hundred recipients a list like this. Telling us your 'make check'
fails without a single detail on the error message or your build environment
just wastes everyone's time including yours. 

Here is what a good report looks like: 

http://document-foundation-mail-archive.969070.n3.nabble.com/JunitTest-forms-unoapi-tests-now-failing-on-Windows-td4247132.html

Note that it includes both the failing test(s) along with build parameters.
On the flip side, if you feel you have too much information, you can use a
service like pastebin for your failing make logs. 



--
Sent from: 
http://document-foundation-mail-archive.969070.n3.nabble.com/Dev-f1639786.html
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Windows Debug builds failure: 'DbgGUIInitSolarMutexCheck': identifier not found

[slacka]

Sorry I was in the wrong folder: this is the correct one

Microsoft (R) C/C++ Optimizing Compiler Version 19.14.26433 for x64
Copyright (C) Microsoft Corporation.  All rights reserved.



--
Sent from: 
http://document-foundation-mail-archive.969070.n3.nabble.com/Dev-f1639786.html
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Windows Debug builds failure: 'DbgGUIInitSolarMutexCheck': identifier not found

[slacka]

Here is my build environment: 

$ cat autogen.input
--enable-debug

$ cl /?
Microsoft (R) C/C++ Optimizing Compiler Version 17.00.60610.1 for x86

Do you need anything else? I'll try reverting Noel's patches to check if
that is the cause or not.









--
Sent from: 
http://document-foundation-mail-archive.969070.n3.nabble.com/Dev-f1639786.html
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Windows Debug builds failure: 'DbgGUIInitSolarMutexCheck': identifier not found

[slacka]

Here is my build environment: 

$ cat autogen.input
--enable-debug

$ cl /?
Microsoft (R) C/C++ Optimizing Compiler Version 17.00.60610.1 for x86

Do you need anything else?



--
Sent from: 
http://document-foundation-mail-archive.969070.n3.nabble.com/Dev-f1639786.html
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Segmentation fault when compiling

[slacka]

This is not an issue specific to his environment. I'm also seeing the same
seg fault on a clean Windows 32-bit debug build. 

$ cat autogen.input
--enable-debug

After a 
$ make clean && git pull && ./autogen.sh && make check

I'm seeing: 
[build CUT] vcl_lifecycle
[build SLC] drawinglayer
[build DEP] LNK:CppunitTest/test_framework_dispatch.dll
[build LNK] CppunitTest/test_framework_dispatch.dll
   Creating library
C:/core/workdir/LinkTarget/CppunitTest/itest_framework_dispatch.lib and
object C:/core/workdir/LinkTarget/CppunitTest/itest_framework_dispatch.exp
[build LNK] Library/graphicfilterlo.dll
/usr/bin/sh: line 1:  6360 Segmentation fault  (
PATH="C:\core\instdir\program;C:\core\instdir\program;C:\core\workdir\LinkTarget\Library;C:\core\workdir\UnpackedTarball\cppunit\src\cppunit\ReleaseDll;$PATH"
$W/LinkTarget/Executable/cppunittester.exe
$W/LinkTarget/CppunitTest/test_vcl_lifecycle.dll --headless
"-env:BRAND_BASE_DIR=file:///$S/instdir" "-env:BRAND_SHARE_SUBDIR=share"
"-env:BRAND_SHARE_RESOURCE_SUBDIR=program/resource"
"-env:UserInstallation=file:///$W/CppunitTest/vcl_lifecycle.test.user"
"-env:CONFIGURATION_LAYERS=xcsxcu:file:///$I/share/registry
xcsxcu:file:///$W/unittest/registry"
"-env:UNO_TYPES=file:///$I/program/types.rdb
file:///$I/program/types/offapi.rdb"
"-env:UNO_SERVICES=file:///$W/Rdb/ure/services.rdb
file:///$W/ComponentTarget/configmgr/source/configmgr.component
file:///$W/ComponentTarget/i18npool/util/i18npool.component
file:///$W/ComponentTarget/ucb/source/core/ucb1.component
file:///$W/ComponentTarget/ucb/source/ucp/file/ucpfile1.component
file:///$W/ComponentTarget/framework/util/fwk.component
file:///$W/ComponentTarget/sfx2/util/sfx.component"
-env:URE_INTERNAL_LIB_DIR=file:///$I/program
-env:LO_LIB_DIR=file:///$I/program
-env:LO_JAVA_DIR=file:///$I/program/classes --protector
$W/LinkTarget/Library/unoexceptionprotector.dll unoexceptionprotector
--protector $W/LinkTarget/Library/unobootstrapprotector.dll
unobootstrapprotector --protector
$W/LinkTarget/Library/vclbootstrapprotector.dll vclbootstrapprotector
"-env:CPPUNITTESTTARGET=$W/CppunitTest/vcl_lifecycle.test" ) >
$W/CppunitTest/vcl_lifecycle.test.log 2>&1
warn:vcl.window:18848:3412:vcl/source/window/window.cxx:946:
Window::Window(): pParent == NULL
warn:vcl.opengl:18848:3412:vcl/opengl/win/WinDeviceInfo.cxx:506: use :
warn:vcl.fonts:18848:3412:vcl/win/gdi/salfont.cxx:1300:
WinSalGraphics::GetDevFontList(): enter
LifecycleTest::testPostDispose finished in: 2ms
LifecycleTest::testFocus finished in: 2ms
LifecycleTest::testLeakage finished in: 1544ms
LifecycleTest::testToolkit finished in: 2ms
OK (10)
warn:fwk.desktop:18848:3412:framework/source/services/desktop.cxx:1069:
Desktop disposed before terminating it
warn:fwk.desktop:18848:3412:framework/source/services/desktop.cxx:191:
Desktop not terminated before being destructed

Error: a unit test failed, please do one of:
make CppunitTest_vcl_lifecycle CPPUNITTRACE=TRUE # which is a shortcut for
the following line
make CppunitTest_vcl_lifecycle CPPUNITTRACE="'C:/Program Files
(x86)/Microsoft Visual Studio/2017/Community/Common7/IDE/devenv.exe'
/debugexe" # for interactive debugging in Visual Studio
make CppunitTest_vcl_lifecycle CPPUNITTRACE="drmemory -free_max_frames 20" #
for memory checking (install Dr.Memory first, and put it to your PATH)

You can limit the execution to just one particular test by:

make CppunitTest_vcl_lifecycle CPPUNIT_TEST_NAME="testXYZ" ...above
mentioned params...

C:/core/solenv/gbuild/CppunitTest.mk:116: recipe for target
'C:/core/workdir/CppunitTest/vcl_lifecycle.test' failed
make[1]: *** [C:/core/workdir/CppunitTest/vcl_lifecycle.test] Error 1
make[1]: *** Waiting for unfinished jobs
   Creating library C:/core/workdir/LinkTarget/Library/iavmedia.lib and
object C:/core/workdir/LinkTarget/Library/iavmedia.exp
   Creating library C:/core/workdir/LinkTarget/Library/idbp.lib and object
C:/core/workdir/LinkTarget/Library/idbp.exp
   Creating library C:/core/workdir/LinkTarget/Library/ixo.lib and object
C:/core/workdir/LinkTarget/Library/ixo.exp
Makefile:286: recipe for target 'build' failed
make: *** [build] Error 2




--
Sent from: 
http://document-foundation-mail-archive.969070.n3.nabble.com/Dev-f1639786.html
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Compiler baselines

[slacka]

devtoolset-7 for i386 is over here:

https://copr-be.cloud.fedoraproject.org/results/mlampe/devtoolset-7/epel-6-i386/00756569-devtoolset-7/

Is that what you're looking for?



--
Sent from: 
http://document-foundation-mail-archive.969070.n3.nabble.com/Dev-f1639786.html
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Compiler baselines

[slacka]

While it's true there is no 32-bit RHEL 7, CentOS 7 has had a 32-bit release
since 2015. You can download it from here: 
http://mirror.centos.org/altarch/7/isos/i386/

More details can be found here:
https://wiki.centos.org/SpecialInterestGroup/AltArch/i386





--
Sent from: 
http://document-foundation-mail-archive.969070.n3.nabble.com/Dev-f1639786.html
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Question, please

[slacka]

As of a few weeks ago, LODE was working. You just have to be careful to
follow every step carefully.

You might find some helpful developers on IRC or you can try to fix it
yourself. 

Assuming you are in the lode/dev/core folder, if that make command is
failing, you likely missed one of the setup steps. I'd start by repeating
the steps starting with: "./setup --help" when you are in ~/lode

If that wasn't it, maybe you clone failed. You can verify the status with a
"git pull" and a "git status". 

If that fails, then I'd remove "C:\cygwin" directory and repeat the steps in
the wiki from ".\install_cygwin.ps1" in MS PowerShell. 

Just be sure to read the results of each command and following the
associated instructions on the wiki and it will work. 



--
Sent from: 
http://document-foundation-mail-archive.969070.n3.nabble.com/Dev-f1639786.html
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: CppunitTest_sc_tabviewobj failing on Windows MSVC 2017

[slacka]

Tested on another totally different system with MSVC 2015. Same failure as
reported in my original post with ScTabViewObj::testGetReferredCells. 

I would be surprised if this works on any windows system. Should this be
disabled for windows or does someone want to take a look at it? 



--
Sent from: 
http://document-foundation-mail-archive.969070.n3.nabble.com/Dev-f1639786.html
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: CppunitTest_sc_tabviewobj failing on Windows MSVC 2017

[slacka]

Jens,
Could you be a bit more specific? What debug info would you like me to
gather? 

-Luke



--
Sent from: 
http://document-foundation-mail-archive.969070.n3.nabble.com/Dev-f1639786.html
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: CppunitTest_sc_tabviewobj failing on Windows MSVC 2017

[slacka]

Sorry for the noise. We can talk about the OpenCL issue caused by the same
commit  in another thread. 

Re: the original issue, when I only run:

$ make CppunitTest_sc_tabviewobj

On my Broadwell MSVC 2015  system, it fails with the same error as I
reported originally seen MSVC 2017 Sandybridge system. 
 
error : Assertion Test name: sc_apitest::ScTabViewObj::testGetReferredCells
equality assertion failed
- Expected: Sheet: 0 StartColumn: 0 StartRow: 0 EndColumn: 6 EndRow: 14
- Actual  : Sheet: 0 StartColumn: 0 StartRow: 0 EndColumn: 6 EndRow: 23

Would you like any debug information?



--
Sent from: 
http://document-foundation-mail-archive.969070.n3.nabble.com/Dev-f1639786.html
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Subsequent Test PythonTest_dbaccess_python stuck in Infinite Loop

[slacka]

I can confirm that the build failure was caused by 
https://cgit.freedesktop.org/libreoffice/core/commit/?id=1c5c9b84 

Refactor: migration warn dlg without modifying API

and that Mike Kaganski's commit does resolve the issue.




--
Sent from: http://nabble.documentfoundation.org/Dev-f1639786.html
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: PythonTest_pyuno_pytests_insertremovecells Unit Test Failing on Windows

[slacka]

With
https://cgit.freedesktop.org/libreoffice/core/commit/?id=e21b2a61d64b697413c0fc9013746b9d358da4c6

and
https://cgit.freedesktop.org/libreoffice/core/commit/?id=04f4702eb896a330bc3b10443b7303a1d07d7a11

Windows 'make check' builds now succeed again.

Thanks Stephan! 



--
Sent from: http://nabble.documentfoundation.org/Dev-f1639786.html
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: vclplug_gtk - vclplug_gtk3

[slacka]

Assuming you are a developer and are trying to fix this issue yourself, I
suggest you start  by filing a bug report.
   Be
sure to include your bug doc and system configuration so that others can
reproduce this issue. 



--
Sent from: http://nabble.documentfoundation.org/Dev-f1639786.html
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: UITest_writerperfect_epubexport hang (only sometimes)

[slacka]

I experienced this hang today in UITest_writerperfect_epubexport on a clean
build. A subsequent clean build on the same revision  succeeded.  This
appears to be a intermittent issue.



--
Sent from: http://nabble.documentfoundation.org/Dev-f1639786.html
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Unit test PythonTest_solenv_python failing on Linux on est_gbuildtojson

[slacka]

If you are getting this failure, you have to manually

$ rm xmlsecurity/qa/unit/signing/data/S.gpg-agent

Neither a  "make clean" nor a "git clean -fdx" will remove this file. After
that plus Thorsten's fix, "make check" now successfulness runs on Linux. 


Thanks Thorsten





--
Sent from: http://nabble.documentfoundation.org/Dev-f1639786.html
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Unit test PythonTest_solenv_python failing on Linux on est_gbuildtojson

[slacka]

I'm still getting the same failure and same  "[Errno 6] No such device or
address: '/core/xmlsecurity/qa/unit/signing/data/S.gpg-agent'")]

Was this a blind fix? If so, you need anything else from me?



--
Sent from: http://nabble.documentfoundation.org/Dev-f1639786.html
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: CppunitTest_dbaccess_hsqldb_test / CppunitTest_dbaccess_RowSetClones Failing after System Update

[slacka]

Thank you Jan-Marek Glogowski. The workaround:

kernel parameter stack_guard_gap=1

resolved the issue and the build successfully completed. This issue was also
reported in our bug tracker here:

https://bugs.documentfoundation.org/show_bug.cgi?id=108619



--
View this message in context: 
http://nabble.documentfoundation.org/CppunitTest-dbaccess-hsqldb-test-CppunitTest-dbaccess-RowSetClones-Failing-after-System-Update-tp4218769p4218835.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Link error: undefined reference to `__mulodi4' with Clang 32-bit

[slacka]

I build with x86 because my home laptop is a Dell Precision M90 Core Duo
T2700 which is a 32-bit CPU. This machine has a gorgeous 16:10 display which
is hard to find these days. The other machine is just a 32-bit image on a VM
that I spool up to verify bugs.  It does have the added benefit of less
memory usage than its x86-64 bit counterpart. 


Up until these recent 2 regressions (jpeg-turbo and mulodi4) , I've been
building 32-bit builds with Clang for the past couple of years.




--
View this message in context: 
http://nabble.documentfoundation.org/Link-error-undefined-reference-to-mulodi4-with-Clang-32-bit-tp4213636p4213759.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Link error: undefined reference to `__mulodi4' with Clang 32-bit

[slacka]

> Whatever the trouble with your toolchain 

If you have access to a Fedora x86 box with Clang, I'm sure you'd see this
too as I'm seeing this on both my 32-bit Fedora box with Clang 5.0 master
and 32-bit Ubuntu box with clang 3.9. 

> tweak the  #elif so that you use the #else fallback implementation

So you don't think  this sound like a compiler issue? Anything else you
suggest I try or look into before working on a patch for this?




--
View this message in context: 
http://nabble.documentfoundation.org/Link-error-undefined-reference-to-mulodi4-with-Clang-32-bit-tp4213636p4213680.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Clang 5.0 32-bit builds Failing on CppunitTest_vcl_pdfexport

[slacka]

>  SIGABRT failure of
CppunitTest_vcl_filters_test only happen on one of those "2 different
machines(Ubuntu/Fedora)" or on both? 

To Answer your other 2 Questions. It's failing on my Fedora box with Clang
5.0 master. It's failing on my Ubuntu box with clang 3.9 release. Both are
x86.

> * Which jpeg library is that, system one or external/jpeg-turbo? 

How do I check this? See my previous post for my 'autogen.input'.



--
View this message in context: 
http://nabble.documentfoundation.org/MSVC-2015-s-broken-static-initializer-list-causing-build-failure-tp4202928p4213632.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Build error: 'GetMap' is a protected member of 'SwAccessibleContext'

[slacka]

That commit fixed the error. I just finished a successful build with Clang.

Thanks Markus!



--
View this message in context: 
http://nabble.documentfoundation.org/Build-error-GetMap-is-a-protected-member-of-SwAccessibleContext-tp4213098p4213122.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Clang 5.0 32-bit builds Failing on CppunitTest_vcl_pdfexport

[slacka]

I think my initial bisect was wrong because I didn't do a "make clean"
between all the builds. Reverting
https://cgit.freedesktop.org/libreoffice/core/commit/?id=6889fa826eef6bd1074d77507818e71dfe8ba152
Caused a failing build to pass, so it looks like Michael Stahl's hunch was
correct.


$ cat autogen.input 
--without-export-validation
CC=clang
CXX=clang++


and --enable-debug for recent debug builds


The build command I'm using is  
$ ./autogen.sh && make ENVCFLAGS="-mllvm -no-x86-call-frame-opt"
ENVCFLAGSCXX="-mllvm -no-x86-call-frame-opt" 2>&1 | tee build2.log

The flags are because of  this issue.
  





--
View this message in context: 
http://nabble.documentfoundation.org/MSVC-2015-s-broken-static-initializer-list-causing-build-failure-tp4202928p4212415.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Clang 5.0 32-bit builds Failing on CppunitTest_vcl_pdfexport

[slacka]

Here is the backtrace:

https://pastebin.com/vhYRQDSG

This was with  clang version 4.0.0 (trunk 287326)

On Ubuntu 16.04.2 LTS 3 4.4.0-64-generic #85-Ubuntu SMP Mon Feb 20 11:49:39
UTC 2017 i686 i686 i686 

I'm not sure if it was timing, ccache. or what but whatever is causing this
crash started about 1 month ago. I have been building Libreoffice with Clang
for years and I'm seeing this on 2 different machines(Ubuntu/Fedora).



--
View this message in context: 
http://nabble.documentfoundation.org/MSVC-2015-s-broken-static-initializer-list-causing-build-failure-tp4202928p4212319.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Possible bug in libreoffice online

[slacka]

Aditya Dewan,

This list is more for coding-level discussion, not bug reports. To file a
bug report, please follow the instructions on our wiki:

https://wiki.documentfoundation.org/QA/BugReport



--
View this message in context: 
http://nabble.documentfoundation.org/Possible-bug-in-libreoffice-online-tp4210294p4210298.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Post-Build Limited Functionality

[slacka]

'libreoffice-common is needed for your distro's version of libreoffice. And
your symptoms sound like a corrupt user profile.

Are you running your distro's,  soffice? or the one you just built,
./instdir/program/soffice ? 

If you are running the version you just built, i'd try making a clean copy.

$ make clean && git pull && ./autogen.sh && make 



--
View this message in context: 
http://nabble.documentfoundation.org/Post-Build-Limited-Functionality-tp4209039p4209046.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: MSVC 2015 Error C2664

[slacka]

sberg wrote
> fixed with 
> ;
>  
> "Blind fix for MSVC 2015 error C2664"

Yes that did the trick, and with Markus's commit:
https://cgit.freedesktop.org/libreoffice/core/commit/?id=73f2944618e637762125fabd214b09b4fa50fb90
Revert "convert spell menu to .ui

I can now build successfully on MSVC 2015. 

Thanks Stephan and Markus!



--
View this message in context: 
http://nabble.documentfoundation.org/MSVC-2015-s-broken-static-initializer-list-causing-build-failure-tp4202928p4208948.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: MSVC 2015 builds Failing After 2017 Support added

[slacka]

Thanks for the work-around, but that doesn't really answer my question. 

To clarify, before support for MSVC 2017 was added, I did not need the Win
10 SDK. Even after, I do not need the Win 10 SDK to build with MSVC 2013.
Only MSVC 2015 has this new requirement.

Was this change intentional? If so, I'll update the wiki documentation to
mention this.



--
View this message in context: 
http://nabble.documentfoundation.org/MSVC-2015-s-broken-static-initializer-list-causing-build-failure-tp4202928p4208349.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: minutes of ESC call ...

[slacka]

VS 2015 has much better support for Support For C++11/14 Features

https://msdn.microsoft.com/en-us/library/hh567368.aspx

When VS 2013 is depreciated, we can probably remove some ugly  IFDEFs. 

I really hope that hour search was a bad joke. Google "Download VS 2013" and
the first link is the download link for the installer. When I was bisecting
some old regressions, I had no issues finding or downloading VS 2012 either. 



--
View this message in context: 
http://nabble.documentfoundation.org/minutes-of-ESC-call-tp4208111p4208180.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Does anyone use windows

[slacka]

That is not what the wiki says. It says "Visual Studio 2013 is the preferred
compiler for new developers." It also goes on to say "Visual Studio 2015 is
known to work on current master."  If you are a new developer, I suggest you
follow the wiki's advice. The wiki contains everything you need to get
started and is full of useful tips. I suggest you try to read it before
asking for more help.



--
View this message in context: 
http://nabble.documentfoundation.org/Does-anyone-use-windows-tp4208152p4208156.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: system-wide location for dictionary files and dictionary file name format

[slacka]

To answer your first and third question, we use hunspell not myspell. For the
spellcheck function to work, LibreOffice requires both the main hunspell
package along with a language dictionary (hunspell-en for English,
hunspell-de for German, etc). For a package maintainer, your main concern
should be that the language dictionary associated with the user’s locales is
installed.  



--
View this message in context: 
http://nabble.documentfoundation.org/system-wide-location-for-dictionary-files-and-dictionary-file-name-format-tp4207770p4207781.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: helpful stuff

[slacka]

How are spammers getting malicious messages like this on the list. It's
showing up in both our Archive and Nabble. 

There seems to be a moderations system that blocks non-subscribers. Do we
need more mods or just stricter controls to make it harder to circumvent. If
you need more mods, who should I approach?



--
View this message in context: 
http://nabble.documentfoundation.org/helpful-stuff-tp4206152p4206154.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: build breaks in embeddedobj/source/msole/olemisc.cxx

[slacka]

I saw that same exact failure earlier today. I did a 
$ make clean && git pull && ./autogen.sh && make

And now had a successful build of commit
e15fd1371567fd4b78dab37d843562ff676c52b8

I guess that build error was fixed by: 

https://cgit.freedesktop.org/libreoffice/core/commit/?id=4b429851e54ccc42e5f9acebce67139bc3d5e244



--
View this message in context: 
http://nabble.documentfoundation.org/build-breaks-in-embeddedobj-source-msole-olemisc-cxx-tp4205783p4205824.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: export-validation in tests by default causing 32 bit Ubuntu to crash

[slacka]

This appears to be an OpenJDK 1.8 bug that was fixed in 1.8.0_112. At least
with 32-bit Arch, 1.8 can now pass all the Unit Tests without the need for
"--without-export-validation".


Java version "1.7.0_111" : GOOD 
OpenJDK Runtime Environment (build 1.8.0_91-8u91-b14-3ubuntu1~16.04.1-b14):
SdImportTest::testDocumentLayout test FAIL
openjdk version "1.8.0_111": SdImportTest::testDocumentLayout test FAIL
openjdk version "1.8.0_112": Good










--
View this message in context: 
http://nabble.documentfoundation.org/export-validation-in-tests-by-default-causing-32-bit-Ubuntu-to-crash-tp4192925p4204186.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Need help for building

[slacka]

clean everything up with  
$ git checkout master
$ git clean -fdx
$ git reset --hard origin/master
$ git pull

then make everything is sync'd with master
$ git status

If that doesn't do it, 
Try paring down your ./autogen.input. I'm having no issues with a simpler
version on VS2013



--
View this message in context: 
http://nabble.documentfoundation.org/Need-help-for-building-tp4203984p4203993.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Warning and error during settingup lode in windows

[slacka]

Nikhil,
What GPU and version of Windows do you have?


Markus,
I posted about  the same testFinancialXirrFormula error here.

  
I was only seeing this on my Win 10 laptop with intel HD 5500 
Driver: 20.19.15.4404 

My Win 10 desktop with a Nvidia GTX 650 passes all the Unit Tests.

I was planning to submit a patch to blacklist my current driver. Is that a
better solution, or is it better to remove the failing test as you have
already done?






--
View this message in context: 
http://nabble.documentfoundation.org/Warning-and-error-during-settingup-lode-in-windows-tp4203495p4203524.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: MSVC 2015's broken static initializer_list causing build failure

[slacka]

It's working now for me too. Thanks!



--
View this message in context: 
http://nabble.documentfoundation.org/MSVC-2015-s-broken-static-initializer-list-causing-build-failure-tp4202928p4203154.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: MSVC 2015's broken static initializer_list causing build failure

[slacka]

Per your recommendation, I upgrade to 
Microsoft Visual Studio Community 2015
Version 14.0.25431.01 Update 3

After the update, I'm still seeing the same error.

configure: error: working support for static initializer_list needed

-Luke




--
View this message in context: 
http://nabble.documentfoundation.org/MSVC-2015-s-broken-static-initializer-list-causing-build-failure-tp4202928p4203000.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: MSVC 2015's broken static initializer_list causing build failure

[slacka]

Microsoft Visual Studio Community 2015
Version 14.0.25123.00 Update 2


Is it working for you? What version are you running?



--
View this message in context: 
http://nabble.documentfoundation.org/MSVC-2015-s-broken-static-initializer-list-causing-build-failure-tp4202928p4202950.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: OpenCL enabled by default after OS reinstall causing Unit Test Failure

[slacka]

If someone wants to dig deeper, I’d be glad to run special debug builds like
I did for Ashod’s failing Unit tests.

Or, should we just blacklist my driver? What info do you need for that?

-Luke




--
View this message in context: 
http://nabble.documentfoundation.org/OpenCL-enabled-by-default-after-OS-reinstall-causing-Unit-Test-Failure-tp4202419p4202823.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: OpenCL enabled by default after OS reinstall causing Unit Test Failure

[slacka]

Niklas Johansson wrote
> Is it the only OpenCL test that fails for you?

Yes, Build finishes without error after I comment the
testFinancialXirrFormula out.Afterwards when I
open:core\sc\qa\unit\data\ods\opencl\financial\XIRR.odsThe actual results
seem to match the expected results. -Luke



--
View this message in context: 
http://nabble.documentfoundation.org/OpenCL-enabled-by-default-after-OS-reinstall-causing-Unit-Test-Failure-tp4202419p4202785.html
Sent from the Dev mailing list archive at Nabble.com.___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: OpenCL enabled by default after OS reinstall causing Unit Test Failure

[slacka]

I attached the old HDD to an external USB and reconfigured the old Cygwin.bat 
to run from the new drive. With the old make 4.0 and all the old LODE tools,
the weird " [0m [37;40m[ [0m [36;1;40mCUT [0m " on every line went away, but
the build still failed on Test name: ScOpenCLTest::testFinancialXirrFormula 

So maybe this is just a case of new drivers that need to be blacklisted? Or
something I had done on my old install disabled OpenCL? Any ideas? 

It looks like LODE was not to blame here, but it raises some interesting
questions. Is there any way to get LODE to install fresh tools (ex make 4.0
-> 4.2)? Do we really want LODE to always use the newest version, with
everyone’s LODE install slightly different based on when they ran it.




--
View this message in context: 
http://nabble.documentfoundation.org/OpenCL-enabled-by-default-after-OS-reinstall-causing-Unit-Test-Failure-tp4202419p4202737.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Budgeting & investing in features ...

[slacka]

Here are some ideas

* Regular scan-build reports like we do with CppCheck[1]
* Improve CppCheck (uncheck low priority/quality warnings, show new detected
problem since last run, and [2]).
* More variety in Jenkins bots like switching 1 of Linux to 32-bit or adding
64-bit MSVC 2015 
* Improve tinderboxes so they are better at reporting when a commit range
broke them


[1] https://wiki.documentfoundation.org/Development/Clang_Code_Analysis
[2]
http://nabble.documentfoundation.org/Re-Libreoffice-commits-core-git-cppcheck-style-fix-for-noExplicitConstructor-in-writerfilter-tp4201803.html



--
View this message in context: 
http://nabble.documentfoundation.org/Budgeting-investing-in-features-tp4202090p4202424.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

OpenCL enabled by default after OS reinstall causing Unit Test Failure

[slacka]

I just reinstalled windows 10, LODE, and VS2013. Now my new builds are
failing OpenCL Unit tests. This is not a regression as I built the same
version as I made on my old OS. After disabled the failing Unit Tests, I
discovered that the new binaries enable OpenCL by default, where as in my
old binary I cannot even enable OpenCL. 

Did something change in new Cygwin/LODE env that's causing OpenCL to be
enabled now? 

Unrelated, but the new Cygwin has this garbage to every line of the build:
[CUT


GPU: intel HD 5500
Driver: 20.19.15.4404

Here's a sniped down build log:

ScOpenCLTest::testStatisticalFormulaStDevPA1 finished in: 78ms
ScOpenCLTest::testFinancialMDurationFormula1 finished in: 125ms
D:/cygwin/home/Hearthstone/lode/dev/core/sc/qa/unit/opencl-test.cxx(2760) :
error : Assertion
Test name: ScOpenCLTest::testFinancialXirrFormula
assertion failed
- Expression: rtl::math::approxEqual(fExpected, fFormula)

Failures !!!
Run: 224   Failure total: 1   Failures: 1   Errors: 0

Error: a unit test failed, please do one of:
make CppunitTest_sc_opencl_test CPPUNITTRACE=TRUE # which is a shortcut for
the following line
make CppunitTest_sc_opencl_test
CPPUNITTRACE="'C:/PROGRA~2/MICROS~1.0/VC//../Common7/IDE/devenv.exe'
/debugexe" # for interactive debugging in Visual Studio
make CppunitTest_sc_opencl_test CPPUNITTRACE="drmemory -free_max_frames 20"
# for memory checking (install Dr.Memory first, and put it to your PATH)





--
View this message in context: 
http://nabble.documentfoundation.org/OpenCL-enabled-by-default-after-OS-reinstall-causing-Unit-Test-Failure-tp4202419.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: I'm new and I'm having build issues

[slacka]

> Do I need to delete the failed build before building again?
Not usually. If you do get stuck trying a 'make clean' before asking for
help never hurts.

> Does it need to be connected to the Internet while building? (so that I
> could disconnect the net while disabling my firewall to build)

This question was answered just a few hours before you posted it. 

http://nabble.documentfoundation.org/Build-Problem-with-Lode-tp4201726p4201764.html

Please search the dev list and use google to try to answer your own
questions before asking for help.



--
View this message in context: 
http://nabble.documentfoundation.org/I-m-new-and-I-m-having-build-issues-tp4201824p4201867.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Needs help

[slacka]

Use a text editor or IDE to edit the code. But first you need to pick an easy
hack that look doable and interesting to you.

https://wiki.documentfoundation.org/Development/EasyHacks 



--
View this message in context: 
http://nabble.documentfoundation.org/Needs-help-tp4201846p4201865.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

RE: Build Problem with Lode

[slacka]

Jason Marshall wrote
> From your experience, is it best to disable anti-virus entirely during the
> build, or should it be configured to ignore certain programs associated
> with the build?

As you can see from the build notes

  
ever different anti-virus programs have different false positives. If you
want to take the time to review the log and manually whitelist each
quarantined file, you can keep your anti-virus software enabled. Disabling
it is the universal solution with the added bonus of speeding up build
times.



Jason Marshall wrote
> Would the build still proceed if I disconnected my internet connection? I
> ask because if I need to disable anti-virus, I would prefer to also
> disable my internet connection for that period.

I've lost Internet in the middle of builds and still had them succeed.

I've browsed the Internet for years without AV software, and never once been
infected by malware. Then again, my main user account has lacked admin
privileges since my win2K days. I'm fanatical about keeping my OS/Browser
fully updated and have had flash set to only click-to-play and use the
NoScript extension to only allow JS from whitelisted sites since those
options have existed.

No AV software is 100% effective. They do not cover every virus signature
and cannot detect all new threats. I worked in IT for a large corporation.
During that time we were hit several times by 0-day infections that got to
our users before their signature had made it into our vendor’s DB. So if
you're browsing sketchy sites with outdated software and relying 100% on
your AV software to protect you, you're asking for trouble.



--
View this message in context: 
http://nabble.documentfoundation.org/Build-Problem-with-Lode-tp4201726p4201761.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Merging feature/commonsallayout branch

[slacka]

I just came back from a trip to China and found many machines there still
running XP with old versions of MS Office. I used the opportunity to
introduce several people there, including one IT manager, to LibreOffice.
Had we already dropped support for XP, it would have been an embarrassing
demonstration and reflected badly on us.  

Dropping support for XP isn't going to push anyone into upgrading there OS.
It will however prevent new users from discovering us, especially in markets
like China and India. 




--
View this message in context: 
http://nabble.documentfoundation.org/Merging-feature-commonsallayout-branch-tp4197400p4198948.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Fresh install of Win 10 + LODE + vs2013-ide-integration = Error 127

[slacka]

Hi Bjoern, 
Should this be working with a vanilla LODE install? With the master I'm
getting:

 $  ../../opt/bin/make vs2013-ide-integration
cd C:/cygwin/home/luke/lode/dev/core && (LC_MESSAGES=C
C:/cygwin/home/luke/lode/opt/bin/make
cmd="C:/cygwin/home/luke/lode/opt/bin/make -npf Makefile.gbuild all" cmd ||
true) | C:/cygwin/home/luke/lode/dev/core/bin/gbuild-to-ide --ide vs2013
make[1]: *** [cmd] Error 127
Solution LibreOffice:
Successfully created the project files.

Has anyone else got this working yet with LODE + vs2013? Any ideas what I
might be doing wrong? Do I need to do a fresh LODE install? 



--
View this message in context: 
http://nabble.documentfoundation.org/Fresh-install-of-Win-10-LODE-vs2013-ide-integration-Error-127-tp4195655p4197131.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Fresh install of Win 10 + LODE + vs2013-ide-integration = Error 127

[slacka]

Yes, I had a successful build with LODE's default
autogen.input="--enable-debug". After it finished, I ran
'./instdir/program/soffice.exe' to make sure everything was actually
working. It seemed fine. So I tried several runs of
'C:/cygwin/home/luke/lode/opt/bin/make vs2013-ide-integration'. I also tried
rebooting my VM and removing the 'LibreOffice.sln' file.

This is on the same computer that ide integration used to work every time.
Could it be related to the switch from Win 7 to Win 10? Or is it more likely
that LODE pulls a different version of make (or some other file) now than it
did when ide integration was working?




--
View this message in context: 
http://nabble.documentfoundation.org/Fresh-install-of-Win-10-LODE-vs2013-ide-integration-Error-127-tp4195655p4195672.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: export-validation in tests by default causing 32 bit Ubuntu to crash

[slacka]

The error "- failed to execute: sh /core/bin/officeotron.sh
/tmp/lu16851plw1cl.tmp > /tmp/lu16851plw1cn.tmp" along with an apport crash
report of openjdk 8, led me to believe this was a java issue. 

Here are a summary of my results:
Ubuntu 16.04 64-bit - builds successfully
Ubuntu 16.04 32-bit - fails ww8export.test 
Ubuntu 14.04 32-bit - builds successfully with Open JDK 7

I build an Ubuntu 16.04 32-bit with the export tests disabled. Then I opened
all of the SdImportTest::testDocumentLayout tests and resaved and reloaded
them. No problems. 

What else can I do to try to help you track this issue down?



--
View this message in context: 
http://nabble.documentfoundation.org/export-validation-in-tests-by-default-causing-32-bit-Ubuntu-to-crash-tp4192925p4194512.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Test File: sc/qa/unit/data/functions/fods/chiinv.fods: fails with Assertion

[slacka]

Eike Rathke-2 wrote
> If you want to get a working build without disabling all checks then you
> can use
> https://gerrit.libreoffice.org/gitweb?p=core.git;a=commitdiff;h=b9a27d5856f60688456762bfcc29c38670009254
> 
> that disables the function tests for linux_x86 builds.
> 
> However, if you'd find a general solution that does not involve
> disabling the tests that would be more than welcomed.
> 
>   Eike

We are only failing 3 individual tests. And we fail the same tests Excel
fails. Instead of disabling all test for x86 Linux , why not disable or
change the rounding accuracy of the individual tests? 

For example, CHIINV can be made to work with both x86, x86-64 and Excel by
changing 
C8=ROUND(A8,3)=ROUND(B8,3) 
 
VDS can be made to work with x86, x86-64, and Excel by changing
C11=ROUND(A11,10)=ROUND(B11,10)

MINVERSE x86 and Excel get similar results. Unless there is some evidences
we have the same bug in our x86 code as Excel, the test is invalid or the
bug is with the x86-64 code. So shouldn’t we disable that individual test?



Eike Rathke-2 wrote
> So you actually *do* see it. Or only not in chiinv.fods? 

 
Sorry I was not clear. MINVERSE is the first test to fail on my AMD desktop. 
CHIINV does fail but only when I run it manually. I assume the tests are not
run sequentially. Are they? If they are something weird is going on and I
can try disabling MINVERSE and VDS to see if that's enough for a successful 
build. 





--
View this message in context: 
http://nabble.documentfoundation.org/Test-File-sc-qa-unit-data-functions-fods-chiinv-fods-fails-with-Assertion-tp4192267p4193577.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Recommended build instructions ...

[slacka]

Is the  "make vs2013-ide-integration" script working for anyone? With a clean
Win 10 install + VS 2013 + LODE, I always get:
make[1]: *** [cmd] Error 127 

From, 
http://nabble.documentfoundation.org/Error-building-Visual-Studio-2013-project-file-for-LibreOffice-on-Windows-tp4140307p4140941.html

"The "make version 4.0" do it wrong, I build ONLY the VS-Solution with "make
version 3.82"
The size is 517.746 Bytes when you have trouble to found, call me, I have
forget where I downloaded."

Lode used to download 3.82, but now it downloads 4.0. So new users are out
of luck.

Does anyone has a version of make that works with make
vs2013-ide-integration? If so, could you please share it on a cloud storage
service? 



--
View this message in context: 
http://nabble.documentfoundation.org/Recommended-build-instructions-tp4193014p4193568.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Recommended build instructions ...

[slacka]

Speaking of wiki build instructions, the IDE instructions for Windows have
not worked for almost a year now.
Both the  IDE instructions
  
and  Windows Instructions

  
say to build with  build with "--enable-debug" and then "make
vs2013-ide-integration".  This results in the following error:

cd E:/core && (LC_MESSAGES=C E:/lode/opt/bin/make
cmd="E:/cygwin/home/Hearthstone/lode/opt/bin/make -npf Makefile.gbuild all"
cmd || true) | E:/core/bin/gbuild-to-ide --ide vs2013

make[1]: *** [cmd] Error 127

According this thread

 
, You need an old version of make. 

Could someone please verify these instructions, and put them on the wiki
with a *working* download location? None of the versions of make that I was
able to find work with the script in that thread. 




--
View this message in context: 
http://nabble.documentfoundation.org/Recommended-build-instructions-tp4193014p4193353.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Test File: sc/qa/unit/data/functions/fods/chiinv.fods: fails with Assertion

[slacka]

This may be a regression, but I'm not seeing it with the 32-bit 5.1.4.2
official LibreOffice for Ubuntu 16.04. With minverse.fods, C10 changes to
FALSE after pressing Shift+Ctrl+F9. With vdb.fods, C11 changes to FALSE
after a force recalculate.

Interestingly the minverse.fods test also fails with Excel 2013 which
calculates A10=-4.5E+15, while 32-bit calc comes to A10=-4.7E+16. 

Excel also fails the vdb.fods test at C11. Both Excel and Calc can pass the
failing vdb.fods test  by relaxing the rounding accuracy to 10.



--
View this message in context: 
http://nabble.documentfoundation.org/Test-File-sc-qa-unit-data-functions-fods-chiinv-fods-fails-with-Assertion-tp4192267p4193164.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: export-validation in tests by default causing 32 bit Ubuntu to crash

[slacka]

with the following autogen.input: 
--enable-ext-validator
--with-export-validation
--enable-symbols

I get a crash in bfbd66f151002af6f65b9c062cc511797690e625


Test name: SdImportTest::testDocumentLayout
equality assertion failed
- Expected: 0
- Actual  : 34304
- failed to execute: sh
/media/luke/9e79b120-4914-425d-b6ec-97b55ef4c85e/home/luke/lo/core/bin/officeotron.sh
/tmp/lu15504xl5v3v.tmp > /tmp/lu15504xl5v3x.tmp

Failures !!!
Run: 46   Failure total: 1   Failures: 1   Errors: 0
[Thread 0x4b2e3b40 (LWP 15536) exited]
[Thread 0x4b0e2b40 (LWP 15535) exited]
[Thread 0x49f1fb40 (LWP 15534) exited]
[Thread 0x49d1eb40 (LWP 15533) exited]
[Thread 0x40709b40 (LWP 15508) exited]
[Inferior 1 (process 15504) exited with code 01]
(gdb) thread apply all bt
(gdb) quit
luke@luke-Inspiron-5523:~/u64/lo/core$ ls *.log
config.log  hs_err_pid15539.log


I'm not sure where the bt went. Here is the hs_err_pid15539.log file:
http://pastebin.com/xxqGndMF


Here was the log from the original build:
http://pastebin.com/x983UT2t




--
View this message in context: 
http://nabble.documentfoundation.org/export-validation-in-tests-by-default-causing-32-bit-Ubuntu-to-crash-tp4192925p4193137.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Recommended build instructions ...

[slacka]

Michael Meeks-5 wrote
> * I was excited about Chocolatey ... eventually I gave up, and moved on to
> manual installation.

As did I. If you look at the history all of the Chocolatey info was recently
added. It seems to cause more problems than it solves. Should we should move
it off into it's own section at the end until it offers a smooth experience?


Michael Meeks-5 wrote
> *  Recommending a known-good Visual Studio
> 
>  The LODE page for some reason recommends Visual Studio 2015 - three 
> times, though there is 2013 in the small print. 

Again, the VS2015 info was all added with Chocolatey. The  old LODE wiki
page recommend 2013.

  
Also the main Windows dev page also makes it clear that 2013 is the
preferred version. 

That said I'd rather see a VS2015 Jenkins or Tinderbox rather than steer
people away from it. I've been building both 32/64 VS2015 builds regularly
all year long.


Michael Meeks-5 wrote
>  * Antivirus 

The main  Windows dev pages covers this topic thoroughly.

  

Since you've verified it's a problem, please add McAffe to the list that's
already there.






--
View this message in context: 
http://nabble.documentfoundation.org/Recommended-build-instructions-tp4193014p4193053.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: MSVC 2015 Error C2672: no matching overloaded function found

[slacka]

Thanks Stephan! I verified that both the 32 and 64-bit builds are working
again under MSVC 2015 after your commit.





--
View this message in context: 
http://nabble.documentfoundation.org/MSVC-2015-Error-C2672-no-matching-overloaded-function-found-tp4192415p4192564.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: LibreOffice's New Area Dialog Box crashes when compiled with Clang

[slacka]

I sent the backtrace to Stephan directly, which he used to resolve the clang
crash with
https://cgit.freedesktop.org/libreoffice/core/commit/?id=e11931da72eabd98f9ea49ae93bd76039b283268
 

Why was this working with gcc and MSVC? Undefined behavior or a compiler
bug?

Thanks Stephan!




--
View this message in context: 
http://nabble.documentfoundation.org/LibreOffice-s-New-Area-Dialog-Box-crashes-when-compiled-with-Clang-tp4191943p4192391.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: LibreOffice's New Area Dialog Box crashes when compiled with Clang

[slacka]

Here is the backtrace made with $ instdir/program/soffice --backtrace, and
the steps listed in my first post. Is there anything else I can do?




--
View this message in context: 
http://nabble.documentfoundation.org/LibreOffice-s-New-Area-Dialog-Box-crashes-when-compiled-with-Clang-tp4191943p4192269.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Another C2220: warning treated as error with MSVC 2015

[slacka]

Can we trust MSVC 2015 unreachable code analysis like we with  this similar
issue?

  

The patch below fixes the build:

diff --git a/comphelper/source/misc/threadpool.cxx
b/comphelper/source/misc/threadpool.cxx
index 6846f4b..6a335e0 100644
--- a/comphelper/source/misc/threadpool.cxx
+++ b/comphelper/source/misc/threadpool.cxx
@@ -72,17 +72,7 @@ public:
 {
 SAL_WARN("comphelper", "exception in thread worker while
calling doWork(): " << e.Message);
 }
-try {
-delete pTask;
-}
-catch (const std::exception &e)
-{
-SAL_WARN("comphelper", "exception in thread worker while
deleting task: " << e.what());
-}
-catch (const css::uno::Exception &e)
-{
-SAL_WARN("comphelper", "exception in thread worker while
deleting task: " << e.Message);
-}
+delete pTask;
 pTag->onTaskWorkerDone();
 }
 }






--
View this message in context: 
http://nabble.documentfoundation.org/C2220-warning-treated-as-error-64-bit-MSVC-2015-tp4184053p4189213.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: New MSVC 2015 build failure

[slacka]

Yes, that fixed it. Thanks  Michael!

Now the only hold up with MSVC 2015 is the C4702: unreachable code Error. 

http://nabble.documentfoundation.org/C2220-warning-treated-as-error-64-bit-MSVC-2015-td4184053.html#a4189120







--
View this message in context: 
http://nabble.documentfoundation.org/New-C2220-warning-treated-as-error-MSVC-2015-build-failure-tp4187644p4189145.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: New C2220: warning treated as error (MSVC 2015 build failure)

[slacka]

After Michael Stahl's commit,

https://cgit.freedesktop.org/libreoffice/core/commit/?id=59e4bd07211d8509dcb3e89f6645c0ba3085df23

MSVC 2015 can successfully build master again.  Thanks everyone!



--
View this message in context: 
http://nabble.documentfoundation.org/New-C2220-warning-treated-as-error-MSVC-2015-build-failure-tp4187644p4187825.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Error building Visual Studio 2013 project file for LibreOffice on Windows

[slacka]

Ashod Nakashian-2 wrote
> I haven't tried a different version of make as Juergen suggests, but I
> confirm that the issue has to do with the fact that make doesn't generate
> the invariant data that the python script excepts. Specifically, all the #
> lines that contain the paths and filenames are missing from the output,
> hence the python script's failure to generate proper project/solution
> files.


About a year ago, I setup my build environment with Lode and I had no issues
with building a VS2013  project file. Recently I had to reset my Windows 10
install. With a clean install windows and Lode, now I'm getting the 
"make[1]: *** [cmd] Error 127" when I try to make a project file. 

Is Lode pulling a new version of make that's causing this error? Has anyone
come up with a work-around?



--
View this message in context: 
http://nabble.documentfoundation.org/Error-building-Visual-Studio-2013-project-file-for-LibreOffice-on-Windows-tp4140307p4186909.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: vs2013 + Intel GPU = build failure on LO 4.4+

[slacka]

After
https://cgit.freedesktop.org/libreoffice/core/commit/?id=40b0b9ab7703a165295b008f47df14d2ec076fb1
LibreOffice can now be successfully built with VS 2013 again. 

Thanks Mark!



--
View this message in context: 
http://nabble.documentfoundation.org/vs2013-Intel-GPU-build-failure-on-LO-4-4-tp4185252p4185446.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: C2220: warning treated as error (64 bit MSVC 2015)

[slacka]

With sberg's and Noel's patches, I can now build the 64-bit version again.
Nice work team!

To answer my own question, the C4334 warning is new in VS 2015 Update 2.




--
View this message in context: 
http://nabble.documentfoundation.org/C2220-warning-treated-as-error-64-bit-MSVC-2015-tp4184053p4184447.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: C2220: warning treated as error (64 bit MSVC 2015)

[slacka]

Even after:
https://cgit.freedesktop.org/libreoffice/core/commit/?id=4a8caa37fe83c389f4fd43219e8ea0f21f03c6fe

With the 64-bit build, I'm still getting the following error:

[build CXX] vcl/source/filter/ixbm/xbmread.cxx
[build CXX] vcl/source/filter/ixpm/xpmread.cxx
E/vcl/source/filter/igif/gifread.cxx(251): error C2220: warning treated as
error - no 'object' file generated
E/vcl/source/filter/igif/gifread.cxx(251): warning C4334: '<<': result of
32-bit shift implicitly converted to 64 bits (was 64-bit shift intended?)
E/vcl/source/filter/igif/gifread.cxx(462): warning C4334: '<<': result of
32-bit shift implicitly converted to 64 bits (was 64-bit shift intended?)
[build CXX] vcl/source/filter/jpeg/Exif.cxx
[build CXX] vcl/source/filter/jpeg/jpeg.cxx
E/solenv/gbuild/LinkTarget.mk:189: recipe for target
'E/workdir/CxxObject/vcl/source/filter/igif/gifread.o' failed
make[1]: *** [E/workdir/CxxObject/vcl/source/filter/igif/gifread.o] Error 2
make[1]: *** Waiting for unfinished jobs
Makefile:257: recipe for target 'build' failed
make: *** [build] Error 2




--
View this message in context: 
http://nabble.documentfoundation.org/C2220-warning-treated-as-error-64-bit-MSVC-2015-tp4184053p4184112.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice