(2011/07/16 7:46), Norbert Thiebaud wrote:
2011/7/15 Nguyen Vu Hung (KiEi)<vuhung@ki-ei.com>:
Hello all,
I had followed the build instruction[1] and setup my environment for a few
weeks ago.
As I thought the code was a little out of date, so I have tried to pull the
latest code
and make, but it seems that wget could not wget a dependency.
I am not sure what it is.
Any help is appreciated
BR,
Nguyen Vu Hung
cd bootstrap
git pull
You probably need make clean + autogen before continuing here
especially if you have not pulled for few weeks (actually, I'm
guessing, probably at least a couple of month based on the error
below)
(l10n is now translations... that is the git repos that contain localisation)
Norbert
I've tried
[vuhung@libo bootstrap]$ git pull
→ 3 new files
[vuhung@libo bootstrap]$ ./autogen.sh
'--with-junit=/home/vuhung/opt/junit.jar'
→ Done, autogen tells me to make.
[vuhung@libo bootstrap]$ make
********************************************************************
*
* Running the post download checks.
*
********************************************************************
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
/home/vuhung/work/001.GNOME/000.git/bootstrap/instsetoo_native
Fetching dependencies for module l10n from solver... failed
ERROR: incomplete dependencies!
make: *** [all] Error 1
--
Nguyen Vu Hung (Nguyyễn Vũ Hưng)
LibreOffice, Vietnamese Translation Team.
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.