Hello,
I monitor LibreOffice usage with Wine on Illumos-based distros so I can help in
that regard.
Minor crash issues seem to affect the builds on oi_151a7. This is not much
different as seen on various Linux builds, so
just isolate the ones specific to Illumos-based distros.
The Adfinis SyGroup in Sweden has been provided build of OpenOffcie and there
was some talks to see if they would do the same for LibreOffice (this was about
a year ago...).
Important references here as well:
https://blogs.apache.org/OOo/entry/porting_apache_openoffice_to_solaris
http://ask.libreoffice.org/en/question/1386/are-there-plans-for-a-solaris-version-of/
http://nabble.documentfoundation.org/LibreOffice-openIndiana-td3688764.html
https://www.illumos.org/issues/684
http://ewaldertl.blogspot.com/2012/01/wine-on-openindiana-liberoffice-ok.html
Many of us have built build environments or builds of LibreOffice for testing
so just ask if you have the time to do some debugging or work on specific
packages/packaging.
~ Ken Mays
________________________________
From: Peter Tribble <peter.trib...@gmail.com>
To: OpenIndiana Developer mailing list <oi-dev@openindiana.org>
Sent: Sunday, January 6, 2013 4:49 PM
Subject: Re: [oi-dev] Libreoffice status
On Fri, Jan 4, 2013 at 10:11 PM, Paolo Marcheschi
<paolo.marches...@ftgm.it> wrote:
> Hi
> Thank you, very much, for sharing your notes.
> I will try as soon as possible into a clean developer zone.
Some links I've found useful (one is a link to Jonathan's work)
http://permalink.gmane.org/gmane.comp.documentfoundation.libreoffice.devel/31802
http://www.linuxfromscratch.org/blfs/view/svn/xsoft/libreoffice.html
http://lists.freedesktop.org/archives/libreoffice/2012-July/034802.html
My attempts to build on Tribblix got sidetracked both by the holidays and
by the release of Enlightenment E17 (finally!). Some comments:
I'm using gcc 4.7.2; I've installed
Java
perl Archive::Zip
ant
autoconf
automake
zip (updated)
unzip (updated)
bison
curl
clucene
hunspell
I've found the build to be pretty broken, so if you can build something
outside of the Libreoffice build and tell it to use that copy then the build
goes much more smoothly. Both clucene and hunspell were built from
the tarballs that Libreoffice uses. So disable everything possible and
use --with-system if you can. I have the following configure flags
--disable-cups
--disable-gconf
--disable-gtk
--without-junit
--without-doxygen
--disable-mozilla
--disable-odk
--with-system-openssl
--with-system-jpeg
--with-system-zlib
--with-system-libxml
--without-stlport
--disable-neon
--disable-python
--with-system-cairo
--with-system-clucene
--with-system-hunspell
--disable-xmlsec
--disable-postgresql-sdbc
I've found both the Illumos ld and the gnu ld that come with OI to fail,
so I upgraded to GNU coreutils 2.23.1 and set LD_ALTEXEC=/usr/gnu/bin/ld
to use that. (This gets even worse with LO 4.0.0 - various pieces call ld
with arguments that aren't compatible with any ld I can use.)
I find that a regular make fails due to dependency errors. Running a
make tail_build explicitly seems to get past that.
--
-Peter Tribble
http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/
_______________________________________________
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev
_______________________________________________
oi-dev mailing list
oi-dev@openindiana.org
http://openindiana.org/mailman/listinfo/oi-dev
