Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


Update on how this worked.

On 2011-05-04, at 6:58 PM, Peter Teeson wrote:

Hi Michael et al:
Tried everything suggested so far. Same build failure.
Peter

P.S. Right now going to watch the evening news whilst doing:

Gandalf:git pteeson$ rm -dfR libo
Gandalf:git pteeson$ git clone git://anongit.freedesktop.org/libreoffice/bootstrap libo
Cloning into libo...
remote: Counting objects: 97475, done.
.......


-----------------------------------------------------------------------
        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 /Users/pteeson/git/libo/vcl/aqua/source/window
ERROR: error 65280 occurred while making /Users/pteeson/git/libo/vcl/aqua/source/a11y
ERROR: error 65280 occurred while making /Users/pteeson/git/libo/vcl/source/app
ERROR: error 65280 occurred while making /Users/pteeson/git/libo/shell/source/backends/macbe
ERROR: error 65280 occurred while making 
/Users/pteeson/git/libo/lingucomponent/source/spellcheck/macosxspell

 it seems you are using a threaded build, which means that the
 actual compile error is probably hidden far above, and could be
 inside any of these other modules:
     vcl lingucomponent
 please re-run build inside each one to isolate the problem.
-----------------------------------------------------------------------

rm -Rf /Users/pteeson/git/libo/shell/unxmacxi.pro # optional module 'clean'
/bin/sh
cd /Users/pteeson/git/libo
source ./MacOSXX86Env.Set.sh
cd shell
build

when the problem is isolated and fixed exit and re-run 'make' from the top-level
make: *** [check] Error 1
Gandalf:libo pteeson$

============== end of log ==============

----------- my comments & questions -----------------
(0) The symbolic links are correct
(1) ???? What does it mean to " please re-run build inside each one to isolate the problem."

NOTE: I found these in the log:
/Users/pteeson/Desktop/LibreOffice/5May-2nd Build.txt:18882:  dmake:  Error code 1, while making 
'../../../unxmacxi.pro/slo/macbecdef.obj'
/Users/pteeson/Desktop/LibreOffice/5May-2nd Build.txt:18893:  dmake:  Error code 1, while making 
'../../../unxmacxi.pro/slo/macbecdef.obj'
/Users/pteeson/Desktop/LibreOffice/5May-2nd Build.txt:25236:  dmake:  Error code 1, while making 
'../../../unxmacxi.pro/slo/salobj.obj'
/Users/pteeson/Desktop/LibreOffice/5May-2nd Build.txt:25261:  dmake:  Error code 1, while making 
'../../unxmacxi.pro/slo/stdtext.obj'
/Users/pteeson/Desktop/LibreOffice/5May-2nd Build.txt:25304:  i686-apple-darwin10-g++-4.0.1: dmake: 
 Error code 1, while making '../../../unxmacxi.pro/slo/salframe.obj'
/Users/pteeson/Desktop/LibreOffice/5May-2nd Build.txt:25321:  dmake:  Error code 1, while making 
'../../../unxmacxi.pro/slo/aqua11yfactory.obj'
/Users/pteeson/Desktop/LibreOffice/5May-2nd Build.txt:25352:  dmake:  Error code 1, while making 
'../../unxmacxi.pro/slo/help.obj'
/Users/pteeson/Desktop/LibreOffice/5May-2nd Build.txt:25398:  dmake:  Error code 1, while making 
'../../../unxmacxi.pro/slo/aqua11ycomponentwrapper.obj'
/Users/pteeson/Desktop/LibreOffice/5May-2nd Build.txt:26097:  dmake:  Error code 1, while making 
'../../../unxmacxi.pro/slo/macspellimp.obj'
/Users/pteeson/Desktop/LibreOffice/5May-2nd Build.txt:26106:  dmake:  Error code 1, while making 
'../../../unxmacxi.pro/slo/macspellimp.obj'


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.