Still can't build libreoffice

[Doug Barton]

On 10/03/2011 07:32, Oliver Heesakkers wrote:

> I have the same problem (9.0 BETA3 amd64)
> 
> When I set libreoffice's DEBUG option, the build (`make`) does complete.

Thanks, that gave me some new places to look. I had the following in
make.conf:

CFLAGS+=       -g
DEBUG_FLAGS+=  -g

Commenting those out avoids the cppunittest error, but now it fails in
various random locations depending on the options I choose. I still have
the following in make.conf in case that's relevant:

WRKDIRPREFIX=	/home/tmp
WITH_OPTIONS=	true
WITH_QT_PHONON=	true
WITH_X11=	true
WITHOUT_HAL=	true
WITHOUT_NLS=	true

For libreoffice the only option I have enabled is GTK. With that
configuration it fails like this:

----------------------------------------------------------
- start unit test #1 on library ../../unxfbsd.pro/lib/libcppu_ifcontainer.so
----------------------------------------------------------
: &&
LD_LIBRARY_PATH=/home/tmp/home/ports/editors/libreoffice/work/libreoffice-bootstrap-3.4.3.2/clone/ure/cppuhelper/unxfbsd.pro/lib:/home/tmp/home/ports/editors/libreoffice/work/libreoffice-bootstrap-3.4.3.2/solver/340/unxfbsd.pro/lib${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}

/home/tmp/home/ports/editors/libreoffice/work/libreoffice-bootstrap-3.4.3.2/solver/340/unxfbsd.pro/bin/cppunit/cppunittester
../../unxfbsd.pro/lib/libcppu_ifcontainer.so
OK (5)

-----------------------------------------------------------------------
        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 65280 occurred while making
/home/tmp/home/ports/editors/libreoffice/work/libreoffice-bootstrap-3.4.3.2/cppuhelper/qa/unourl

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

I tried enabling the DEBUG option and that just caused it to fail
somewhere else.


Doug

-- 

	Nothin' ever doesn't change, but nothin' changes much.
			-- OK Go

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/