On Sat, 2010-10-02 at 08:41 +1300, sidney wrote:
Michael Meeks wrote, On 2/10/10 3:46 AM:
Hi Krishnan,
On Thu, 2010-09-30 at 19:27 +0530, krishnan parthasarathi wrote:
I followed the above test and found that open() calls on pythonloader
module were failing with ENOENT. For eg,
..
Ok - this is a broken pythonpath issue.
From the log file I found that ooinstall is looking for python module
in the system directories and not in the python that was built in LO.
Right - so - we added a fix to ooinstall in git master that should make
this work for you - just update: $ git pull -r # in your top-level
source directory, and this should be fixed.
Thanks for the report, hope it works for you now,
I don't know whether I built before or after this patch, but someone on IRC
suggested adding the --with-system-python option in the configuration step
which worked for me. Is that a result of this patch or is that option no
longer necessary?
Well, *if* your build works with --with-system-python, I personally
recommend you keep using it, as it reduces build time by skipping the
internal python module.
But as I hear, this problem is fixed now, so that you should be able to
build without --with-system-python.
Best,
Kohei
--
Kohei Yoshida, LibreOffice hacker, Calc
<kyoshida@novell.com>
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.