+  Kiba Dock
|-+  Kiba-Dock
| |-+  Kiba Dock
| | |-+  How to easily install/update from SVN - easyKiba [UPDATED on 18/08/2007]
« previous next »
Pages: 1 2 [3] 4 5 6 Print
Author Topic: How to easily install/update from SVN - easyKiba [UPDATED on 18/08/2007]  (Read 51990 times)
danielb
Lead Developer
Veteran
*****
Offline Offline

Posts: 910



View Profile Email
« Reply #30 on: May 19, 2007, 08:57:09 AM »

yeah right
Logged
danielb
Lead Developer
Veteran
*****
Offline Offline

Posts: 910



View Profile Email
« Reply #31 on: May 24, 2007, 10:28:59 AM »

for translating, you can take a look here: http://www.gnu.org/software/gettext/manual/gettext.html#sh
Logged
SpUpUz
New Guy
*
Offline Offline

Posts: 17


View Profile Email
« Reply #32 on: May 29, 2007, 06:25:33 AM »

No package 'libxml' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables LIBXML_CFLAGS
and LIBXML_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.


1) Checking your GNU/Linux distro                               [    OK    ]
2) Selecting components to install                              [    OK    ]
3) Verifying if components are not already installed            [    OK    ]
4) Fetching SVN repos : kibadock                                [    OK    ]
5) Fetching SVN repos : kibaplugins                             [    OK    ]
6) Fetching SVN repos : gaimplugin                              [    OK    ]
7) Fetching SVN repos : kibadbusplugins                         [    OK    ]
Cool Installing components : kibadock                             [    KO    ]
9) Installing components : kibaplugins
10) Installing components : gaimplugin
11) Installing components : kibadbusplugins
12) Verifying installation



--------INFO-----------------------------------------------------------------
 Could not finish operation !
-----------------------------------------------------------------------------
 Please scroll up your screen to see the error messages the script returned.
-----------------------------------------------------------------------------

Logged
danielb
Lead Developer
Veteran
*****
Offline Offline

Posts: 910



View Profile Email
« Reply #33 on: May 29, 2007, 07:16:35 AM »

what about installing libxml-dev?
Logged
neoAKiRAz
New Guy
*
Offline Offline

Posts: 38


View Profile Email
« Reply #34 on: May 31, 2007, 03:10:53 PM »

Successfully installed in Kubuntu. Great job! Smiley

I don't remember right now which, but some package was missing in my system at build/installation of kibaplugins, so the script returned an error. I installed the package and re-ran the script but it would tell me kiba was already installed. So I used the -u option and selected only kibaplugins for update. That did the job Smiley
Congrats bochecha!
Logged
bochecha
Writer
Insistent
***
Offline Offline

Posts: 144



View Profile
« Reply #35 on: May 31, 2007, 10:07:00 PM »

Great !

Happy that it can work on two of the main distros Smiley
Logged

tarnok
New Guy
*
Offline Offline

Posts: 1


View Profile Email
« Reply #36 on: June 02, 2007, 04:49:34 AM »

Code:
./easyKiba: line 191: ./autogen.sh: No such file or directory







1) Checking your GNU/Linux distro                               [    OK    ]
2) Selecting components to update                               [    OK    ]
3) Verifying if those components can be updated                 [    OK    ]
4) Fetching SVN repos : akamaru                                 [    OK    ]
5) Fetching SVN repos : kibadock                                [    OK    ]
6) Fetching SVN repos : kibaplugins                             [    OK    ]
7) Fetching SVN repos : gaimplugin                              [    OK    ]
8) Fetching SVN repos : kibadbusplugins                         [    OK    ]
9) Updating components : akamaru                                [    OK    ]
10) Updating components : kibadock                              [    KO    ]
11) Updating components : kibaplugins
12) Updating components : gaimplugin
13) Updating components : kibadbusplugins
14) Verifying update



--------INFO-----------------------------------------------------------------
 Could not finish operation !
-----------------------------------------------------------------------------
 Please scroll up your screen to see the error messages the script returned.
-----------------------------------------------------------------------------

I found out it is in kibaplugins/trunk
Logged
bochecha
Writer
Insistent
***
Offline Offline

Posts: 144



View Profile
« Reply #37 on: June 24, 2007, 05:12:27 AM »

Hi tarnoc !

Did you follow the instructions I provided in the first post ? I will write them here again :
Code:
$ cd /anywhere/you/have/write/access
$ mkdir kiba-dock
$ cd kiba-dock
$ easyKiba --install

If that's what you did, I'd be happy to have more informations so that I can improve the script Smiley

By the way, script updated !
Logged

HeLLWAR
New Guy
*
Offline Offline

Posts: 1


View Profile Email
« Reply #38 on: June 29, 2007, 05:39:15 AM »

Code:
prefs.c:35:27: error: libxml/parser.h: Arquivo ou diretório não encontrado
prefs.c:36:25: error: libxml/tree.h: Arquivo ou diretório não encontrado
prefs.c: In function ‘kiba_prefs_update_config_file’:
prefs.c:238: error: ‘LIBXML_TEST_VERSION’ undeclared (first use in this function)
prefs.c:238: error: (Each undeclared identifier is reported only once
prefs.c:238: error: for each function it appears in.)
prefs.c:240: error: expected ‘;’ before ‘pref_file’
prefs.c: At top level:
prefs.c:713: error: expected declaration specifiers or ‘...’ before ‘xmlNode’
prefs.c: In function ‘parse_option’:
prefs.c:714: error: ‘xmlNode’ undeclared (first use in this function)
prefs.c:714: error: ‘cur_node’ undeclared (first use in this function)
prefs.c:726: error: ‘option_element’ undeclared (first use in this function)
prefs.c:727: error: ‘XML_ELEMENT_NODE’ undeclared (first use in this function)
prefs.c: At top level:
prefs.c:774: error: expected declaration specifiers or ‘...’ before ‘xmlNode’
prefs.c: In function ‘parse_options’:
prefs.c:775: error: ‘xmlNode’ undeclared (first use in this function)
prefs.c:775: error: ‘cur_node’ undeclared (first use in this function)
prefs.c:777: error: ‘a_element’ undeclared (first use in this function)
prefs.c:778: error: ‘XML_ELEMENT_NODE’ undeclared (first use in this function)
prefs.c:785: error: too many arguments to function ‘parse_option’
prefs.c:787: error: too many arguments to function ‘parse_options’
prefs.c: In function ‘write_schema_to_config’:
prefs.c:793: error: ‘xmlDoc’ undeclared (first use in this function)
prefs.c:793: error: ‘doc’ undeclared (first use in this function)
prefs.c:794: error: ‘xmlNode’ undeclared (first use in this function)
prefs.c:794: error: ‘root_element’ undeclared (first use in this function)
prefs.c:805: error: too many arguments to function ‘parse_options’
prefs.c: At top level:
prefs.c:896: error: expected declaration specifiers or ‘...’ before ‘xmlNode’
prefs.c: In function ‘create_option_from_node’:
prefs.c:898: error: ‘xmlNode’ undeclared (first use in this function)
prefs.c:898: error: ‘cur_node’ undeclared (first use in this function)
prefs.c:900: error: ‘a_element’ undeclared (first use in this function)
prefs.c:901: error: ‘xmlChar’ undeclared (first use in this function)
prefs.c:901: error: ‘lang’ undeclared (first use in this function)
prefs.c:903: error: ‘XML_ELEMENT_NODE’ undeclared (first use in this function)
prefs.c: At top level:
prefs.c:980: error: expected declaration specifiers or ‘...’ before ‘xmlNode’
prefs.c: In function ‘create_subsection_from_node’:
prefs.c:982: error: ‘xmlNode’ undeclared (first use in this function)
prefs.c:982: error: ‘cur_node’ undeclared (first use in this function)
prefs.c:984: error: ‘a_element’ undeclared (first use in this function)
prefs.c:985: error: ‘xmlChar’ undeclared (first use in this function)
prefs.c:985: error: ‘lang’ undeclared (first use in this function)
prefs.c:987: error: ‘XML_ELEMENT_NODE’ undeclared (first use in this function)
prefs.c:1014: error: too many arguments to function ‘create_option_from_node’
prefs.c: At top level:
prefs.c:1020: error: expected declaration specifiers or ‘...’ before ‘xmlNode’
prefs.c: In function ‘create_section_from_node’:
prefs.c:1022: error: ‘xmlNode’ undeclared (first use in this function)
prefs.c:1022: error: ‘cur_node’ undeclared (first use in this function)
prefs.c:1024: error: ‘a_element’ undeclared (first use in this function)
prefs.c:1025: error: ‘xmlChar’ undeclared (first use in this function)
prefs.c:1025: error: ‘lang’ undeclared (first use in this function)
prefs.c:1027: error: ‘XML_ELEMENT_NODE’ undeclared (first use in this function)
prefs.c:1064: error: too many arguments to function ‘create_subsection_from_node’
prefs.c: At top level:
prefs.c:1070: error: expected declaration specifiers or ‘...’ before ‘xmlNode’
prefs.c: In function ‘create_tree_from_node’:
prefs.c:1071: error: ‘xmlNode’ undeclared (first use in this function)
prefs.c:1071: error: ‘cur_node’ undeclared (first use in this function)
prefs.c:1073: error: ‘a_element’ undeclared (first use in this function)
prefs.c:1074: error: ‘XML_ELEMENT_NODE’ undeclared (first use in this function)
prefs.c:1075: error: too many arguments to function ‘create_section_from_node’
prefs.c:1078: error: too many arguments to function ‘create_tree_from_node’
prefs.c: In function ‘create_xml_tree_from_file’:
prefs.c:1085: error: ‘xmlDoc’ undeclared (first use in this function)
prefs.c:1085: error: ‘doc’ undeclared (first use in this function)
prefs.c:1086: error: ‘xmlNode’ undeclared (first use in this function)
prefs.c:1086: error: ‘root_element’ undeclared (first use in this function)
prefs.c:1097: error: too many arguments to function ‘create_tree_from_node’
prefs.c: In function ‘kiba_prefs_get_schema’:
prefs.c:1139: error: ‘LIBXML_TEST_VERSION’ undeclared (first use in this function)
prefs.c:1141: error: expected ‘;’ before ‘schema_data’
make[3]: ** [prefs.o] Erro 1
make[3]: Saindo do diretório `/home/HeLL/dock/kibadock/src'
make[2]: ** [all] Erro 2
make[2]: Saindo do diretório `/home/HeLL/dock/kibadock/src'
make[1]: ** [all-recursive] Erro 1
make[1]: Saindo do diretório `/home/HeLL/dock/kibadock'
make: ** [all] Erro 2

1) Checking your GNU/Linux distro                               [    OK    ]
2) Selecting components to install                              [    OK    ]
3) Verifying if components are not already installed            [    OK    ]
4) Fetching SVN repos : kibadock                                [    OK    ]
5) Fetching SVN repos : kibaplugins                             [    OK    ]
6) Fetching SVN repos : gaimplugin                              [    OK    ]
7) Fetching SVN repos : kibadbusplugins                         [    OK    ]
8) Installing components : kibadock                             [    KO    ]
9) Installing components : kibaplugins
10) Installing components : gaimplugin
11) Installing components : kibadbusplugins
12) Verifying installation



--------INFO-----------------------------------------------------------------
 Could not finish operation !
-----------------------------------------------------------------------------
 Please scroll up your screen to see the error messages the script returned.
-----------------------------------------------------------------------------

[HeLL@localhost dock]$

In fedora 7
this error happened ....
note:akamaru already installed.
thanks
« Last Edit: June 29, 2007, 05:42:46 AM by HeLLWAR » Logged
bochecha
Writer
Insistent
***
Offline Offline

Posts: 144



View Profile
« Reply #39 on: July 01, 2007, 03:22:30 AM »

I had exactly the same error on my Fedora 7.

The only solution I could find is to create a symbolic link in /usr/include called libxml and pointing to /usr/include/libxml2/libxml

Seems to be a distro/packaging issue of libxml2 in Fedora 7 as it worked fine in FC6 (the libxml include folder was in the same place though) and no one ever encountered this issue in another distro (or no one spoke about it Smiley)

If you an find a less dirty way, I take it Smiley
Logged

danielb
Lead Developer
Veteran
*****
Offline Offline

Posts: 910



View Profile Email
« Reply #40 on: July 01, 2007, 03:57:11 AM »

someone in a gentoo forums fixed it a bit cleaner Wink
Code:
env LIBXML_CFLAGS=/usr/lib/libxml2.so LIBXML_LIBS=/usr/lib/libxml2.so KIBA_DOCK_CFLAGS=/usr/lib/libxml2.so KIBA_DOCK_LIBS=/usr/lib/libxml2.so emerge -va kiba-dock
but another developer, malwak, has the same issue and said that he will look into that, so maybe its fixed soon
Logged
bochecha
Writer
Insistent
***
Offline Offline

Posts: 144



View Profile
« Reply #41 on: July 01, 2007, 05:57:13 AM »

I can see "emerge" in this command, is it Gentoo only ?

Glad it moght be fixed soon.

And also glad you finally found some devsto help you Smiley

How many are you ?
Logged

danielb
Lead Developer
Veteran
*****
Offline Offline

Posts: 910



View Profile Email
« Reply #42 on: July 01, 2007, 06:18:42 AM »

you know, since i requested help in the news section i get emails from developers who wanna help every few days. but none of them sended me a patch yet Sad
i hope the reason is that it takes some time getting into a code written by someone else.

emerge configures, compiles and installs a package, just replace it with the way your distro handles it, important are the environment variables
Logged
frik
New Guy
*
Offline Offline

Posts: 5


View Profile Email
« Reply #43 on: July 01, 2007, 10:45:57 AM »

on my debian it work good Wink
but i have one problem. I get this when I add luncher :
Code:
Error (launcher.c @ line 406):
        Failed to get key 'GroupMember' from file '/home/frik/.kiba-dock/launcher/htop.desktop'
 Segmentation fault
when I use script everything was ok. meaby I don't have something?
Logged
muhmuh
New Guy
*
Offline Offline

Posts: 9


View Profile Email
« Reply #44 on: July 23, 2007, 10:30:21 AM »

I was forced to reinstall my linux - dont ask why.
So when i use your script i get this:


checking for intltool...
found intltool
checking for libtoolize...
found libtoolize
checking for automake...
found automake
checking for autoconf...
found autoconf
Running 'autoreconf -v --install'...
autoreconf: Entering directory `.'
autoreconf: configure.in: not using Gettext
autoreconf: running: aclocal  --output=aclocal.m4t
autoreconf: `aclocal.m4' is created
autoreconf: configure.in: tracing
autoreconf: configure.in: creating directory config
autoreconf: running: libtoolize --copy
Putting files in AC_CONFIG_AUX_DIR, `config'.
autoreconf: `aclocal.m4' is unchanged
autoreconf: running: /usr/bin/autoconf
autoreconf: running: /usr/bin/autoheader
autoreconf: running: automake --add-missing --copy
configure.in: installing `config/install-sh'
configure.in: installing `config/mkinstalldirs'
configure.in: installing `config/missing'
Makefile.am: installing `./INSTALL'
libakamaru_la_LDFLAGS: variable `export_symbols' is used but `export_symbols' is undefined
src/Makefile.am: installing `config/depcomp'
autoreconf: automake failed with exit status: 1


I dont know what to do  Cry
This script worked in the past...
any hints maybe  Smiley
Logged
Pages: 1 2 [3] 4 5 6 Print 
« previous next »
Jump to:  


Login with username, password and session length

Powered by MySQL Powered by PHP Powered by SMF 1.1.10 | SMF © 2006-2009, Simple Machines LLC Valid XHTML 1.0! Valid CSS!