KDE-Forum.org

You haven't any errors on ./configure ? With my MDK 9.2, I have error....

See this topic :

http://www.kde-forum.org/viewtopic.php?t=2244

And good luck !!

i have the same problem as you.

But how do you do to solve the fact that kopete installation directory is /usr/local/kde .

I try to copy all the kde directory into /usr/local, but it gives me only the possibility to execute from the konsole.

What's more : kopete does not display its icon in the status bar. So as for the plugins it is a problem of directory. It doesnt know where to look for...

perhaps should i try to copy kde directory directly into .usr . But i fears me a bit .

I did not find your /etc/kderc file too.

okay, i got it to work

If compilation works even if there is the message in the configure. You should be able to open kopete but without any plugins nor the icon.

So uninstall it then :

modifiy the "configure" file.
look for ' ac_default_prefix=${KDEDIR:-/usr/local/kde} '
and modify it as : 'ac_default_prefix=${KDEDIR:-/usr}'

Then ./configure
make
su -c "make install" as usual .

that works for me with Mandrake 9.2 .

ok lol, i'm a real NB :

it's simple doing : ./configure --prefix=/usr in place of modifing the configure file.

I always have the tcp.h error in ./configure and I don't understand why I must change the kde path because mine is in /usr/local/kde

After compilation, when I launch kopete I have some problem :

kopete: [KopetePlugin* KopetePluginManager::loadPluginInternal(const QString&)] kopete_chatwindow
kopete: WARNING: [KopetePlugin* kopetePluginManager::loadPluginInternal(const QString&)] Unable to find a plugin named 'kopete_chatwindow'!

And as you see the plugins configuration is non-existent !?
:cry:

If your prefix is /usr/local/kde, then maybe its not a prefix problem, but rather you have to run kbuioldsycoca manually. Not sure if thats your problem or not, but its worth a shot.

I run kbuildsycoca like this $kbuildsycoca but nothing append!!

What is this ?

And do you think plugins configuration is linked by tcp.h problem ?

checking linux/tcp.h usability... no
checking linux/tcp.h presence... yes
configure: WARNING: linux/tcp.h: present but cannot be compiled
configure: WARNING: linux/tcp.h: check for missing prerequisite headers?
configure: WARNING: linux/tcp.h: see the Autoconf documentation
configure: WARNING: linux/tcp.h: section "Present But Cannot Be Compiled"
configure: WARNING: linux/tcp.h: proceeding with the preprocessor's result
configure: WARNING: linux/tcp.h: in the future, the compiler will take precedence
configure: WARNING: ## ------------------------------------------ ##
configure: WARNING: ## Report this to the AC_PACKAGE_NAME lists. ##
configure: WARNING: ## ------------------------------------------ ##
checking for linux/tcp.h... yes

Thanks for your help !

Okay, I've done exactly as suggested above, uninstalling, configuring with -prefix=/usr, making, make installing then running kbuildsycoca, but I still get an "Empty Page" message when I click on "configure kopete".
When I run from the command line, one of the first warnings that comes up says "servicetype Kopete/Plugin not found" and I assume the following "plugin not found" messages stem from this.

Any ideas at all? I'm getting pretty fed up to be honest...
:x

Okay, I should really learn to read FAQs more thoroughly.

Kopete will work fine (in Suse9.0 at least) if you install in your kde home directory:
type "which konqueror"
- you should see something like "/opt/kde3/bin/konqueror"; in which case, /opt/kde3 is your kde home directory.
type "./configure --prefix=/opt/kde3"
"make"
"make install"
"make clean"
"kbuildsycoca"

That's it. It wasn't liking me installing in /usr even though I added the path to the prefix in /etc/kde3rc, and adding an environment variable didn't help either, so it seems to fully communicate with the kde plugin files, this is where it should be installed. I just feel stoopid for not looking properly through the FAQs.
:roll:

I am asking me if I can see kopete worked a day !!??

I alaways do "which konqueror" that say : /usr/bin/konqueror
So I do "./configure --prefix=/usr" then "make" and I launch kopete.

And this warning appear :
kopete: WARNING: [KopetePlugin* KopetePluginManager::loadPluginInternal(const QString&)] Unable to find a plugin named 'kopete_chatwindow'!

So I search for this file "kopete_chatwindow" and I find it here :
/usr/kopete-0.8.0/kopete/kopete/chatwindow/.libs/kopete_chatwindow.so
/usr/kopete-0.8.0/kopete/kopete/chatwindow/.libs/kopete_chatwindow.lai
/usr/kopete-0.8.0/kopete/kopete/chatwindow/.libs/kopete_chatwindow.la
/usr/kopete-0.8.0/kopete/kopete/chatwindow/kopete_chatwindow.la

So, where is the problem ??
:?

This is strange, that is exactly where the plugin should be. Have you tried running kbuildsycoca manually?

i had exactly the same problem, and here is what i did.
from console type:

> setenv KDEDIR=/usr/local/kde/
> kbuildsycoca
> /usr/local/kde/bin/kopete

it worked for me. the bad thing is i have to do this every time i wanna start kopete. i don't know a better solution (there must be a better solution - i put this on .bashrc but didn't worked).
until i'll find it i'll use this one.

Quoted

Original von djtrippin

This is strange, that is exactly where the plugin should be. Have you tried running kbuildsycoca manually?

No because it is launched with kopete :

Loading required GL library /usr/X11R6/lib/libGL.so.1.2
kbuildsycoca running...
Loading required GL library /usr/X11R6/lib/libGL.so.1.2

But if I run it manualy there is no change and I have a warning :

Warning: kbuildsycoca is unable to register with DCOP.

Is DCOP required by kopete ?

Thanks for your help

cornel -
SETENV is a c/tc-shell command so it shouldn't go in .bashrc. In bash the line would be something like:
KDEDIR=$KDEDIR:/your/path/wherever; export KDEDIR
which might be best in .profile rather than .bashrc. But if you're using c-shell or tc-shell, I think it goes in .cshrc. You shouldn't have to type the SETENV command in every time, putting it in the dot file will achieve the same result. And then you shouldn't have to include the full path when you run kopete either. If it doesn't work, I don't know why.

fdp3 -
just to check - are you uninstalling (make uninstall) before each ./configure attempt? Otherwise it won't work. Then you 'make' then 'make install' and it should work. What Linux distro are you using?

Basically, your system should already know where to look for kde bins and headers and stuff, so if installed into the kde home dir, everything should be ok and you shouldn't need to add anything to your env variables. But then, when was anything ever simple? Try uninstalling and doing everything again as outlined above...
Good luck!

Quoted

Original von AngryBoy

cornel -
fdp3 -
just to check - are you uninstalling (make uninstall) before each ./configure attempt? Otherwise it won't work. Then you 'make' then 'make install' and it should work. What Linux distro are you using?

Basically, your system should already know where to look for kde bins and headers and stuff, so if installed into the kde home dir, everything should be ok and you shouldn't need to add anything to your env variables. But then, when was anything ever simple? Try uninstalling and doing everything again as outlined above...
Good luck!

Hello,

I never do "make uninstall" because I don't wan't to delete the old RPM version in my computer.
So, I always do "./configure" and "make".
That's always work with kopete 0.7.5 and the oldest.

But It seems to be not working with kopete 0.8.0. Perhaps kopete 0.7.5 uses old plugins that are in my computer and these plugins don't work with 0.8.0

I do the "make uninstall" then "configure", "make" and "make install" and it work fine. :?

And kopete 0.8.0 is beautifull !!

Thanks for all :wink: