On Wed, Sep 29, 2010 at 8:54 PM, Luis E Vásquez r <starsuitesun@gmail.com>wrote:
Medellin, sep 29/2010
Hi, people
All day was testing LOo in different environments and multiple files and I'm
really happy with the result, among other relevant langpack install OOo,
both French and Spanish work fine.
Great news Luis, keep up the good work. We will probably need to setup a TCM
similar to the one in OOo or request it to the community.
The previous TCM is located here, it looks somehow basic, maybe building a
new TCM with better look and feel.
http://www.sunvirtuallab.com:8001/tcm2/opensource/tcm_login.cgi?tcm_config=newooo
Best Regards,
Luis E. Vásquez R.
OpenOffice.org Volunteer & Support
Este mensaje se ha enviado desde Medellín, Colombia
*10 Años usando exitosamente OpenOffice.org libre, seguro y abierto*
2010/9/29 George Galt <george.galt@gmail.com>
On Tue, Sep 28, 2010 at 4:52 PM, Volker Merschmann <merschmann@gmail.com>
wrote:
Hi,
2010/9/28 George Galt <george.galt@gmail.com>:
Is this the correct forum for posting questions on building
LibreOffice from source?
Thanks,
George
This is the only mailinglist at this moment, please ask.
Volker
--
++ Volker Merschmann - Content Developer OpenOffice.org
++ Office-Suite für Linux, Mac, Windows -- http://de.openoffice.org/
--
To unsubscribe, send an empty e-mail to
discuss+unsubscribe@documentfoundation.org<discuss%2Bunsubscribe@documentfoundation.org>
All messages you send to this list will be publicly archived and cannot
be deleted.
List archives are available at
http://www.documentfoundation.org/lists/discuss/
I'm on Fedora 13 x86_64. I followed the instructions here:
http://www.documentfoundation.org/develop/
FYI, for me, I needed to also install libXaw-devel even after
yum-depbuild for openoffice, I also needed to alter the auto-gen
command to: ./autogen.sh --with-distro=LibreOfficeLinux --with-git
--with-num-cpus=2 --without-junit because I was getting complaints
that make couldn't find "Junit 4".
Now, however, I'm stuck. Running make ends with the following:
8 module(s):
tomcat
beanshell
hsqldb
rhino
saxon
lucene
qadevOOo
xmerge
need(s) to be rebuilt
Reason(s):
ERROR: error 65280 occurred while making
/home/ggalt/workspace/build/build/libreoffice-3.2.99.1/rhino
ERROR: error 65280 occurred while making
/home/ggalt/workspace/build/build/libreoffice-3.2.99.1/xmerge/source/xmerge
ERROR: error 65280 occurred while making
/home/ggalt/workspace/build/build/libreoffice-3.2.99.1/lucene
ERROR: error 65280 occurred while making
/home/ggalt/workspace/build/build/libreoffice-3.2.99.1/tomcat
ERROR: error 65280 occurred while making
/home/ggalt/workspace/build/build/libreoffice-3.2.99.1/saxon
ERROR: error 65280 occurred while making
/home/ggalt/workspace/build/build/libreoffice-3.2.99.1/beanshell
ERROR: error 65280 occurred while making
/home/ggalt/workspace/build/build/libreoffice-3.2.99.1/hsqldb
ERROR: error 65280 occurred while making
/home/ggalt/workspace/build/build/libreoffice-3.2.99.1/qadevOOo
Attention: if you fix the errors in above module(s) you may prolongue
your the build issuing command:
build --from tomcat beanshell hsqldb rhino saxon lucene qadevOOo
xmerge
make: *** [stamp/build] Error 1
Any thoughts on where to go?
George
--
To unsubscribe, send an empty e-mail to
discuss+unsubscribe@documentfoundation.org<discuss%2Bunsubscribe@documentfoundation.org>
All messages you send to this list will be publicly archived and cannot be
deleted.
List archives are available at
http://www.documentfoundation.org/lists/discuss/
--
*Alexandro Colorado*
*OpenOffice.org* Español
http://es.openoffice.org
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.