It's an issue related with LibreOfficePython.framework and
install_name_tool:
1 - create the folder where LibreOfficePython.framework was installed in
the tinderbox:
$: sudo mkdir -p
/Volumes/Master/lo/core/workdir/UnpackedTarball/python3/python-inst/@__________________________________________________OOO
2 - create a symbolic link to LibreOfficePython.framework:
$: sudo ln -s
/Applications/LibreOfficeDev.app/Contents/Frameworks/LibreOfficePython.framework
/Volumes/Master/lo/core/workdir/UnpackedTarball/python3/python-inst/@__________________________________________________OOO/LibreOfficePython.framework
3 - Launch LibreOffice:
$: /Applications/LibreOfficeDev.app/Contents/MacOS/soffice
Regards,
Robert
On Sat, Nov 1, 2014 at 10:40 AM, Robert Antoni Buj i Gelonch wrote:
Doing a clean build seems that doesn't solve the issue, so I'm going to
install the development environment from scratch.
On Fri, Oct 31, 2014 at 11:16 AM, Christian Lohmaier wrote:
Hi Robert,
there have been reports on IRC that the daily builds of your tinderbox
(@64) crashes when opening any file.
Those crashes don't occur with the daily builds from my bot (@49),
that also compiles on Mac OSX 10.10 (although with the default
min-version.
As your bot does incremental builds: could you try a make clean to see
whether the problem is caused by some incompatible changes that
weren't picked up properly by the incremental build?
The user who reported it often hangs out in the #libreoffice-qa
channel (nich steve-_-2)
Thanks a lot,
ciao
Christian
--
http://about.me/rbuj
--
http://about.me/rbuj
Context
- Re: 10.10 tinderbox builds crashes on opening any file · Robert Antoni Buj i Gelonch
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.