This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Compile Krita/trunk (Ubuntu / Debian /OpenSuse / ArchLinux)

Tags: None
(comma "," separated)
User avatar
Kubuntiac
Registered Member
Posts
786
Karma
2
Kbuildsycoca usually spits out a couple of errors. As far as I can see yours don't have anything to do with Koffice though. Can you run Krita/Karbon/Whatever afterwards? (Sometimes I find you can't by clicking the binary in dolphin, but you can from the command line)
User avatar
robyshot
Registered Member
Posts
6
Karma
0
OS
Kubuntiac wrote:Kbuildsycoca usually spits out a couple of errors. As far as I can see yours don't have anything to do with Koffice though. Can you run Krita/Karbon/Whatever afterwards? (Sometimes I find you can't by clicking the binary in dolphin, but you can from the command line)

sorry for noit being complete,that's the problem i can't run krita (konsole propose me to install it) if i run the "icon" from /home/roby/koffice/koffice-inst/bin/krita
Code: Select all
krita(2709)/koffice (lib komain): "krita" part.desktop not found.

krita(2709)/koffice (lib komain): Run 'kde4-config --path services' to see which directories were searched, assuming kde startup had the same environment as your current shell.

krita(2709)/koffice (lib komain): Check your installation (did you install KOffice in a different prefix than KDE, without adding the prefix to /etc/kderc ?)
User avatar
Kubuntiac
Registered Member
Posts
786
Karma
2
That usually means that the paths were changed or aren't set yet. This can happen if you created the koffice folder anywhere but in the top of your home folder (ie ~/koffice) or if you haven't restarted/logged out and in again.

You can have koffice compile in folders other than ~/koffice, but if you do you just need to edit the paths you pasted in ~/ .bashrc to match. After that just logout and log in again.

You're close!
User avatar
robyshot
Registered Member
Posts
6
Karma
0
OS
i'm so stupid :z

i skipped a passage (to edit bashrc)

really thank for the patience :)
User avatar
Kubuntiac
Registered Member
Posts
786
Karma
2
Glad you got it working! Enjoy, and remember to post your masterpieces on the Gallery :)
User avatar
chicao
Registered Member
Posts
12
Karma
0
OS
Hello everyone!

I'm trying to build Krita for the first time using the steps in Build Koffice. (http://wiki.koffice.org/index.php?title ... ng_KOffice)

Everything goes fine, but when trying to generate index.cache.bz2 the error bellow appears.

Can someone point me what i'm doing wrong?

Code: Select all
...
[ 65%] Built target krita_colorspaces_extensions                                                                                                                                   
[ 65%] Generating index.cache.bz2
file:///usr/share/apps/ksgmltools2/customization/dtd/kdex.dtd:101: warning: failed to load external entity "file:///usr/share/xml/docbook/xml-dtd-4.2/docbookx.dtd"                 
%DocBookDTD;
            ^
Entity: line 1:
 %DocBookDTD;
             ^
file:///usr/share/apps/ksgmltools2/customization/dtd/modifications.elements:42: validity error : PEReference: %div.title.content; not found
<!ELEMENT book %ho; ((%div.title.content;)?, bookinfo,
                                         ^
file:///usr/share/apps/ksgmltools2/customization/dtd/modifications.elements:42: parser error : ContentDecl : Name or '(' expected
<!ELEMENT book %ho; ((%div.title.content;)?, bookinfo,
                                         ^
file:///usr/share/apps/ksgmltools2/customization/dtd/modifications.elements:42: parser error : expected '>'
<!ELEMENT book %ho; ((%div.title.content;)?, bookinfo,
                                           ^
file:///usr/share/apps/ksgmltools2/customization/dtd/modifications.elements:42: parser error : Content error in the external subset
<!ELEMENT book %ho; ((%div.title.content;)?, bookinfo,
                                           ^
index.docbook:11: parser error : Entity 'language' not defined
<book lang="&language;">
                      ^
index.docbook:13: parser error : Entity 'koffice' not defined
<title>&koffice;</title>
                ^
index.docbook:17: parser error : Entity 'Raphael.Langerhorst' not defined
&Raphael.Langerhorst; &Raphael.Langerhorst.mail;
                     ^
index.docbook:17: parser error : Entity 'Raphael.Langerhorst.mail' not defined
&Raphael.Langerhorst; &Raphael.Langerhorst.mail;
                                                ^
index.docbook:20: parser error : Entity 'Jost.Schenck' not defined
&Jost.Schenck; &Jost.Schenck.mail;
              ^
index.docbook:20: parser error : Entity 'Jost.Schenck.mail' not defined
&Jost.Schenck; &Jost.Schenck.mail;
                                  ^
index.docbook:30: parser error : Entity 'koffice' not defined
&koffice; is an integrated office suite for the K Desktop Environment
         ^
index.docbook:31: parser error : Entity 'kde' not defined
(&kde;).
      ^
index.docbook:46: parser error : Entity 'koffice' not defined
<title>&koffice; components</title>
                ^
index.docbook:49: parser error : Entity 'koffice' not defined
&koffice; is an integrated office suite for the K Desktop Environment
         ^
index.docbook:50: parser error : Entity 'kde' not defined
(&kde;). &koffice; currently consists of the following components:
      ^
index.docbook:50: parser error : Entity 'koffice' not defined
(&kde;). &koffice; currently consists of the following components:
                  ^
index.docbook:54: parser error : Entity 'kword' not defined
<listitem><para>&kword; (a frames-based wordprocessor)</para></listitem>
                       ^
index.docbook:55: parser error : Entity 'kspread' not defined
<listitem><para>&kspread; (a spreadsheet application)</para></listitem>
                         ^
index.docbook:56: parser error : Entity 'kpresenter' not defined
<listitem><para>&kpresenter; (screen and slide presentations)</para></listitem>
                            ^
index.docbook:57: parser error : Entity 'kivio' not defined
<listitem><para>&kivio; (a flowchart application)</para></listitem>
                       ^
index.docbook:58: parser error : Entity 'karbon14' not defined
<listitem><para>&karbon14; (a vector drawing application)</para></listitem>
                          ^
index.docbook:59: parser error : Entity 'krita' not defined
<listitem><para>&krita; (a pixel based drawing application)</para></listitem>
                       ^
index.docbook:60: parser error : Entity 'kexi' not defined
<listitem><para>&kexi; (an integrated environment for managing data)</para></lis
                      ^
index.docbook:61: parser error : Entity 'kchart' not defined
<listitem><para>&kchart; (a charts/graphs generation application)</para></listit
                        ^
index.docbook:62: parser error : Entity 'kformula' not defined
<listitem><para>&kformula; (an editor for mathematical formulae)</para></listite
                          ^
index.docbook:66: parser error : Entity 'koffice' not defined
Because these components are based on the KParts component model, &koffice;
                                                                           ^
index.docbook:67: parser error : Entity 'koffice' not defined
components are designed to work very well with each other. Any &koffice;
                                                                        ^
index.docbook:68: parser error : Entity 'koffice' not defined
component can be embedded in another &koffice; document. For instance, you
                                              ^
index.docbook:69: parser error : Entity 'kspread' not defined
can insert a spreadsheet which you created in &kspread; directly into a &kword;
                                                       ^
index.docbook:69: parser error : Entity 'kword' not defined
can insert a spreadsheet which you created in &kspread; directly into a &kword;
                                                                               ^
index.docbook:71: parser error : Entity 'koffice' not defined
&koffice;.
         ^
index.docbook:76: parser error : Entity 'koffice' not defined
&koffice;. You will find many plugins in some of the components
         ^
index.docbook:83: parser error : Entity 'koffice' not defined
This manual only covers the general features of &koffice;, those that
                                                         ^
index.docbook:91: parser error : Entity 'koffice' not defined
<title>Overview of &koffice; features</title>
                            ^
index.docbook:95: parser error : Entity 'koffice' not defined
&koffice; provides a framework that all components build on. Through
         ^
index.docbook:105: parser error : Entity 'koffice' not defined
Despite offering so many components, &koffice; is very lightweight, fast and
                                              ^
index.docbook:106: parser error : Entity 'koffice' not defined
has a rather low memory footprint. This is also achieved because &koffice; build
                                                                          ^
index.docbook:107: parser error : Entity 'kde' not defined
on &kde;, which is already a very powerful application development framework.
        ^
index.docbook:110: parser error : Entity 'koffice' not defined
A goal of &koffice; is also to not overload the user interface with features
                   ^
index.docbook:117: parser error : Entity 'koffice' not defined
functionality yourself by extending &koffice;. &koffice; really doesn't
                                             ^
index.docbook:117: parser error : Entity 'koffice' not defined
functionality yourself by extending &koffice;. &koffice; really doesn't
                                                        ^
index.docbook:120: parser error : Entity 'koffice' not defined
additional plugins or scripts, thus keeping &koffice; itself lightweight.
                                                     ^
index.docbook:126: parser error : Entity 'koffice' not defined
&koffice; offers a wide range of components, covering most of the home
         ^
index.docbook:128: parser error : Entity 'koffice' not defined
through scripts, plugins or even whole components based on the &koffice;
                                                                        ^
index.docbook:141: parser error : Entity 'koffice' not defined
For this reason &koffice; has adapted the OASIS OpenDocument format
                         ^
index.docbook:146: parser error : Entity 'kde' not defined
<title>&kde; Features</title>
            ^
index.docbook:148: parser error : Entity 'koffice' not defined
Since &koffice; builds on &kde; all the features you would expect from a
               ^
index.docbook:148: parser error : Entity 'kde' not defined
Since &koffice; builds on &kde; all the features you would expect from a
                               ^
index.docbook:149: parser error : Entity 'kde' not defined
&kde; application are also available in &koffice;. This includes &DCOP;, KParts,
     ^
index.docbook:149: parser error : Entity 'koffice' not defined
&kde; application are also available in &koffice;. This includes &DCOP;, KParts,
                                                 ^
index.docbook:149: parser error : Entity 'DCOP' not defined
&kde; application are also available in &koffice;. This includes &DCOP;, KParts,
                                                                       ^
index.docbook:151: parser error : Entity 'koffice' not defined
feel of &koffice; very familiar and really integrates &koffice; into the
                 ^
index.docbook:151: parser error : Entity 'koffice' not defined
feel of &koffice; very familiar and really integrates &koffice; into the
                                                               ^
index.docbook:160: parser error : Entity 'koffice' not defined
<title>&koffice; Technology</title>
                ^
index.docbook:163: parser error : Entity 'koffice' not defined
<title>KParts - the building blocks of &koffice;</title>
                                                ^
index.docbook:169: parser error : Entity 'koffice' not defined
Each &koffice; application is designed to fulfill very specific needs.
              ^
index.docbook:170: parser error : Entity 'kspread' not defined
For example, &kspread; is a program for manipulating spreadsheets, while
                      ^
index.docbook:171: parser error : Entity 'kword' not defined
&kword; is a program for word processing. By focusing on a specific
       ^
index.docbook:173: parser error : Entity 'koffice' not defined
depending on what you do with &koffice;, you'll often want to take
                                       ^
index.docbook:179: parser error : Entity 'kword' not defined
Suppose that you are preparing a document in &kword; and want to
                                                    ^
index.docbook:180: parser error : Entity 'kword' not defined
illustrate some point using a table. While &kword; provides its own
                                                  ^
index.docbook:184: parser error : Entity 'kword' not defined
&kword; programmer certainly <emphasis>could</emphasis> try to implement
       ^
index.docbook:185: parser error : Entity 'kword' not defined
this functionality. However, &kword; would never be as good as &kspread;
                                    ^
index.docbook:185: parser error : Entity 'kspread' not defined
this functionality. However, &kword; would never be as good as &kspread;
                                                                        ^
index.docbook:203: parser error : Entity 'koffice' not defined
functionality offered by <emphasis>all</emphasis> &koffice;
                                                           ^
index.docbook:211: parser error : Entity 'kspread' not defined
In the example mentioned above, you would simply insert a &kspread; part
                                                                   ^
index.docbook:212: parser error : Entity 'kword' not defined
into your &kword; document. Then, whenever you edit your table,
                 ^
index.docbook:213: parser error : Entity 'kspread' not defined
&kspread; would take control in the background. Control would return to
         ^
index.docbook:214: parser error : Entity 'kword' not defined
&kword; when you stop working on the table and start working on text
       ^
index.docbook:216: parser error : Entity 'kspread' not defined
while editing the table, reflect the functionality of &kspread; instead
                                                               ^
index.docbook:217: parser error : Entity 'kword' not defined
of that of &kword;. This ability to include the functionality of one
                  ^
index.docbook:234: parser error : Entity 'kspread' not defined
<title>Inserting a &kspread; part into a &kword; application</title>
                            ^
index.docbook:234: parser error : Entity 'kword' not defined
<title>Inserting a &kspread; part into a &kword; application</title>
                                                ^
index.docbook:236: parser error : Entity 'kword' not defined
<para>Start &kword;. You can do that either from the panel or by typing
                   ^
index.docbook:255: parser error : Entity 'LMB' not defined
Press the &LMB; mouse button where you want the upper left corner of
               ^
index.docbook:265: parser error : Entity 'kword' not defined
Easy, isn't it? You should now see a table frame in your &kword;
                                                                ^
index.docbook:274: parser error : Entity 'kspread' not defined
&kspread;.
         ^
index.docbook:279: parser error : Entity 'kspread' not defined
Your table frame now contains the elements of a &kspread; view, with
                                                         ^
index.docbook:280: parser error : Entity 'etc' not defined
scrollbars, a tab bar for the selection of tables, &etc;
                                                        ^
index.docbook:287: parser error : Entity 'kspread' not defined
&kspread;. In fact you <emphasis>are</emphasis> using &kspread;.
         ^
index.docbook:287: parser error : Entity 'kspread' not defined
&kspread;. In fact you <emphasis>are</emphasis> using &kspread;.
                                                               ^
index.docbook:291: parser error : Entity 'kword' not defined
Now click somewhere into your &kword; document, outside of the table
                                     ^
index.docbook:293: parser error : Entity 'kword' not defined
&kword;, the elements of the &kspread; view should disappear. Your table
       ^
index.docbook:293: parser error : Entity 'kspread' not defined
&kword;, the elements of the &kspread; view should disappear. Your table
                                      ^
index.docbook:309: parser error : Entity 'koffice' not defined
<title>Configuring &koffice; and Your System</title>
                            ^
index.docbook:312: parser error : Entity 'koffice' not defined
While &koffice; should work quite nice out of the box, there may well be
               ^
index.docbook:313: parser error : Entity 'koffice' not defined
some things to optimize to get the best out of &koffice;. This chapter
                                                        ^
index.docbook:315: parser error : Entity 'koffice' not defined
your new office suite and make it suite your needs. &koffice; is
                                                             ^
index.docbook:322: parser error : Entity 'X-Window' not defined
Fonts are a difficult topic on &X-Window;. In this section we'll cover
                                         ^
index.docbook:324: parser error : Entity 'koffice' not defined
&koffice;. Some problems are not just &koffice;s fault, but depend on
         ^
index.docbook:324: parser error : Entity 'koffice' not defined
&koffice;. Some problems are not just &koffice;s fault, but depend on
                                               ^
index.docbook:346: parser error : Entity 'koffice' not defined
<para> While &koffice; automatically can handle all X11 fonts
                      ^
index.docbook:349: parser error : Entity 'koffice' not defined
<application>ghostscript</application>. Now, while &koffice; knows the
                                                            ^
index.docbook:350: parser error : Entity 'X-Window' not defined
font names used by &X-Window;, it does normally
                             ^
index.docbook:352: parser error : Entity 'koffice' not defined
<application>ghostscript</application>. &koffice; tries to guess these
                                                 ^
index.docbook:361: parser error : Entity 'koffice' not defined
font names &koffice; uses to its own font names. This can be done by
                    ^
index.docbook:375: parser error : Entity 'koffice' not defined
Algerian-Roman is the name &koffice; uses for Algerian. You'll have to
                                    ^
index.docbook:376: parser error : Entity 'koffice' not defined
add such lines for the fonts &koffice; doesn't display correctly.  To
                                      ^
index.docbook:394: parser error : Entity 'koffice' not defined
<title>Customizing the &koffice; &GUI;</title>
                                ^
index.docbook:394: parser error : Entity 'GUI' not defined
<title>Customizing the &koffice; &GUI;</title>
                                      ^
index.docbook:397: parser error : Entity 'koffice' not defined
While &koffice; comes out of the box with a &GUI; (graphical user interface)
               ^
index.docbook:397: parser error : Entity 'GUI' not defined
While &koffice; comes out of the box with a &GUI; (graphical user interface)
                                                 ^
index.docbook:404: parser error : Entity 'koffice' not defined
doesn't understand. To tailor &koffice; to her needs, I reduced the
                                       ^
index.docbook:405: parser error : Entity 'GUI' not defined
&GUI; to a bare minimum of functionality. As she only needs to write
     ^
index.docbook:407: parser error : Entity 'etc' not defined
functionality than saving, loading, printing, &etc;
                                                   ^
index.docbook:410: parser error : Entity 'Qt' not defined
<para> Thanks to the <quote>action</quote> concept of &Qt; and &kde;,
                                                          ^
index.docbook:410: parser error : Entity 'kde' not defined
<para> Thanks to the <quote>action</quote> concept of &Qt; and &kde;,
                                                                    ^
index.docbook:411: parser error : Entity 'koffice' not defined
you can freely customize &koffice; menubars and tool
                                  ^
index.docbook:413: parser error : Entity 'koffice' not defined
to do this. &koffice; stores its &GUI; configuration in &XML; files
                     ^
index.docbook:413: parser error : Entity 'GUI' not defined
to do this. &koffice; stores its &GUI; configuration in &XML; files
                                      ^
index.docbook:413: parser error : Entity 'XML' not defined
to do this. &koffice; stores its &GUI; configuration in &XML; files
                                                             ^
index.docbook:416: parser error : Entity 'XML' not defined
&XML; document works (or &HTML;, which is a subset of
     ^
index.docbook:416: parser error : Entity 'HTML' not defined
&XML; document works (or &HTML;, which is a subset of
                               ^
index.docbook:417: parser error : Entity 'XML' not defined
&XML;). [The <quote>action</quote> concept needs to be discussed in
     ^
index.docbook:421: parser error : Entity 'koffice' not defined
Normally, each &koffice; application has at least two of those &XML;
                        ^
index.docbook:421: parser error : Entity 'XML' not defined
Normally, each &koffice; application has at least two of those &XML;
                                                                    ^
index.docbook:422: parser error : Entity 'GUI' not defined
files: one describing the &GUI; of the shell (basically, that's what you
                               ^
index.docbook:423: parser error : Entity 'GUI' not defined
see if there is no document open) and one describing the &GUI; of the
                                                              ^
index.docbook:425: parser error : Entity 'kword' not defined
&kword;, these two &XML; files are named
       ^
index.docbook:425: parser error : Entity 'XML' not defined
&kword;, these two &XML; files are named
                        ^
index.docbook:473: parser error : Entity 'koffice' not defined
<title>Other &koffice; manuals</title>
                      ^
index.docbook:476: parser error : Entity 'koffice' not defined
For detailed information on the different &koffice; applications, please
                                                   ^
index.docbook:490: parser error : Entity 'kde' not defined
about &kde; or &koffice;.
           ^
index.docbook:490: parser error : Entity 'koffice' not defined
about &kde; or &koffice;.
                        ^
index.docbook:495: parser error : Entity 'koffice' not defined
<para><ulink url="http://koffice.org">The &koffice;
                                                   ^
index.docbook:497: parser error : Entity 'koffice' not defined
install &koffice;, news about &koffice; development, screenshots &etc;
                 ^
index.docbook:497: parser error : Entity 'koffice' not defined
install &koffice;, news about &koffice; development, screenshots &etc;
                                       ^
index.docbook:497: parser error : Entity 'etc' not defined
install &koffice;, news about &koffice; development, screenshots &etc;
                                                                      ^
index.docbook:501: parser error : Entity 'kde' not defined
<ulink url="http://www.kde.org">The &kde; Homepage</ulink>. &kde; is the most ad
                                         ^
index.docbook:501: parser error : Entity 'kde' not defined
<ulink url="http://www.kde.org">The &kde; Homepage</ulink>. &kde; is the most ad
                                                                 ^
index.docbook:503: parser error : Entity 'koffice' not defined
&koffice; makes use of the &kde; libraries.
         ^
index.docbook:503: parser error : Entity 'kde' not defined
&koffice; makes use of the &kde; libraries.
                                ^
index.docbook:507: parser error : Entity 'Qt' not defined
of the C++-toolkit &Qt;. &kde; and &koffice; make use of &Qt;.
                       ^
index.docbook:507: parser error : Entity 'kde' not defined
of the C++-toolkit &Qt;. &kde; and &koffice; make use of &Qt;.
                              ^
index.docbook:507: parser error : Entity 'koffice' not defined
of the C++-toolkit &Qt;. &kde; and &koffice; make use of &Qt;.
                                            ^
index.docbook:507: parser error : Entity 'Qt' not defined
of the C++-toolkit &Qt;. &kde; and &koffice; make use of &Qt;.
                                                             ^
index.docbook:516: parser error : Entity 'koffice' not defined
<title>Programming &koffice;</title>
                            ^
index.docbook:521: parser error : Entity 'koffice' not defined
If you want to do &koffice; development, the following resources might
                           ^
index.docbook:528: parser error : Entity 'Qt' not defined
find many documents about programming with &Qt; and &kde;. Here you can find
                                               ^
index.docbook:528: parser error : Entity 'kde' not defined
find many documents about programming with &Qt; and &kde;. Here you can find
                                                         ^
index.docbook:529: parser error : Entity 'kde' not defined
the online version of the complete &kde; library documentation.
                                        ^
index.docbook:532: parser error : Entity 'koffice' not defined
In the &koffice; sources you'll find an example application in the
                ^
index.docbook:585: parser error : Entity 'koffice' not defined
&koffice; is the result of the joint effort of many developers. Each source file
         ^
index.docbook:586: parser error : Entity 'koffice' not defined
of &koffice; is copyrighted by the people who wrote this particular file and
            ^
index.docbook:594: parser error : Entity 'Jost.Schenck' not defined
This manual is copyright by &Jost.Schenck;. It can be distributed
                                          ^
index.docbook:596: parser error : Entity 'kde' not defined
it as long as you send me the changes or commit them to &kde;
                                                             ^
index.docbook:602: parser error : Entity 'koffice' not defined
The other &koffice; manuals are copyrighted by their respective authors.
                   ^
index.docbook:606: parser error : Entity 'underFDL' not defined
&underFDL;
          ^
index.docbook:607: parser error : Entity 'underGPL' not defined
&underGPL;
          ^
index.docbook:618: parser error : Entity 'koffice' not defined
In order to install and use &koffice; you must have:
                                     ^
index.docbook:623: parser error : Entity 'UNIX' not defined
A functioning &UNIX; system (for example, &Linux; or BSD)
                    ^
index.docbook:623: parser error : Entity 'Linux' not defined
A functioning &UNIX; system (for example, &Linux; or BSD)
                                                 ^
index.docbook:624: parser error : Entity 'X-Window' not defined
with a configured &X-Window; (for example, XFree86 or X.Org).
                            ^
index.docbook:627: parser error : Entity 'Qt' not defined
The &Qt; 3.3 libraries from Trolltech. See
        ^
index.docbook:632: parser error : Entity 'kde' not defined
The K Desktop Environment 3.3 (&kde; 3.3) or newer. &koffice; cannot be compiled
                                    ^
index.docbook:632: parser error : Entity 'koffice' not defined
The K Desktop Environment 3.3 (&kde; 3.3) or newer. &koffice; cannot be compiled
                                                             ^
index.docbook:633: parser error : Entity 'kde' not defined
with earlier versions of &kde;. Information on obtaining and installing
                              ^
index.docbook:634: parser error : Entity 'kde' not defined
&kde; can be found at: &kde-http;
     ^
index.docbook:634: parser error : Entity 'kde-http' not defined
&kde; can be found at: &kde-http;
                                 ^
index.docbook:644: parser error : Entity 'kde' not defined
Please note that, while you need the &kde; 3.3 (or newer) libraries
                                          ^
index.docbook:645: parser error : Entity 'koffice' not defined
on your system, you can still use &koffice; in a different desktop
                                           ^
index.docbook:650: parser error : Entity 'koffice' not defined
If you plan on <link linkend="from-source">compiling &koffice; from
                                                              ^
index.docbook:669: parser error : Entity 'Qt' not defined
Troll Tech's &Qt; 3.3 development packages. If these packages are not installed
                 ^
index.docbook:671: parser error : Entity 'Qt' not defined
system, you should probably have to compile &Qt; from source.
                                                ^
index.docbook:685: parser error : Entity 'koffice' not defined
If you want to obtain the most current binary version of &koffice;,
                                                                  ^
index.docbook:699: parser error : Entity 'koffice' not defined
url="http://koffice.org">&koffice; homepage</ulink> for further
                                  ^
index.docbook:728: parser error : Entity 'Linux' not defined
compatible with your system.  If you use the &Linux; operating system
                                                    ^
index.docbook:729: parser error : Entity 'koffice' not defined
and are unable to find a binary package at the &koffice; web site or
                                                        ^
index.docbook:740: parser error : Entity 'koffice' not defined
To install &koffice; from precompiled binaries, you should:
                    ^
index.docbook:746: parser error : Entity 'koffice' not defined
and in working condition (excluding &koffice; of course). You can find
                                             ^
index.docbook:749: parser error : Entity 'koffice' not defined
<step><para>Download the &koffice; binary (or binaries) into a temporary
                                  ^
index.docbook:752: parser error : Entity 'RedHat' not defined
role="extension">.rpm</literal> (&RedHat; Package Management file),
                                         ^
index.docbook:753: parser error : Entity 'koffice' not defined
&koffice; can be installed with the following command:
         ^
index.docbook:756: parser error : Entity 'koffice' not defined
nds in <literal role="extension">.deb</literal> (Debian Package file), &koffice;
                                                                               ^
index.docbook:761: parser error : Entity 'koffice' not defined
&koffice; can be installed with the following commands:</para>
         ^
index.docbook:771: parser error : Entity 'koffice' not defined
That's all. &koffice; should now be installed on your system.
                     ^
index.docbook:776: parser error : Entity 'kpackage' not defined
such as &kpackage; or <application>GnoRPM</application>, installed on
                  ^
index.docbook:805: parser error : Entity 'koffice' not defined
If you want to build &koffice; from source code, you should:
                              ^
index.docbook:811: parser error : Entity 'koffice' not defined
in working condition (excluding &koffice; of course). You can find
                                         ^
index.docbook:816: parser error : Entity 'koffice' not defined
Download the &koffice; source file into a temporary folder.
                      ^
index.docbook:820: parser error : Entity 'RedHat' not defined
(&RedHat; Package Management file), the source code for &koffice; can
         ^
index.docbook:820: parser error : Entity 'koffice' not defined
(&RedHat; Package Management file), the source code for &koffice; can
                                                                 ^
index.docbook:825: parser error : Entity 'koffice' not defined
the source code for &koffice; can be installed with:
                             ^
index.docbook:828: parser error : Entity 'koffice' not defined
<step><para>The source code for &koffice; should now be installed on
                                         ^
index.docbook:836: parser error : Entity 'documentation.index' not defined
&documentation.index;
                     ^
make[2]: *** [doc/koffice/index.cache.bz2] Error 1
make[1]: *** [doc/koffice/CMakeFiles/koffice-handbook.dir/all] Error 2
make: *** [all] Error 2
makeobj[0]: Leaving directory `/home/devel/kde4/build/koffice'



Francisco Fernandes - Chicao
...........................................................................
"Who willingly carries the hard, also carries the less difficult ..."
Lao Tsé, in Tao Te Ching
slangkamp
KDE Developer
Posts
607
Karma
4
You probably need to install the docbook-xml package. Common problem on arch.
User avatar
chicao
Registered Member
Posts
12
Karma
0
OS
Thanks slangkamp, that did worked.

However, after the make install completes its task, appears the following:


Code: Select all
...

-- Set runtime path of "/home/devel/kde4/inst/lib/libmsooxml.so.7.0.0" to "/home/devel/kde4/inst/lib"
-- Installing: /home/devel/kde4/inst/share/mime/packages/msooxml-all.xml
- /home/devel/.local/share
- /usr/share
- /usr/local/share


Note that '/home/devel/kde4/inst/share' is not in the search path
set by the XDG_DATA_HOME and XDG_DATA_DIRS
environment variables, so applications may not
be able to find it until you set them. The
directories currently searched are:


-- Installing: /home/devel/kde4/inst/lib/kde4/libxsltexport.so
-- Set runtime path of "/home/devel/kde4/inst/lib/kde4/libxsltexport.so" to "/home/devel/kde4/inst/lib"
-- Installing: /home/devel/kde4/inst/share/kde4/services/xslt_export.desktop
-- Installing: /home/devel/kde4/inst/share/apps/xsltfilter/export/kword/xslfo/main.xsl
-- Installing: /home/devel/kde4/inst/share/apps/xsltfilter/export/kword/xslfo/kword2xslfo-table.xsl
-- Installing: /home/devel/kde4/inst/lib/kde4/libxsltimport.so
-- Set runtime path of "/home/devel/kde4/inst/lib/kde4/libxsltimport.so" to "/home/devel/kde4/inst/lib"
-- Installing: /home/devel/kde4/inst/share/kde4/services/xslt_import.desktop
makeobj[0]: Leaving directory `/home/devel/kde4/build/koffice'



I tryed to add the dir especified in the warning in the two variables that it pointed out:

Code: Select all
[devel@muladhara krita]$ env | grep XDG_DATA
XDG_DATA_HOME=/home/devel/.local/share:/home/devel/kde4/inst/share/:/home/devel/kde4/inst/share/
XDG_DATA_DIRS=/usr/share:/usr/local/share://home/devel/kde4/inst/share:/home/devel/kde4/inst/share


And after that, run krita:

Code: Select all

[devel@muladhara bin]$ pwd
/home/devel/kde4/inst/bin
[devel@muladhara bin]$ ./krita
krita(16902)/koffice (lib komain): "krita" part.desktop not found.

krita(16902)/koffice (lib komain): Run 'kde4-config --path services' to see which directories were searched, assuming kde startup had the same environment as your current shell.

krita(16902)/koffice (lib komain): Check your installation (did you install KOffice in a different prefix than KDE, without adding the prefix to /etc/kderc ?)


My build dir is in my $HOME/kde4/build and install dir is $HOME/kde4/inst.
Running the following:

Code: Select all
[devel@muladhara krita]$ kde4-config --path services
/home/devel/.kdemod4/share/kde4/services/:/usr/share/kde4/services/


Another thing I tryed was running the kbuildsycoca4 ...

Code: Select all
[devel@muladhara bin]$ kbuildsycoca4
kbuildsycoca4 running...
kbuildsycoca4(16953)/kdecore (services) KServicePrivate::init: The desktop entry file  "/home/devel/kde4/inst/share/applications/kde4/koffice.desktop"  has Type= "Application"  but no Exec line

kbuildsycoca4(16953) KBuildServiceFactory::createEntry: Invalid Service :  "/home/devel/kde4/inst/share/applications/kde4/koffice.desktop"


... but without success.

Which detail I'm missing?

Thanks in advance.


Francisco Fernandes - Chicao
...........................................................................
"Who willingly carries the hard, also carries the less difficult ..."
Lao Tsé, in Tao Te Ching
slangkamp
KDE Developer
Posts
607
Karma
4
I get:
Code: Select all
sven@svennotebook:~/kde/bin$ kde4-config --path services
/home/sven/.kde/share/kde4/services/:/home/sven/kde/share/kde4/services/:/usr/share/kde4/services/


Maybe check where KDEDIR and KDEDIRS point.
User avatar
Kubuntiac
Registered Member
Posts
786
Karma
2
If you're on Arch, might I suggest a much easier way... Enkithan posted a PKGBUILD in these very forums. Save it as PKGBUILD in the directory you'd like Kirta and do makepkg -S. When it's done do sudo pacman -U and the name of the package built.

As long as you have the build group (build-essential?) installed, it will take care of installing all dependencies and compiling everything.
User avatar
chicao
Registered Member
Posts
12
Karma
0
OS
@slangkamp, I fixed my $KDEDIR and $KDEDIRS, since it was pointing to a inexistent directory (it's $HOME/kde4, not $HOME/kde).
But now the error is:
Code: Select all
[devel@muladhara bin]$ pwd
/home/devel/kde4/inst/bin
[devel@muladhara bin]$ ./krita
krita(10769)/koffice (lib komain) KoDocumentEntry::createDoc: ""


Any ideas?

@Kubuntiac, Thanks for the tip , but that was the first thing I tried and the error while generating the package was the same as compiling and installing the source. Since I got installed and the error is after I try to run Krita, I wanna go to the very end (most like a honor quest :)

Another point is to understand some questions behind path configuration in KDE development. It's very helpful when you understand the configuration, for instance, to use with Kdevelop.

PS.: If this issue become too long or too out of context, please tell me when and I create a thread for the issue. :)


Francisco Fernandes - Chicao
...........................................................................
"Who willingly carries the hard, also carries the less difficult ..."
Lao Tsé, in Tao Te Ching
User avatar
Kubuntiac
Registered Member
Posts
786
Karma
2
I have no idea if this has anything to do with your problem or not... but a ridiculous number of *my* problems have been solved by running kbuildsycoca4 just before running krita, and always running krita from the command line (ie not clicking the binary in Dolphin)
User avatar
chicao
Registered Member
Posts
12
Karma
0
OS
Thanks for the reply, Kubuntiac.
I run kbuildsycoca4 before, but it wasn't working.
Then I checked all the steps I made in the Building Koffice wiki and it
missed the enviroment variables setup:

Code: Select all
[devel@muladhara bin]$ export KDEDIRS=$KDEDIRS:$HOME/kde4/inst
[devel@muladhara bin]$ export PATH=$PATH:$HOME/kde4/inst/bin


I run the kbuildsycoca4 and now its working just fine. :)

Thankyou all for the help.

Regards


Francisco Fernandes - Chicao
...........................................................................
"Who willingly carries the hard, also carries the less difficult ..."
Lao Tsé, in Tao Te Ching
User avatar
Kubuntiac
Registered Member
Posts
786
Karma
2
Awesome! Glad it's working for you :D


Bookmarks



Who is online

Registered users: Bing [Bot], gfielding, Google [Bot], markhm, sethaaaa, Sogou [Bot], Yahoo [Bot]