Hi Luiz,
I appreciate your persistence, but pay attention in what i'll say: You need
to fix the error before run `make`. Then you can try to build again:
$ cd libo
$ make
If you want to help LibreOffice, there are many possibilities, other than
coding. I don't know your C++ experience, but if you're not confortable with
the code or with Git (i give you all the reason, Git is a penitence!), you
can contribute with documentation (Wiki), reporting bugs (bugzilla), etc.
These are noble activities too.
Resuming, you have to direct your energy for what you do best and you'll
help LibreOffice so much.
Regards,
Júlio.
2011/4/13 Luiz Henrique Natalino <luizhenriquenatalino@gmail.com>
Hi Júlio,
I have to run make again in the base folder?
2011/4/13 Júlio Hoffimann <julio.hoffimann@gmail.com>
Hi Luiz,
Running the commands you'll get the C++ errors, so fix it and run `make`
again.
Júlio.
2011/4/13 Luiz Henrique Natalino <luizhenriquenatalino@gmail.com>
Hello Júlio,
procedure and unfortunately did not work, what can I do for work?
thanks
------------------------------------------------------------------
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/luiz/libreoffice/bootstrap/sal/qa/osl/security
it seems that the error is inside 'sal', please re-run build
inside this module to isolate the error and/or test your fix:
-----------------------------------------------------------------------
rm -Rf /home/luiz/libreoffice/bootstrap/sal/unxlngx6.pro # optional
module 'clean'
/bin/bash
cd /home/luiz/libreoffice/bootstrap
source ./LinuxX86-64Env.Set.sh
cd sal
build
when the problem is isolated and fixed exit and re-run 'make' from the
top-level
make: ** [all] Erro 1
2011/4/13 Júlio Hoffimann <julio.hoffimann@gmail.com>
Hi Luiz,
Just execute the commands in the error message and you'll get the C++
errors. ;-)
rm -Rf /home/luiz/libreoffice/bootstrap/sal/unxlngx6.pro # optional
module 'clean'
/bin/bash
cd /home/luiz/libreoffice/bootstrap
source ./LinuxX86-64Env.Set.sh <http://linuxx86-64env.set.sh/>
cd sal
build
Regards,
Júlio.
2011/4/13 Luiz Henrique Natalino <luizhenriquenatalino@gmail.com>
hello people,
I'm having the following problem in the compilation, anyone know what
might be?
Module 'libxmlsec' delivered successfully. 49 files copied, 0 files
unchanged
-----------------------------------------------------------------------
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/luiz/libreoffice/bootstrap/sal/qa/osl/security
it seems that the error is inside 'sal', please re-run build
inside this module to isolate the error and/or test your fix:
-----------------------------------------------------------------------
rm -Rf /home/luiz/libreoffice/bootstrap/sal/unxlngx6.pro # optional
module 'clean'
/bin/bash
cd /home/luiz/libreoffice/bootstrap
source ./LinuxX86-64Env.Set.sh
cd sal
build
when the problem is isolated and fixed exit and re-run 'make' from the
top-level
make: ** [all] Erro 1
--
Att. Luiz Henrique Natalino
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
--
Att. Luiz Henrique Natalino
--
Att. Luiz Henrique Natalino
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.