Re: [gentoo-user] Anyone compiled libreoffice-3.6.0.4 yet?

2012-08-12 Thread v_2e
  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...@ukr.net



Re: [gentoo-user] Anyone compiled libreoffice-3.6.0.4 yet?

2012-08-12 Thread v_2e
  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...@ukr.net 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...@ukr.net


- 
 v...@ukr.net



Re: [gentoo-user] Anyone compiled libreoffice-3.6.0.4 yet?

2012-08-12 Thread Philip Webb
120812 v...@ukr.net 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




Re: [gentoo-user] Anyone compiled libreoffice-3.6.0.4 yet?

2012-08-12 Thread Philip Webb
120812 Philip Webb wrote:
 120812 v...@ukr.net 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




[gentoo-user] Anyone compiled libreoffice-3.6.0.4 yet?

2012-08-09 Thread walt
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?




Re: [gentoo-user] Anyone compiled libreoffice-3.6.0.4 yet?

2012-08-09 Thread Alex Schuster
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



Re: [gentoo-user] Anyone compiled libreoffice-3.6.0.4 yet?

2012-08-09 Thread Stefan G. Weichinger
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 ;-) )




Re: [gentoo-user] Anyone compiled libreoffice-3.6.0.4 yet?

2012-08-09 Thread Jacques Montier
2012/8/9 Stefan G. Weichinger li...@xunil.at

 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


Re: [gentoo-user] Anyone compiled libreoffice-3.6.0.4 yet?

2012-08-09 Thread Paul Hartman
On Thu, Aug 9, 2012 at 3:19 PM, walt w41...@gmail.com 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).