![]() Registered Member ![]()
|
I want to fix some bugs for akregator so I decided to get all akonadi, kdepimlibs, kdepim and kdepim-runtime from git and then build all of them. On start up, akregator complains that it can not find akregatorpart, though all the libs are in their correct position because ldd command doesn't complain about anything:
I'm really need help from the dev here. This is the first time I get in this situation so I have no idea what to do. |
![]() Administrator ![]()
|
First, Welcome to KDE development.
In order to allow Akregator to work in this case, you need to change a few KDE environment variables. The environment variables to change are: PATH, LD_LIBRARY_PATH and KDEDIRS. If you source the below commands before attempting to build and run Akregator, you should be fine.
If it still cannot find the akregatorpart, try running "kbuildsycoca4" after changing KDEDIRS. You may wish to place these environment variables in a script in ~/.kde4/env (or ~/.kde/env/ depending on your distribution). This script must have a *.sh ending, and be executable for that to work however.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
![]() Registered Member ![]()
|
Thanks for replying me.
I already have a file kde-devel-env:
Before building kdepim, I've already excuted this command:
Is there anything else can cause the problem I'm facing? |
![]() Administrator ![]()
|
Are you launching Akregator from the same terminal used to build kdepim?
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
![]() Registered Member ![]()
|
Yes. Also running it by clicking on it in the /bin directory doesn't make any different. |
![]() Administrator ![]()
|
Hmm.... It could be a kdeinit4 based application.
Try running "kdeinit4" after kbuildsycoca4, and see if that works.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
![]() Registered Member ![]()
|
There are errors when running kdeinit4:
|
![]() Administrator ![]()
|
Not sure why those error messages would occur. Messages of that kind likely cause problems for kbuildsycoca4 too as well.
Can you try disabling the KDETMP line in your development environment script?
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
![]() Registered Member ![]()
|
Forgot to thank you. Really nice of you taking your time to help me.
kbuildsycoca4 runs fine without any problem. :-?
Do I need to rebuild after that? |
![]() Administrator ![]()
|
No rebuild is required, it is just an environment option change.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
![]() Registered Member ![]()
|
Still no different after re-source the file. |
![]() Administrator ![]()
|
Hmm... weird.
Can you try unsetting both the KDEVARTMP and KDETMP variables please? Note you will need to start a new shell - sourcing the script again won't fix it.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
![]() Registered Member ![]()
|
I've comment out those TMP line, logged out then logged in, re-sourced it but the problem still persists.
![]() |
![]() Administrator ![]()
|
Ok, the failure of the kdeinit4 command indicates something unusual is happening. This is probably linked to the failure of Akregator.
Do you have KDE PIM applications installed from distribution packages?
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
![]() Registered Member ![]()
|
I have uninstalled akregator (ubuntu version) before built it from source to avoid it linking to the old version. Strange thing is: If I keep the ubuntu-distributed version, akregator will use that akregatorpart instead of the part built from source, although ldd command has shown the right linking (seen the first post).
|
Registered users: Baidu [Spider], Bing [Bot], Google [Bot]