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


Hello,

During "make dev-install" after built libreoffice, I got the following
error. Any suggestions? Is this an error with libreoffice that needs to be
fix or a problem with java? I know it's showing it as a java bug, but I'm
curious if it was caused by a bug in libreoffice.

*Error:*

[ build LNK ] Library/libfileacc.so
/bin/bash: line 1: 19322 Segmentation fault      make -s -r -j4
dmake:  Error code 139, while making 'all'

-----------------------------------------------------------------------
        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/mouche/LOdev/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:
-----------------------------------------------------------------------

rm -Rf /home/mouche/LOdev/tail_build/unxlngx6.pro # optional module 'clean'
/bin/bash
cd /home/mouche/LOdev
source ./LinuxX86-64Env.Set.sh
cd tail_build
make -r


*And here's the error log that it references:*

http://pastebin.com/QGYBHKmJ

I'm just getting started, and I don't know how to troubleshoot this. I'd
appreciate any help you can provide.

Thanks,
Glen

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.