Hi,
On Sat, Feb 20, 2016 at 02:52:45PM +1100, Chris Sherlock wrote:
> Is it worthwhile asking the RHEL guys to consider creating a Harfbuzz package?
>
> From a comment in that bug I believe the only reason we now statically link
> Harfbuzz is because RHEL doesn't have a package. Previously we al
Is it worthwhile asking the RHEL guys to consider creating a Harfbuzz package?
From a comment in that bug I believe the only reason we now statically link
Harfbuzz is because RHEL doesn't have a package. Previously we also did it was
because of ABI stability issues, but these are apparently no l
On 19.02.2016 10:10, Khaled Hosny wrote:
> On Thu, Feb 18, 2016 at 02:36:48PM +0100, Michael Stahl wrote:
>> On 18.02.2016 14:17, Khaled Hosny wrote:
>>> I don’t think it is just the unit test that is failing, running the
>>> application will most likely crash as well. Building with system
>>> Harf
On Thu, Feb 18, 2016 at 02:36:48PM +0100, Michael Stahl wrote:
> On 18.02.2016 14:17, Khaled Hosny wrote:
> > I don’t think it is just the unit test that is failing, running the
> > application will most likely crash as well. Building with system
> > HarfBuzz should fix the issue, until a better fi
Sure Khaled. I would try running it with system harfbuzz as it is mentioned
in the bug report.
Regards,
Pranav
On Thu, Feb 18, 2016 at 6:47 PM, Khaled Hosny wrote:
> I don’t think it is just the unit test that is failing, running the
> application will most likely crash as well. Building with s
On 18.02.2016 14:17, Khaled Hosny wrote:
> I don’t think it is just the unit test that is failing, running the
> application will most likely crash as well. Building with system
> HarfBuzz should fix the issue, until a better fix is found.
commit 549130ab5d9616f7eb5504db31546b386737ccb2 on master
I don’t think it is just the unit test that is failing, running the
application will most likely crash as well. Building with system
HarfBuzz should fix the issue, until a better fix is found.
Regards,
Khaled
On Thu, Feb 18, 2016 at 06:37:37PM +0530, Pranav Ganorkar wrote:
> Hi,
>
> I want to as
Hi,
I want to ask if there is some switch for temporarily disabling these unit
tests.
I am building it on a 64-bit Archlinux machine.
Regards,
Pranav
On Thu, Feb 18, 2016 at 3:24 PM, Khaled Hosny wrote:
> On Thu, Feb 18, 2016 at 10:39:40AM +0100, Stephan Bergmann wrote:
> > On 02/17/2016 05:4
On Thu, Feb 18, 2016 at 10:39:40AM +0100, Stephan Bergmann wrote:
> On 02/17/2016 05:47 PM, Pranav Ganorkar wrote:
> >Program received signal SIGSEGV, Segmentation fault.
> >0x2aaab93213d3 in ?? () from /usr/lib/libharfbuzz.so.0
> >(gdb) bt
> >#0 0x2aaab93213d3 in ?? () from /usr/lib/libha
On 02/17/2016 05:47 PM, Pranav Ganorkar wrote:
Program received signal SIGSEGV, Segmentation fault.
0x2aaab93213d3 in ?? () from /usr/lib/libharfbuzz.so.0
(gdb) bt
#0 0x2aaab93213d3 in ?? () from /usr/lib/libharfbuzz.so.0
#1 0x2aaab1962f63 in hb_font_funcs_set_glyph_v_origin_func (
Hi,
Using gdb , the backtrace I obtain is:
**
warning: File "/mnt/D-Drive/LibreOffice/libreoffice/instdir/program/
libuno_sal.so.3-gdb.py" auto-loading has been declined by your `auto-load
safe-path' set to "$debugdir:$datadir/auto-load"
On 17.02.2016 16:20, Dennis Roczek wrote:
> please check the thread "Unit test failure on building LibreOffice on
> Windows" from yesterday. I really guess it contains the same problem:
> wrong Visual Studio version plus wrong compiling flags.
i suggest that the problems are unrelated and that cal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Pranav,
please check the thread "Unit test failure on building LibreOffice on
Windows" from yesterday. I really guess it contains the same problem:
wrong Visual Studio version plus wrong compiling flags.
Regards,
Dennis Roczek
Am 17.02.2016 um
On 02/17/2016 01:28 PM, Pranav Ganorkar wrote:
make CppunitTest_svgio CPPUNITTRACE="gdb --args"
***
make -j 4 -rs -f /mnt/D-Drive/LibreOffice/libreoffice/Makefile.gbuild
CppunitTest_svgio
[CUT] svgio
GNU gdb (GDB) 7.10.1
Copyright
Hi, When I try the 'bt' command as suggested by Micheal, the following is
the output:
make CppunitTest_svgio CPPUNITTRACE="gdb --args"
***
make -j 4 -rs -f /mnt/D-Drive/LibreOffice/libreoffice/Makefile.gbuild
CppunitTest_svgio
[CUT
On 16.02.2016 18:05, Pranav Ganorkar wrote:
> Hi, I am trying to build Libreoffice on linux but it fails at this point:
> /bin/sh: line 1: 23247 Segmentation fault (core dumped)
well clearly it crashed, only question is why...
> Error: a unit test failed, please do one of:
> make CppunitTes
Hi Pranav,
you write:
> No core file identified in directory
> /mnt/D-Drive/LibreOffice/libreoffice/workdir/CppunitTest/svgio.test.core
> To show backtraces for crashes during test execution,
> enable core files with:
>
>ulimit -c unlimited
>
> [CUT] vcl_timer
>
> Error: a unit test failed,
17 matches
Mail list logo