Mailing List Archive: Gentoo: User

Anyone compiled libreoffice-3.6.0.4 yet?

Index | Next | Previous | View Threaded

w41ter at gmail

Aug 9, 2012, 1:19 PM

Post #1 of 13 (548 views)
Permalink

Anyone compiled libreoffice-3.6.0.4 yet?

This has been slow and painful so far.

First, the build stops repeatedly because of zero-length library files.
I can restart the ebuild manually and each iteration builds one more
(real) library. I've been doing this iterating for hours and I think
I may have gotten past that part, but the build is far from done...

Second, the ebuild is using only one CPU out of four, so this is taking
much longer than before. Ugh.

Anyone else seeing these problems?

wonko at wonkology

Aug 9, 2012, 1:36 PM

Post #2 of 13 (536 views)
Permalink

Re: Anyone compiled libreoffice-3.6.0.4 yet? [In reply to]

walt writes:

> This has been slow and painful so far.
>
> First, the build stops repeatedly because of zero-length library files.
> I can restart the ebuild manually and each iteration builds one more
> (real) library. I've been doing this iterating for hours and I think
> I may have gotten past that part, but the build is far from done...
>
> Second, the ebuild is using only one CPU out of four, so this is taking
> much longer than before. Ugh.
>
> Anyone else seeing these problems?

No, I just built it today, in the usual time of about 2.5 hours.

Wonko

lists at xunil

Aug 9, 2012, 1:58 PM

Post #3 of 13 (534 views)
Permalink

Re: Anyone compiled libreoffice-3.6.0.4 yet? [In reply to]

Am 09.08.2012 22:36, schrieb Alex Schuster:

> No, I just built it today, in the usual time of about 2.5 hours.

~1 hr here :-P

(I *had* to say that ;-) )

jmontier at gmail

Aug 9, 2012, 2:07 PM

Post #4 of 13 (539 views)
Permalink

Re: Anyone compiled libreoffice-3.6.0.4 yet? [In reply to]

2012/8/9 Stefan G. Weichinger <lists [at] xunil>

> Am 09.08.2012 22:36, schrieb Alex Schuster:
>
> > No, I just built it today, in the usual time of about 2.5 hours.
>
> ~1 hr here :-P
>
> (I *had* to say that ;-) )
>
>
>

Hello,

No problem building libreoffice-3.6.0.4.
About 1h 38 min.

Best regards

--
Jacques

paul.hartman+gentoo at gmail

Aug 9, 2012, 3:43 PM

Post #5 of 13 (535 views)
Permalink

Re: Anyone compiled libreoffice-3.6.0.4 yet? [In reply to]

On Thu, Aug 9, 2012 at 3:19 PM, walt <w41ter [at] gmail> wrote:
> This has been slow and painful so far.
>
> First, the build stops repeatedly because of zero-length library files.
> I can restart the ebuild manually and each iteration builds one more
> (real) library. I've been doing this iterating for hours and I think
> I may have gotten past that part, but the build is far from done...
>
> Second, the ebuild is using only one CPU out of four, so this is taking
> much longer than before. Ugh.
>
> Anyone else seeing these problems?

No problem here, either. It needs a huge amount of temp disk space, be
sure you're not running out (especially if it is on /dev/shm for
example).

w41ter at gmail

Aug 10, 2012, 6:02 AM

Post #6 of 13 (572 views)
Permalink

Re: Anyone compiled libreoffice-3.6.0.4 yet? [SOLVED, maybe] [In reply to]

On 08/09/2012 01:19 PM, walt wrote:

>
> ...the ebuild is using only one CPU out of four, so this is taking
> much longer than before. Ugh.

Well, since there are at least four of you who don't have any problem
with libreoffice it must be something on my two machines with the same
trouble.

This morning I noticed that perl was updated, so I ran perl-updater
and now the libreoffice build seems (fingers crossed) to be building
at normal speed using all CPUs again.

The reason I think it was a perl problem is there are multiple processes
going during a libreoffice build that look like this:

perl -S /var/tmp/portage/app-office/libreoffice-3.6.0.4/work/libreoffice-core-3.6.0.4/solenv

Before I ran perl-updater there was always one process marked <defunct> at
the bottom of that list of perl processes, and now there seem to be four
parallel perl processes in place of that <defunct> one -- I guess one for
each CPU :)

I'll let the build run while I go to work, hoping I have a working
libreoffice when I get home.

Thanks for the feedback.

v_2e at ukr

Aug 12, 2012, 1:50 AM

Post #7 of 13 (542 views)
Permalink

Re: Anyone compiled libreoffice-3.6.0.4 yet? [In reply to]

Hello!
In contrast to previous speakers with more or less successful
LibreOffice 3.6.0.4 build, on my machine it does not build at all.
After >10 hours of compiling (which is a bit longer than a usual time
for 3.5) it said:
-----------------------------------------------------------------------
Oh dear - something failed during the build - sorry !
For more help with debugging build errors, please see the section in:
http://wiki.documentfoundation.org/Development

And the build log says:
########## Quote start ##########
...
subsequent_filters-test.cxx:740:Assertion
Test name: ScFiltersTest::testPasswordOld
assertion failed
- Expression: xDocSh.Is()
- Failed to load password.ods

subsequent_filters-test.cxx:740:Assertion
Test name: ScFiltersTest::testPasswordNew
assertion failed
- Expression: xDocSh.Is()
- Failed to load password.ods

Failures !!!
Run: 18 Failure total: 2 Failures: 2 Errors: 0

Error: a unit test failed, please do one of:

export DEBUGCPPUNIT=TRUE # for exception catching
export GDBCPPUNITTRACE="gdb --args" # for interactive debugging
export VALGRIND=memcheck # for memory checking
and retry.
########### Quote end ###########

So, can anyone suggest a way to fix it?

Thanks!
Vladimir

-----
<v_2e [at] ukr>

v_2e at ukr

Aug 12, 2012, 3:53 AM

Post #8 of 13 (543 views)
Permalink

Re: Anyone compiled libreoffice-3.6.0.4 yet? [In reply to]

Looks like developers have already caught this issue.
https://bugs.gentoo.org/show_bug.cgi?id=428328#c8

On Sun, 12 Aug 2012 11:50:31 +0300
v_2e [at] ukr wrote:

> Hello!
> In contrast to previous speakers with more or less successful
> LibreOffice 3.6.0.4 build, on my machine it does not build at all.
> After >10 hours of compiling (which is a bit longer than a usual
> time for 3.5) it said:
> -----------------------------------------------------------------------
> Oh dear - something failed during the build - sorry !
> For more help with debugging build errors, please see the section
> in: http://wiki.documentfoundation.org/Development
>
>
> And the build log says:
> ########## Quote start ##########
> ...
> subsequent_filters-test.cxx:740:Assertion
> Test name: ScFiltersTest::testPasswordOld
> assertion failed
> - Expression: xDocSh.Is()
> - Failed to load password.ods
>
> subsequent_filters-test.cxx:740:Assertion
> Test name: ScFiltersTest::testPasswordNew
> assertion failed
> - Expression: xDocSh.Is()
> - Failed to load password.ods
>
> Failures !!!
> Run: 18 Failure total: 2 Failures: 2 Errors: 0
>
> Error: a unit test failed, please do one of:
>
> export DEBUGCPPUNIT=TRUE # for exception catching
> export GDBCPPUNITTRACE="gdb --args" # for interactive debugging
> export VALGRIND=memcheck # for memory checking
> and retry.
> ########### Quote end ###########
>
> So, can anyone suggest a way to fix it?
>
> Thanks!
> Vladimir
>
> -----
> <v_2e [at] ukr>

-----
<v_2e [at] ukr>

purslow at ca

Aug 12, 2012, 7:33 AM

Post #9 of 13 (615 views)
Permalink

Re: Anyone compiled libreoffice-3.6.0.4 yet? [In reply to]

120812 v_2e [at] ukr wrote:
> Looks like developers have already caught this issue.
> https://bugs.gentoo.org/show_bug.cgi?id=428328#c8

After nearly 3 hr compiling (previously 2 h 32 m ), it failed with :

-----------------------------------------------------------------------
Oh dear - something failed during the build - sorry !
For more help with debugging build errors, please see the section in:
http://wiki.documentfoundation.org/Development

internal build errors:

ERROR: error 512 occurred while making /z/tmp/portage/app-office/libreoffice-3.6.0.4/work/libreoffice-core-3.6.0.4/tail_build/prj

it seems that the error is inside 'tail_build', please re-run build
inside this module to isolate the error and/or test your fix:

build_error.log should contain the captured output of the failed module(s)

-----------------------------------------------------------------------
To rebuild a specific module:

make tail_build.clean # not recommended, this will re-build almost everything
make tail_build

when the problem is isolated and fixed, re-run 'make'
make[1]: *** [build-packimages] Error 1
make[1]: Leaving directory `/z/tmp/portage/app-office/libreoffice-3.6.0.4/work/libreoffice-core-3.6.0.4'
make: *** [build] Error 2
* ERROR: app-office/libreoffice-3.6.0.4 failed (compile phase):
* (no error message)
*
* Call stack:
* ebuild.sh, line 85: Called src_compile
* environment, line 8980: Called die
* The specific snippet of code:
* make build || die
*
* If you need support, post the output of `emerge --info '=app-office/libreoffice-3.6.0.4'`,
* the complete build log and the output of `emerge -pqv '=app-office/libreoffice-3.6.0.4'`.
!!! When you file a bug report, please include the following information:
GENTOO_VM= CLASSPATH="" JAVA_HOME=""
JAVACFLAGS="" COMPILER=""
and of course, the output of emerge --info
* The complete build log is located at '/var/log/emerge-logs/app-office:libreoffice-3.6.0.4:20120812-112934.log'.
* For convenience, a symlink to the build log is located at '/z/tmp/portage/app-office/libreoffice-3.6.0.4/temp/build.log'.
* The ebuild environment file is located at '/z/tmp/portage/app-office/libreoffice-3.6.0.4/temp/environment'.
* Working directory: '/z/tmp/portage/app-office/libreoffice-3.6.0.4/work/libreoffice-core-3.6.0.4'
* S: '/z/tmp/portage/app-office/libreoffice-3.6.0.4/work/libreoffice-core-3.6.0.4'

I'll try merging again with USE="xmlsec", as the bug fix recommends.

--
========================,,============================================
SUPPORT ___________//___, Philip Webb
ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto
TRANSIT `-O----------O---' purslowatchassdotutorontodotca

purslow at ca

Aug 12, 2012, 10:44 AM

Post #10 of 13 (528 views)
Permalink

Re: Anyone compiled libreoffice-3.6.0.4 yet? [In reply to]

120812 Philip Webb wrote:
> 120812 v_2e [at] ukr wrote:
>> Looks like developers have already caught this issue.
>> https://bugs.gentoo.org/show_bug.cgi?id=428328#c8
> I'll try merging again with USE="xmlsec" , as the bug fix recommends.

Yes, it compiled with that flag.
While it used less memory than 2 emerges ago,
it used more disk space ( 4 GB ) & took much longer ( 3 h 2 m ).
OTOH it also opens almost at once, so I'll take the trade-offs.

--
========================,,============================================
SUPPORT ___________//___, Philip Webb
ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto
TRANSIT `-O----------O---' purslowatchassdotutorontodotca

w41ter at gmail

Aug 12, 2012, 11:01 AM

Post #11 of 13 (521 views)
Permalink

Re: Anyone compiled libreoffice-3.6.0.4 yet? [In reply to]

On 08/12/2012 10:44 AM, Philip Webb wrote:
> 120812 Philip Webb wrote:
>> 120812 v_2e [at] ukr wrote:
>>> Looks like developers have already caught this issue.
>>> https://bugs.gentoo.org/show_bug.cgi?id=428328#c8
>> I'll try merging again with USE="xmlsec" , as the bug fix recommends.
>
> Yes, it compiled with that flag.
> While it used less memory than 2 emerges ago,
> it used more disk space ( 4 GB ) & took much longer ( 3 h 2 m ).
> OTOH it also opens almost at once, so I'll take the trade-offs.

I'm glad to hear that because I'm still failing to build it on three
machines :(

Did you add xmlsec to your make.conf, or use it in the command line when
emerging libreoffice?

purslow at ca

Aug 12, 2012, 3:24 PM

Post #12 of 13 (520 views)
Permalink

Re: Re: Anyone compiled libreoffice-3.6.0.4 yet? [In reply to]

120812 walt wrote:
> On 08/12/2012 10:44 AM, Philip Webb wrote:
>> Yes, it compiled with USE="xmlsec" .
>> While it used less memory than 2 emerges ago,
>> it used more disk space ( 4 GB ) & took much longer ( 3 h 2 m ).
>> OTOH it also opens almost at once, so I'll take the trade-offs.
> I'm glad to hear that
> because I'm still failing to build it on 3 machines.
> Did you add xmlsec to your make.conf
> or use it in the command line when emerging libreoffice?

No, I would never add a temporary fix to make.conf !
I entered 'USE="xmlsec" emergeu libreoffice',
where 'emergeu' is an alias for 'ACCEPT_KEYWORDS="~amd64" emerge'
(yes, I know, howls of horror from the bystanders,
but I've been doing it that way for years without problems).
I was surprised, as the error msg I got was different
from the one quoted earlier in the thread & in the bug.

--
========================,,============================================
SUPPORT ___________//___, Philip Webb
ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto
TRANSIT `-O----------O---' purslowatchassdotutorontodotca

w41ter at gmail

Aug 18, 2012, 6:46 AM

Post #13 of 13 (453 views)
Permalink

Re: Anyone compiled libreoffice-3.6.0.4 yet? [WORKAROUND] [In reply to]

On 08/09/2012 01:19 PM, walt wrote:
> This has been slow and painful so far.
>
> First, the build stops repeatedly because of zero-length library files.

The gentoo libreoffice package doesn't yet compile with the 'binfilter'
useflag set, so I unset it and the install completed.

> Second, the ebuild is using only one CPU out of four, so this is taking
> much longer than before. Ugh.

This is a completely separate problem, which is very annoying but not
fatal. There are some parts of the libreoffice build which take much
longer than normal because 'make' uses 100% of CPU for long periods,
while accomplishing very little. Those sections eventually complete,
and the rest of the build proceeds at full speed by using all four of
the CPU's.

I think the reason that 'make' is being so slow is that certain kinds
of child processes are segfaulting (i.e. become 'defunct') and make
has to stop and respawn the failed processes until they succeed, which
obviously takes a lot of extra time. The build does eventually finish
in spite of all those defunct processes -- no idea why it works in the
end, though.

Can anyone confirm that 'make' is behaving the same way for you while
building libreoffice-3.6.0.4?

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads