Summary: | missing AKONADI_PARAM_EXTERNALPAYLOAD to compile kdepimlibs | ||
---|---|---|---|
Product: | [Applications] kdepimlibs | Reporter: | Unknown <null> |
Component: | syndication | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | andresbajotierra, Frank-Roscher |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Other | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Unknown
2009-04-05 15:34:53 UTC
You need the trunk (aka development) version of Akonadi. Any released version is not enough. I get the same here, using kdesvn-build. Apparently the system's Akonadi in /usr is being used instead of the freshly-compiled trunk version in my home directory. This is the only part of KDE where I encounter such a problem. This suggests to me that there is indeed a problem to be fixed, but I guess it could be kdesvn-build's fault, too. I am very new here! I got the trunk version of akonadi and the error is no more there. I use the cmakeke to do the job. I cannot confirm the comment #2 from Frank. @Frank: probably the CMake (cached) scripts/files are still using the global (/usr) Akonadi version instead your local one. You may need to clean this cmake files and then try again to CMake to properly recognize and use the local one. Thanks (In reply to comment #4) Dario: Thank you for your help, but in my case it was indeed kdesvn-build's fault :) I checked its changelog in trunk and found this: Make kdesvn-build set the CMAKE_PREFIX_PATH environment variable, which allows builds to complete successfully even when system packages are installed. With this, it works. I guess it was just luck that no other part of KDE failed. So, if somebody else complains to you about such a problem just tell him to use the trunk version of the script. I think this bug can be closed now. ok, closing |