Re: editors/libreoffice:internal build errors: ERROR: error 65280 occurred while making /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/vcl/prj

2012-05-31 Thread Jens Jahnke
Hi,

On Fri, 04 May 2012 14:12:17 +0200
Hartmann, O. ohart...@zedat.fu-berlin.de wrote:

HO I found myself incapable of rebuilding/updating editors/libreoffice
HO on ALL FreeBSD 9-STABLE and FreeBSD 10-CURRENT (amd64) platforms
HO with the very same error message as shown below.

I ran into the same issue on my 9-STABLE box at home today.
If I follow the steps provides in the error message it compiles a bit
further and gives the exact same error message some modules later.
Anyhow I stepped through them and finally got another error message:

---snip---
[ build CUT ] lotuswordpro_test_lotuswordpro
R=/usr/ports/editors/libreoffice/work  S=$R/libreoffice-core-3.5.2.2
 O=$S/solver/unxfbsd.pro  W=$S/workdir/unxfbsd.pro   mkdir -p
$W/CppunitTest/  (LD_LIBRARY_PATH=$O/lib:$O/lib/sqlite
DBGSV_ERROR_OUT=shell STAR_RESOURCEPATH=$O/bin/
$O/bin/cppunit/cppunittester
$W/LinkTarget/CppunitTest/libtest_lotuswordpro_test_lotuswordpro.so
--headless --protector unoexceptionprotector.so unoexceptionprotector
-env:CONFIGURATION_LAYERS=xcsxcu:file://$O/xml/registry
-env:UNO_TYPES= file://$O/bin/udkapi.rdb  file://$O/bin/types.rdb
-env:UNO_SERVICES=file://$O/xml/ure/services.rdb
file://$O/xml/component/lotuswordpro/util/lwpfilter.component
file://$O/xml/configmgr.component  file://$O/xml/ucb1.component
file://$O/xml/ucpfile1.component
-env:URE_INTERNAL_LIB_DIR=file://$O/lib  -env:LO_LIB_DIR=file://$O/lib
 $W/CppunitTest/lotuswordpro_test_lotuswordpro.test.log 21 || 
(cat $W/CppunitTest/lotuswordpro_test_lotuswordpro.test.log  echo;
echo Error: a unit test failed, please do one of:; echo; echo export
DEBUGCPPUNIT=TRUE# for exception catching; echo export
GDBCPPUNITTRACE=\gdb --args\ # for interactive debugging; echo
export VALGRIND=memcheck# for memory checking ; echo and
retry.  false))

Abort trap (core dumped) File tested,Test
Result,Execution Time (ms)
file:///usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/lotuswordpro/qa/cppunit/data/pass/A14.lwp,Signal
11 during cups initialization called, ignoring cups

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.
gmake: ***
[/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/workdir/unxfbsd.pro/CppunitTest/lotuswordpro_test_lotuswordpro.test]
Error 1
---snip---

The mysterious thing is that I have a nearly identical box at the office
running 9-STABLE and there libreoffice compiles fine.
It only differs in two hardware components:
CPU is core2 at home and core5i at the office.
RAM is 4gb at home and 8gb at the office.

System on both is clean installed and updated 9-STABLE.

So maybe this is a memory/cpu issue?

Regards,

Jens

-- 
31. Wonnemond 2012, 19:29
Homepage : http://www.jan0sch.de

I can resist anything but temptation.


pgpMlDoVbuRz9.pgp
Description: PGP signature


Re: editors/libreoffice:internal build errors: ERROR: error 65280 occurred while making /usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/vcl/prj

2012-05-31 Thread Leslie Jensen



2012-05-31 19:35, Jens Jahnke skrev:

Hi,

On Fri, 04 May 2012 14:12:17 +0200
Hartmann, O.ohart...@zedat.fu-berlin.de  wrote:

HO  I found myself incapable of rebuilding/updating editors/libreoffice
HO  on ALL FreeBSD 9-STABLE and FreeBSD 10-CURRENT (amd64) platforms
HO  with the very same error message as shown below.

I ran into the same issue on my 9-STABLE box at home today.
If I follow the steps provides in the error message it compiles a bit
further and gives the exact same error message some modules later.
Anyhow I stepped through them and finally got another error message:

---snip---
[ build CUT ] lotuswordpro_test_lotuswordpro
R=/usr/ports/editors/libreoffice/work  S=$R/libreoffice-core-3.5.2.2
  O=$S/solver/unxfbsd.pro  W=$S/workdir/unxfbsd.pro   mkdir -p
$W/CppunitTest/  (LD_LIBRARY_PATH=$O/lib:$O/lib/sqlite
DBGSV_ERROR_OUT=shell STAR_RESOURCEPATH=$O/bin/
$O/bin/cppunit/cppunittester
$W/LinkTarget/CppunitTest/libtest_lotuswordpro_test_lotuswordpro.so
--headless --protector unoexceptionprotector.so unoexceptionprotector
-env:CONFIGURATION_LAYERS=xcsxcu:file://$O/xml/registry
-env:UNO_TYPES= file://$O/bin/udkapi.rdb  file://$O/bin/types.rdb
-env:UNO_SERVICES=file://$O/xml/ure/services.rdb
file://$O/xml/component/lotuswordpro/util/lwpfilter.component
file://$O/xml/configmgr.component  file://$O/xml/ucb1.component
file://$O/xml/ucpfile1.component
-env:URE_INTERNAL_LIB_DIR=file://$O/lib  -env:LO_LIB_DIR=file://$O/lib

$W/CppunitTest/lotuswordpro_test_lotuswordpro.test.log 21 ||

(cat $W/CppunitTest/lotuswordpro_test_lotuswordpro.test.log  echo;
echo Error: a unit test failed, please do one of:; echo; echo export
DEBUGCPPUNIT=TRUE# for exception catching; echo export
GDBCPPUNITTRACE=\gdb --args\ # for interactive debugging; echo
export VALGRIND=memcheck# for memory checking ; echo and
retry.  false))

Abort trap (core dumped) File tested,Test
Result,Execution Time (ms)
file:///usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/lotuswordpro/qa/cppunit/data/pass/A14.lwp,Signal
11 during cups initialization called, ignoring cups

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.
gmake: ***
[/usr/ports/editors/libreoffice/work/libreoffice-core-3.5.2.2/workdir/unxfbsd.pro/CppunitTest/lotuswordpro_test_lotuswordpro.test]
Error 1
---snip---

The mysterious thing is that I have a nearly identical box at the office
running 9-STABLE and there libreoffice compiles fine.
It only differs in two hardware components:
CPU is core2 at home and core5i at the office.
RAM is 4gb at home and 8gb at the office.

System on both is clean installed and updated 9-STABLE.

So maybe this is a memory/cpu issue?

Regards,

Jens




I have the same problem on a 8.2-RELEASE system.

I posted it on the ports list. I got an answer and a patch that can be used.

Take a look at the archives for the ports list.

/Leslie


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org