Re: Build failure on x86 linux: undefined reference to `__atomic_load'

Noel, I can successfully build LO on i686 with LDFLAGS="-latomic" This is overkill. I think patch is needed for the cuckoo module that you added in https://cgit.freedesktop.org/libreoffice/core/commit/?id=3749d9af3745 for IA-32 clang. I attempted to do this but I'm not family with how this patc

Re: Build failure on x86 linux: undefined reference to `__atomic_load'

Rene, > Or clang needs -latomic and gcc not. Yes, it does. Looks like a known bug in clang: https://bugs.llvm.org/show_bug.cgi?id=45785 Building with "-DCMAKE_CXX_FLAGS=-latomic", resolves the undefined reference to `__atomic_load' and allows the build to complete successfully. However, it caus

Re: Build failure on x86 linux: undefined reference to `__atomic_load'

Thanks for helping me to try to reproduce this. I'm building with clang-14. Are you building with gcc? I've confirmed that when I built libcuckoo from https://github.com/efficient/libcuckoo with clang, I get a similar failure to the initial failure. When I build it with gcc-11, the build is succ

Build failure on x86 linux: undefined reference to `__atomic_load'

Noel, After commit 3749d9af3745c0eaff7239e379578e4e2af89e9d tdf#130795 use concurrent hashmap in SharedStringPool On both OpenSUSE Tumbleweed and Arch 32, I see the build failure below. Would you like any additional debugging info? -Luke [DEP] LNK:Library/libsvllo.so [LNK] Library/libsvllo.

Re: freetype2 2.11.0-1.1 Update Breaks on OpenSUSE Tumbleweed

The issue was fixed by https://cgit.freedesktop.org/libreoffice/core/commit/?id=a0edcc68f94915a78fcc08e70d2cdd752abd9ebb Thanks Luboš!

Re: freetype2 2.11.0-1.1 Update Breaks on OpenSUSE Tumbleweed

This also breaks the built on Gentoo and has been reported there too(see below). Should we patch our tarball or just update it? Luboš, You've been the most active maintainer. Any thoughts? -Luke From: bugzilla_nore...@suse.com Sent: Sunday, August 22,

freetype2 2.11.0-1.1 Update Breaks on OpenSUSE Tumbleweed

After updating openSUSE Tumbleweed 20210726-0 -> 20210810-0, I can not longer build LibreOffice. The issue is most likely the update of to freetype2-devel-2.10 -> 2.11 I filed a bug report at: https://bugzilla.opensuse.org/show_bug.cgi?id=1189444 freetype2 2.11 is still in testing on arch: http

JunitTest_ucb_complex test hangs after 739aaf02db335 on Linux x86

After https://cgit.freedesktop.org/libreoffice/core/commit/?id=739aaf02db33 osl::Mutex->std::mutex in bridges/except On both Arch Linux 32 and OpenSUSE Tumbleweed i686, 'make check' now hangs on JunitTest_ucb_complex. I can consistently reproduce this failure with both clang 13 and gcc 11.

Re: Build Failure on OpenSUSE Tumbleweed after distro upgrade: `NSSUTIL_3.59' not found

This was resolved after a distro update of openSUSE Tumbleweed 20210709-0 -> 20210725-0 which updated: mozilla-nss-3.64 -> mozilla-nss-3.66 I no longer need "--with-system-nss" -Luke ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org

Re: Build failure, Error: no matching function for call on x86 Linux

or gcc i686. -Luke From: Rene Engelhard Sent: Friday, July 16, 2021 1:20 AM To: Luke Benes; Libreoffice Dev List Subject: Re: Build failure, Error: no matching function for call on x86 Linux Hi, Am 15.07.21 um 15:10 schrieb Luke Benes: > Build succeeds now and tests

Re: Build failure, Error: no matching function for call on x86 Linux

Rene fixed this issue with: https://cgit.freedesktop.org/libreoffice/core/commit/?id=51754ca5349d Build succeeds now and tests pass on Arch 32. Thanks! ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/l

Build Failure on OpenSUSE Tumbleweed after distro upgrade: `NSSUTIL_3.59' not found

Builds are now failing on the rolling distro OpenSUSE Tumbleweed After the latest update, both gcc and clang builds and both both x86-64 and i686 architectures fail. Seems to be caused by caused by: java.io.IOException: /core/instdir/program/libnssutil3.so: version `NSSUTIL_3.59' not f

Build failure, Error: no matching function for call on x86 Linux

Mert, After commit https://cgit.freedesktop.org/libreoffice/core/commit/?id=67277595902d Unit tests for .uno:MoveShapeHandle command Fails with the error below on both Arch 32 and OpenSUSE i686. Any idea why this would fail on 32-bit linux? -Luke [CXX] sd/qa/unit/tiledrendering/tiledrend

Re: CppCheck Report on vm140 Not Running

Whether Maaten misremembered, there was a net spit, or problem with your search, he did reach out to the dev list:  http://document-foundation-mail-archive.969070.n3.nabble.com/Automated-cppcheck-reports-not-running-tt4290186.html     > I'm very much against re-hooking a box    A box that ran for y

Re: CppCheck Report on vm140 Not Running

Cloph, > But given that the job had stopped so many months ago without anyone > complaining At the time, Maarten reported this on the dev IRC, infra IRC, and the mailing list. At the time, I assumed someone from infra would take care of it. > Recreating it is always an option Why can't you

Re: CppCheck Report on vm140 Not Running

> Yes, at least that's how I use these linters. How common is this? A check of > git rev-list --all --grep='cppcheck' -i --count 1847 Grepping shows a good mix of usual suspects and many GSoC students looking for easy hacks. More importantly there were almost none since the CppCheck script

Re: CppCheck Report on vm140 Not Running

> I'm more interested in running such tools locally Depending on the configuration, cppcheck scans can take 8+ hours to run. This can be greatly reduce with parallel checks at the cost of several checks being disabled. > The other problem with cppcheck is that it doesn't build on an existing c

Re: CppCheck Report on vm140 Not Running

I spoke to the author of the cppcheck script, Maarten Hoes, about this issue. We would like to know why no one has responded to our emails about the cppcheck service being down. Are devs not interested in cppcheck's results, is it the high false positives, or is it that no one knows how to help

Re: CppCheck Report on vm140 Not Running

I dug a little deeper and the last error report has an "unexpected end of file" when I tried to decompress it.[1] Is vm140 out of free space? -Luke [1] https://dev-builds.libreoffice.org/cppcheck_reports/cppcheck_reports.tar.bz2 ___ LibreOffice mail

CppCheck Report on vm140 Not Running

The script to email the dev list with the updated CppCheck Report at has stopped running. Could we get this restarted? While it was not perfect, a quick grep of the commit log shows hundred of fixed bugs that it helped highlight. The script was running on host vm140 as /home/buildslave/sourc

Re: Unit Tests failing when built with clang 12

The UITest_calc_tests9 failure with clang 12/13 was fixed by https://cgit.freedesktop.org/libreoffice/core/commit/?id=9ccbf716ba16 Fix null-pointer-use Thanks Stephan! ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.f

Re: Unit Tests failing when built with clang 12

Sounds like there is a headless or distro dependent aspect of this bug too. I can reproduce this on both my i686 openSUSE Tumbleweed (32-bit) laptop and on my x86-64 openSUSE Tumbleweed desktop. This issue has not been fixed in clang 13 as today's build 402f2cae7dcab also fails. I also was able

Unit Tests failing when built with clang 12

The recently added Unit Test test_tdf131000 https://cgit.freedesktop.org/libreoffice/core/commit/?id=df33714f0eca fails with clang 12 but not with gcc 10 or clang 11. I bisected this regression to this change in clang: https://github.com/llvm/llvm-project/commit/69cd776e1ee79e72ccbdad30749eac045

CppunitTest_sc_shapetest failing after cd966aac6e

After https://cgit.freedesktop.org/libreoffice/core/commit/?id=cd966aac6e tdf#137033 improve save of cell anchored shapes CppunitTest_sc_shapetest fails with the errors below. I can reliable reproduce the failure and the verified the bisect with a 'make clean' between builds. Let me know i

JunitTest_sfx2_complex failing on Windows after f5ab8bcbfd20

After https://cgit.freedesktop.org/libreoffice/core/commit/?id=f5ab8bcbfd20 WIN don't notify clipboard change with SolarMutex I'm seeing the failure below on Windows 10 x86. Any idea why this would cause this failure? Let me know if you need any additional debugging info. -Luke [build JU

Re: build failure on ubuntu 18.04

Try: sudo apt-get install libx11-xcb-dev For some reason, the wiki was just massively paired down with stuff like this removed. https://wiki.documentfoundation.org/index.php?title=Development/Linux_Build_Dependencies In the case of dependencies, less is not more. _

Bridgetest Failing on RPI4 armhf

On Raspberry Pi OS with both gcc-8 and clang 12, the build is failing with the following error: ### float does not match! failed struct comparison test failed ### float does not match! failed recursive test results failed standard test failed exception occurred: error: test failed! /core/testtoo

Re: UITest_writer_tests failing on KDE Neon

Correct URL: https://cgit.freedesktop.org/libreoffice/core/commit/?id=a658ece9f9fa308084c3e0f4662dda7afb9a0879 From: Luke Benes Sent: Sunday, September 20, 2020 9:25 PM To: Caolán McNamara; libreoffice@lists.freedesktop.org; Xisco Fauli; Miklos Vajna

Re: UITest_writer_tests failing on KDE Neon

revert https://cgit.freedesktop.org/libreoffice/core/commit/?id=a658ece9f9fa308084c3e0f4662dda7afb9a0879/ now? Thanks everyone! From: Caolán McNamara Sent: Sunday, September 20, 2020 2:56 PM To: Luke Benes; libreoffice@lists.freedesktop.org; Xisco Faul

UITest_writer_tests failing on KDE Neon

After https://cgit.freedesktop.org/libreoffice/core/commit/?id=b6ab2330d97672936edc56de8d6f5b6f772908ff On KDE Neon, I'm seeing the following failure: [UIT] writer_tests ... == FAIL: test_tdf135018 (trackedChanges.trackedchanges

New Unit Test for tdf#130960 causing Build Failure on i686

After https://cgit.freedesktop.org/libreoffice/core/commit/?id=4a581f12e0d0 tdf#130960: Add UItest The UI test is failing on test_tdf131907 (trackedChanges.CalcTrackedChanges) Xisco, Do you need any additional debugging info? Any idea why this would fail on i686? Thanks -Luke build l

i686 Linux build failure error: no viable conversion from 'xmlDocUniquePtr'

On Arch linux 32, I'm seeing the following build failure [CXX] sd/qa/unit/export-tests.cxx /core/sd/qa/unit/export-tests.cxx:1284:15: error: no viable conversion from 'xmlDocUniquePtr' (aka 'unique_ptr<_xmlDoc, xmlDocDeleter>') to 'xmlDocPtr' (aka '_xmlDoc *') xmlDocPtr pXmlDoc = parseExport

32-bit Linux build error: no matching function for call to 'assertEquals'

[CXX] toolkit/qa/cppunit/EventContainer.cxx /core/toolkit/qa/cppunit/EventContainer.cxx:73:5: error: no matching function for call to 'assertEquals' CPPUNIT_ASSERT_EQUAL(4, nEventCount); ^~~~ /core/workdir/UnpackedTarball/cppunit/include/cppunit/TestAssert

Re: LibreOffice and old Microsoft Binary file formats.

> MS Word in the web (via onedrive) You are comparing apples to oranges. The onedrive version is the free, crippleware version. The paid version that companies use does include the functionality to save as with the older binary formats. [1] Until recently, my company had a group policy to save

Re: Planned Gerrit upgrade on Wed, Dec 25 from 00:00 to 04:00 UTC

What is the URL to change that? Some people might not want their email name to be changed to their SSO login IDs. From: Guilhem Moulin Sent: Friday, December 27, 2019 11:34 AM To: Luke Benes Cc: Libreoffice Dev List Subject: Re: Planned Gerrit upgrade on Wed, Dec

Re: Planned Gerrit upgrade on Wed, Dec 25 from 00:00 to 04:00 UTC

Guilhem, With the new Gerrit, I have noticed that people's usernames have changed on the commit messages. For example: Ayhan Yalçınsoy --> ayhanyalcinsoy https://cgit.freedesktop.org/libreoffice/core/log/?qt=author&q=ayhanyalcinsoy%40pisilinux.org Mine has also changed. The username gerrit pick

Re: chart2.check fails in testAxisTitlePositionDOCX

thing other than 100%. Thanks, -Luke From: Luke Benes Sent: Saturday, December 7, 2019 12:47 PM To: Regina Henschel ; Regina Henschel ; Libreoffice Dev List ; Balazs Varga Subject: Re: chart2.check fails in testAxisTitlePositionDOCX   Regina, This is not an intermittent failure and no

Re: chart2.check fails in testAxisTitlePositionDOCX

Regina, This is not an intermittent failure and not the same error as your gerrit failures. Rather it is a yet another Windows HiDPI bug and a recent regression. Possibly when these tests were added a month ago: https://cgit.freedesktop.org/libreoffice/core/commit/?id=9ff954d5f780 tdf#12790

Re: build failure on i686: error: invalid conversion and no matching function

Stephan's patch, https://gerrit.libreoffice.org/#/c/83912/ fixes the build. Christian, Issues like this, are a reminder that we still need to get an x86 Jenkin's Bot setup. The latency in our previous communications was discouraging and then life took over. I'll have some free time over the hol

build failure on i686: error: invalid conversion and no matching function

Caolán, https://cgit.freedesktop.org/libreoffice/core/commit/?id=278a365c68e0 Related: tdf#126043 use fastest png compression ratio Does actually hurt:) It's causing the following error on x86 builds: [CXX] vcl/unx/gtk3/gtk3gtkinst.cxx /core/include/cppu/unotype.hxx: In instantiation of ‘stat

Re: Build failure with clang on older CPU :Illegal instruction

I confirmed that git bisect identified the wrong commit, probably because I didn't run a `make clean` between builds. Also confirmed that Tomaž's patch https://gerrit.libreoffice.org/#/c/82422/ allows a successful build on older CPUs. Superb job tracking down and fixing this issue despite my bad

Build failure with clang on older CPU :Illegal instruction

Noel, After https://cgit.freedesktop.org/libreoffice/core/commit/?id=09f77e8ed51fc64fccc6a14e87eed48b2f15a28d     loplugin:unusedmethods Clang 7 on KDE Neon x86-64, and clang 10-git on openSUSE Tumbleweed i686 is failing with  [CUT] tools_test Illegal instruction (core dumped) It looks like /

clang 10 error: use of overloaded operator '!=' is ambiguous

clang version 10.0.0 (https://github.com/llvm/llvm-project.git 8e050e41a4b1193592f9b4298f14935f5878ae5f / r375496)  is failing with the following new errors: [CXX] vcl/unx/generic/gdi/salgdi.cxx /core/vcl/unx/generic/gdi/salgdi.cxx:138:18: error: use of overloaded operator '!=' is ambiguous (wi

Unit Test: CppunitTest_sc_opencl_test failing on Windows

After https://cgit.freedesktop.org/libreoffice/core/commit/?id=4ee424b3ddc6 Pre-allocate an ScInterpreter object for each thread... Both 32 and 64-bit windows builds are failing with the following error: D:/lode/dev/core/sc/qa/unit/opencl-test.cxx(573) : error : Assertion Test name: ScOpenCLTe

Re: CppunitTest_sw_layoutwriter failing on Windows with HiDPI

After Stephan and Balazs' patches, I can now build on windows with HiDPI. Thanks guys! Does it really make sense for all of these unit tests to be DPI dependent? -Luke ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freede

CppunitTest_sw_layoutwriter failing on Windows with HiDPI

Miklos, The Unit Test in https://cgit.freedesktop.org/libreoffice/core/commit/?id=c56bf1479cc71d1a2b0639f6383e90c1f7e3655b Is failing on Windows with 125% scale factor. The build fails with the following error: C:/core/sw/qa/extras/uiwriter/uiwriter2.cxx(2253) : error : Assertion Test name: tes

Re: CppunitTest_sw_layoutwriter failing on Windows with HiDPI

Sorry. I copy/pasted the wrong commit id. The build started failing after the Unit Test added in https://cgit.freedesktop.org/libreoffice/core/commit/?id=55136439e71b7adc62a46a3d3dc8de26d54d989d tdf127448 Chart: Avoid distortion of charts with multilevel axis labels Should the assert be relaxed

CppunitTest_sw_layoutwriter failing on Windows with HiDPI

The Unit Test added in https://cgit.freedesktop.org/libreoffice/core/commit/?id=4ac31078b9c46231f8ecf0409a1724749ac8c5a4 Is causing the core Unit Test CppunitTest_sw_layoutwriter to fail when you set, Settings->Display->Scale=125% in Windows 10. horizontal_multilevel.odt: C:/lode/dev/core/te

Re: Fwd: [global-libreoffice-ci] lo_daily_update_gandalf - Build # 666 - Still Failing!

https://cgit.freedesktop.org/libreoffice/core/commit/?id=14087d3e5fed9b56384432d9aeac608a5e8d86cf         tdf#121670 ooxmlimport: no columns in page styles, only sections was the cause of this failure ___ LibreOffice mailing list LibreOffice@lists.free

Re: Fwd: [global-libreoffice-ci] lo_daily_update_gandalf - Build # 666 - Still Failing!

A clean install of KDE Neon is failing with the same error that Stephan reported: https://ci.libreoffice.org/job/lo_daily_update_gandalf/lastBuild/console ooxmlexport4.cxx:1209:Assertion Test name: testTdf81345_045Original::Import_Export_Import assertion failed - Expression: pageStyleName != "Sta

CppunitTest_sw_ooxmllinks failing on Windows

After https://cgit.freedesktop.org/libreoffice/core/commit/?id=217a80fd205c Some windows boxes like @42 are failing. https://tinderbox.libreoffice.org/cgi-bin/gunzip.cgi?tree=MASTER&brief-log=1563378001.26689 24716

CppunitTest testFlipAndRotateCustomShape failing on certain setups

My desktop and @39 have been failing ever since the additional Unit Tests were enabled with https://cgit.freedesktop.org/libreoffice/core/commit/?id=3f7e8ddea89f6340cd18b5b34f5a7c5f503962be Here is a sample of @39 failure: https://tinderbox.libreoffice.org/cgi-bin/gunzip.cgi?tree=MASTER&full-log=

CppunitTest_sw_ooxmlexport3 broken on HiDPI setup

Ever since the additional unit tests were enabled with https://cgit.freedesktop.org/libreoffice/core/commit/?id=3f7e8ddea89f6340cd18b5b34f5a7c5f503962be The CppunitTest_sw_ooxmlexport3 unit test is failing when display scaling does not equal 100% For 125% the test is failing with the following

Jenkins_Callgrind broken after: Drop extra define ENABLE_GTKSINK

Michael, https://cgit.freedesktop.org/libreoffice/core/commit/?id=34bbf192a7753205bb64d14e4eec4ce303317396 broke Jenkins_Callgrind https://tinderbox.libreoffice.org/cgi-bin/gunzip.cgi?tree=MASTER&brief-log=1559555453.4509 https://ci.libreoffice.org/computer/vm139/builds with this error: avmedi

Re: Need for new x86 Jenkin's Bot

Christian, Our concern is that by scuttling @87, we will lose important diversity in TDF's testing infrastructure. While upgrading @87 does address this, it is not what we are asking for. Why have you chosen to not upgrade @87 like you have the others? Master will build on x86 Fedora 30, Cent

Need for new x86 Jenkin's Bot

upgrade @87 to CentOS 7 or Debian 9.0 before bit rot makes this a difficult task. Currently master has no problem building on 32-bit Fedora 30. -Luke From: Christian Lohmaier Sent: Tuesday, June 4, 2019 6:17 AM To: Luke Benes Subject: Re: @87 reboot? Hi Luke, On

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

This long weekend, I attempted to update the patch for libgpg-error-1.36. This went well until I hit a new file in 1.36, sysutils.c, which makes use of  a UNIX header .  Thorsten converted this to a win32's in other files,[1] but following his example didn't work for me here. We really need to

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

Thorsten fixed it. It's working now for me. Thanks! ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice

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

https://dev-www.libreoffice.org/src/libgpg-error-1.36.tar.bz2 I'm getting:  403 Forbidden Error https://dev-www.libreoffice.org/src/libgpg-error-1.27.tar.bz2 Correctly downloads the tarball After the 403 issue with 1.36 is fixed, I'll be happy to create a patch to update download.lst and attem

CppUnit SdMiscTest::testTdf119956 Failing on Windows with 150% scale factor

While testing various scaling factors for the starmath issue, http://document-foundation-mail-archive.969070.n3.nabble.com/CppunitTest-starmath-qa-cppunit-Failing-on-Windows-with-HiDPI-screens-tp4261772.html I discovered that SdMiscTest::testTdf119956 is also failing. Any ideas why this test wo

Re: CppunitTest_starmath_qa_cppunit Failing on Windows with HiDPI screens

-Luke From: Noel Grandin Sent: Sunday, May 19, 2019 6:22 AM To: Luke Benes Cc: noel.gran...@collabora.co.uk; Libreoffice Dev List Subject: Re: CppunitTest_starmath_qa_cppunit Failing on Windows with HiDPI screens should be fixed with https://cgit.freedesktop.org/libreoffice/core/commi

CppunitTest_starmath_qa_cppunit Failing on Windows with HiDPI screens

After commit: https://cgit.freedesktop.org/libreoffice/core/commit/?id=13894996601d handle empty Rectangle better in starmath Windows builds on machines with display scaling enabled are failing. In my testing only a 100% scale factor is working. Here is a sample build log with Display Scale =

Re: Clang trunk build failure in external/librevenge

Stephan, Comparing to a good workdir/UnpackedTarball/librevenge/config.log, This seems to be the problem: In file included from /core/workdir/UnpackedTarball/boost/boost/spirit/home/classic/attribute/closure.hpp:24: /core/workdir/UnpackedTarball/boost/boost/spirit/home/classic/phoenix/operators.h

Jenkins_Callgrind failing with error: use of deleted function

After commit: https://cgit.freedesktop.org/libreoffice/core/commit/?id=a361231b1363 fix wrong SET/QUERY flags passed to uno::Reference Jenkins_Callgrind is failing with the following error: /lo_callgrind_linux/sc/qa/perf/scperfobj.cxx:623:87: error: use of deleted function ‘com::sun::star::uno:

Clang trunk build failure in external/librevenge

After commit: http://llvm.org/viewvc/llvm-project?view=revision&revision=360308 Clang builds are failing on both Arch and Ubuntu with the following error: checking for boost/spirit/include/classic.hpp... no configure: error: Required boost headers not found. make[1]: *** [/core/external/libreveng

Re: Gitiles VCS browser

Guilthem, Why have you not answered my question about returning the Commit Bot back to cgit? Gitiles is wasting our time. For example, just now I followed the commit bot link on tdf#42949 to https://gerrit.libreoffice.org/plugins/gitiles/core/+log/63a25b79f18fda29cd744add813ce9508c69b996/sw/s

Re: Gitiles VCS browser

It is telling that when I asked what you prefer, you answered that the extraneous information “doesn't hurt “. Your tolerance to noise may be higher than many, but it’s a well-established fact the less clutter in the UI, the faster it is for humans to use.  Gitiles is fails here, takes longer to

Re: Gitiles VCS browser

Mike, That is not an apples to apples comparison. In your browser open and compare side-by-side: https://git.libreoffice.org/core/+/6a9cf9ba2d37fee9b7c2f190b347e0d7c4a2676a and https://cgit.freedesktop.org/libreoffice/core/commit/?id=6a9cf9ba2d37fee9b7c2f190b347e0d7c4a2676a Do you really like al

Re: Gitiles VCS browser

Guilhem, There is something wrong with your benchmark methodology. This cgit page loads in under 1 second: https://cgit.freedesktop.org/libreoffice/core/log/sw/source/filter/ww8/docxattributeoutput.cxx?ofs=50 While https://gerrit.libreoffice.org/plugins/gitiles/core/+log/2d6f8c36126effc66ea35af

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

Switching to hub redirection solves the annoying symbols that Gitiles appends to URLs leading to copy and paste errors and the timestamp issue. But it does not address: * Lack of Built-in, easy to use search functionality * Lack of branch tags, allowing you to see what release you are on when go

Japanese and Korean Fonts Requirements for building on Arch

On a fresh install of Arch, I installed the https://wiki.documentfoundation.org/Development/Linux_Build_Dependencies requirements. During the build I get the following notification: Additional Fonts Required An application is requesting additional fonts. Clicking on the notification, the Soft

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

Could you please change the Commit Notification bot back to cgit? In the 6 months, that I have been testing gitiles, I have found no advantages and many disadvantages over cgit. In general, it presents information in an inferior way and it’s URL’s have led to multiple copy and paste errors, c

CppunitTest_chart2_dump Unit Test Failure

Hey Mike, After https://cgit.freedesktop.org/libreoffice/core/commit/?id=166a4989a0d1e5a6271c66bceb73a27970afc882 tdf#123504: 0 and 360 are different angles in charts My 32-bit Windows box is failing with the following error: ChartDataTest::verify finished in: 2796ms PivotChartDataButtonTest::

Cygwin 3.0.0-1 Released

Info on this major release can be found here: https://cygwin.com/ml/cygwin/2019-02/msg00229.html Do any of these improvements look beneficial to LibreOffice?  ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/ma

Windows Unit TestSwLayoutWriter::testBtlrCell Failing

Ever since: https://cgit.freedesktop.org/libreoffice/core/commit/?id=a0bb480364c80192111ecab3501d63584e651ea3 or https://cgit.freedesktop.org/libreoffice/core/commit/?id=bef3818dbedba467a257e2573e298d98062be37b The build is failing with: C:/core/test/source/xmltesttools.cxx:139:SwLayoutWriter::t

Re: Bug around legend of a pie chart

There are many legend/title overlapping import issues on the bug tracker. The only universal solution will be to teach the chart engine the concept of not allowing overlapping legend/title and allow the importers to use this. Awhile back Markus made some progress in this area. The basic work has

CppunitTest_chart2_xshape Failure with Display Scaling on Windows

Mike, The fix for Bug 121685, https://cgit.freedesktop.org/libreoffice/core/commit/?id=7263d223ddf4 ​ Is causing the core Unit Test CppunitTest_chart2_xshape to fail when you set, Settings->Display->Scale=125%​ ​ Setting Scale=100% all

Subsequent Unit Test CppunitTest_sc_ddelinkobj Failing Under Windows

'make check' builds are failing on both of my Windows 10 boxes are failing after: https://cgit.freedesktop.org/libreoffice/core/commit/?id=63ff8602c16b tdf#45904 Move XRefreshable Java tests to C++ With this failure: https://pastebin.com/bvafeEUv [build CUT] sc_ddelinkobj D:/core/test/source

Windows build failure - C2131: expression did not evaluate to a constant

After commit: https://cgit.freedesktop.org/libreoffice/core/commit/?id=644188bf7f3a Compute (un-)premultiply_table at compile time I'm seeing the following build failure on Windows 32-bit release build: D:/core/vcl/source/bitmap/BitmapTools.cxx(1078): error C2131: expression did not evaluate

Tinberbox MacOSX-x86_64_49-TDF failure - ld: file not found

In this range: https://cgit.freedesktop.org/libreoffice/core/log/?qt=range&q=313a0efb1d703a36030a7e5e55bd308c7e4650f3..ae3309c908311248f1580a894f197732964bfac2 @49 started failing with: https://tinderbox.libreoffice.org/cgi-bin/gunzip.cgi?tree=MASTER&full-log=1543237201.21995 [build

Re: JunitTest_forms_unoapi_3 failing on Windows

Unfortunately, the patch did not work. On both my win10 laptop and desktop, I'm still seeing a JunitTest_forms_unoapi_3 failure with a 'make check' on master. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/

JunitTest_forms_unoapi_3 failing on Windows

Stephan, After commit: https://cgit.freedesktop.org/libreoffice/core/commit/?id=d5ed903618f2 Set CppunitTest-related env vars only during CppunitTest I'm seeing Windows 'make check' fail with: There were 2 failures: 1) test(org.openoffice.test.UnoApiTest) com.sun.star.lang.DisposedException

Seg fault on Windows in xmlsecurity_signing Unit Test

Both my Windows box and @42 and @62 are failing with the following error: [build CUT] xmlsecurity_pdfsigning /usr/bin/sh: line 1: 8100 Segmentation fault ( PATH="C:\core\instdir\program;C:\core\instdir\program;C:\core\workdir\LinkTarget\Library;C:\core\workdir\UnpackedTarball\cppunit\src\cpp

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

Now that gitiles is linked to bugzilla instead of cgit, I'm giving it a good workout. From a QA perspective, it's missing 2 key features that interfere with my workflow. The date gitiles displays in the log is the author date, rather than the much more useful commit date. When trying to track

Re: Cppcheck: Reduction of False Positives: Manual Approach

> It was mentioned that the correct way is to generate the proper project > structure for cppcheck using our existing tools that generate IDE > integrations (and they have correct include correct includes, deps and all). Mike, Yes, agreed. But AFAIK, no one other than me is looking into this. Qui

Re: Cppcheck: Reduction of False Positives: Manual Approach

> Was it not you how came up with the idea to reduce the false positives with > specifying the includes? No, it was not my idea. On #cppcheck, I was told by danmar, the primary developer of cppcheck, that our script is using cppcheck incorrectly. Without being passed the same include location

Re: Cppcheck: Reduction of False Positives: Manual Approach

In my first attempt to improve the quality of the cppcheck reports, Tamás Zolnai pointed out that including every possible header resulted in some valid warnings not being reported. Instead, how about just including only our primary include folder of ./include with the '-Iinclude' parameter? T

After loplugin:staticvar in various, Jenkins_MacOSX failing

After https://cgit.freedesktop.org/libreoffice/core/commit/?id=76dd28afc9c0 loplugin:staticvar in various Jenkins_MacOSX is failing with: toolkit/source/awt/vclxtoolkit.cxx:764:6: error: unused function ´ComponentInfoCompare´ [-Werror,-Wunused-function] 895 bool ComponentInfoCompare( c

After loplugin:staticvar in sw, Jenkins_Windows_Dbg failing

After https://cgit.freedesktop.org/libreoffice/core/commit/?id=4ba5b003b594f9eb6c9b185208bdb72aef8273d0 loplugin:staticvar in sw Jenkins_Windows_Dbg failing with 9 NEXT C:/cygwin/home/tdf/lode/jenkins/workspace/lo_tb_master_win_dbg/sw/source/filter/html/svxcss1.cxx(3166): error C2065: ´CS

Tinderbox @71 now failing with undefined reference to `SvMemoryStream::remainingSize()´

After https://cgit.freedesktop.org/libreoffice/core/commit/?id=b2cefc2e36925b4384eb0aea54aa2c6bcfb018a8 Most of the Linux tinderboxes went red. This was fixed by https://cgit.freedesktop.org/libreoffice/core/commit/?id=49c87270f7176312806d1759967c247a312f0acf But @71 is still to failing with:

Re: how to set JAVA_HOME

I first noticed this same error in Arch after a Java version upgrade. Then again after I upgraded Ubuntu from 16.04 to 180.4. My guess is that either this is an error in our autogen.sh Java detection logic or there was a change in the Java installer between Java 8 and Java 10. _

CppunitTest_sc_filters_test now failing on Jenkins_MacOSX

It appears that a commit in this range: https://cgit.freedesktop.org/libreoffice/core/log/?qt=range&q=f6eee4f7966e09be82b51554ead4c4aac8c47457..9388d9b5d3bdbd649d164deb97cae756bb1d3de3 is causing: Jenkins_MacOSX to fail with 1030 NEXTError: a unit test failed, please do one of: 1035

Re: Cppcheck: Reduction of False Positives: Manual Approach

Maarten, Thanks for your suggestion here and your earlier contributions to the Cppcheck Report. I agree that we should create the include file dynamically. However the approach used by your script seems like overkill. Cppcheck already finds that quoted includes like #include "GraphicExportFilter

Intermittent Unit Test Failure: VclComplexTextTest::testArabic

Over the years, I've probably done several hundred windows builds. Until now I have never been bitten an intermittent Unit Test failures. This month, I have started to see fairly regular failure of VclComplexTextTest::testArabic 3 out of ~15 builds. Here are 2 separate examples of the Jenkins_W

Re: Cppcheck: Reduction of False Positives: Manual Approach

As I mentioned before, by manually specifying  includes and preprocessor configurations, I was able to reduce the number of warning from ~9000 to 30. https://drive.google.com/file/d/1Ai_Zcj18cdQxVIQESb4lJr5K9LnzjnpW/view?usp=sharing You can view it by unzipping and opening 'index.html'. Caolán

Re: Hello, I am Interested in Helping Libre Office

Thanks for your offer to help with LibreOffice. Based on your experience you could help us with QA and documentation. First, I would recommend you create an account in Bugzilla [1], where all bugs are reported and triaged. Then, depending on your interests, you can either start helping with

Re: clang-8: error: unknown argument: '-flto-partition=none' when building lxml

> uses $$CFLAGS (i.e., whathever the CFLAGS env var is set to in the shell run by `make`) It's not coming from shell CFLAGS. I have searched all shell and environment variables with: $( set -o posix ; set ) | less And nothing has a '-flto-partition=none' Any other ideas on where to find this

Jenkins_Callgrind failing on CppunitTest_sw_layoutwriter and CppunitTest_sw_uiwriter

Some commit in this range: https://cgit.freedesktop.org/libreoffice/core/log/?id=e625c64575216f787d7f534b90b6a7e7f981849f&qt=range&q=761308edb65a6cf44ef84cebc387e77af8b70f83..e625c64575216f787d7f534b90b6a7e7f981849f Has caused all recent Callgrind builds to fail with this error: https://tinderbox.

Cppcheck: Reduction of False Positives: Manual Approach

By manually specifying includes and preprocessor configurations, I was able to reduce the number of warning from ~9000 to 30. https://drive.google.com/file/d/1Ai_Zcj18cdQxVIQESb4lJr5K9LnzjnpW/view?usp=sharing You can view it by unzipping and opening 'index.html'.Did this uncover any valid issu

Best way to handle oddball header #includes for Cppcheck Report?

I am in the process of teaching cppcheck about our source tree. So far I have reduced the number of warnings from ~9000 to ~100. In order for our weekly Cppcheck Report to benefit from these, I need to automate the process. Here is the command I used to list all of our include directories: $ f

  1   2   >