Bug 49556

Summary:	Latest git fails to build on ubuntu 10.04
Product:	LibreOffice	Reporter:	Sergey <fuxx>
Component:	Libreoffice	Assignee:	Not Assigned <libreoffice-bugs>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	medium	CC:	jmadero.dev
Version:	unspecified
Hardware:	Other
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:
Attachments:	build_error.log

Description Sergey 2012-05-06 09:14:45 UTC

Created attachment 61106 [details]
build_error.log

I followed steps from here: http://wiki.documentfoundation.org/Development/Native_Build
1) git clone git://anongit.freedesktop.org/libreoffice/core libo
2) cd libo
3) /autogen.sh --with-num-cpus=6 --with-max-jobs=6 --without-junit
4) make

then i get the following:

postgresql deliver
Module 'postgresql' delivered successfully. 4 files copied, 0 files unchanged

-----------------------------------------------------------------------
        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 /media/Data/libreoffice/libo/udkapi/prj

 it seems that the error is inside 'udkapi', 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)

Comment 1 Sergey 2012-05-07 10:21:10 UTC

Seems this is a bug in build system - parallel build does not honor dependencies.
E.g the problem is in --with-num-cpus=6 --with-max-jobs=6.

Comment 2 Joel Madero 2012-10-30 18:40:58 UTC

FDO is more for bugs with the product, not bugs with building. For these kinds of things it's best to get on the mailing list to ask questions. Marking as INVALID because of this. 

If you need instructions on how to send mail to mailing list let me know and I'll get those for you.

Regards

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.