| Summary: | Make gives error "digikamthumbnail.cpp:662: error: visibility arg must be one of "default", "hidden", "protected" or "internal" | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Stephan van den Akker <memelink.akker> |
| Component: | Portability-Compilation | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | caulier.gilles |
| Priority: | NOR | ||
| Version: | 0.7.3 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Stephan van den Akker
2005-07-03 00:25:38 UTC
Upgrade KDE to >= 3.3.1. This doesn't solve my problem. the "dependency" part of both the kde extragear/digikam website and the README file clearly state a the need for "KDE 3.x", not "KDE >=3.3.1". It should be possible to find a less drastic solution. I simply can't afford to mess around with my system the way you propose. Swapping out KDE is a big deal for an average user like me. Generally speaking, upgrades like these should not be necessary on a perfectly working system that is less than 1 year old. This doesn't solve my problem. the "dependency" part of both the kde extragear/digikam website and the README file clearly state a the need for "KDE 3.x", not "KDE >=3.3.1". It should be possible to find a less drastic solution. I simply can't afford to mess around with my system the way you propose. Swapping out KDE is a big deal for an average user like me. Generally speaking, upgrades like these should not be necessary on a perfectly working system that is less than 1 year old. The fix is in KDE 3.3.1. Your two options are: 1) update to KDE 3.3.1 or better; or downgrade to KDE 3.2.3 or lower or 2) don't use a compiler that supports -fvisibility If you use a compiler with -fvisibility, you CANNOT use KDE 3.3.0. You can use other versions. On 2 Jul 2005 23:40:42 -0000, Thiago Macieira <thiago@kde.org> wrote: [bugs.kde.org quoted mail] Both these options are more drastic compared making the user simply modify the kdemacros.h file to rectify the error in definition of visibility attributes. Should that be give as an option too? A simply change of value from "visibile" to "default" in Kde macros.h seems to be a perfect solution to me, is there any hidden problem with such a solution? AFAIK Fedora Core 3 gives KDE3.3.0-5 and FC3 must be a large user base, we can't ask all such users to do some small hacking, we need to do ourself or release a RPM package with the required patch. Just a suggestion. Vardhman PS: I have faced this problem and it really took lot of time to understand what the problem was. Finally I compiled the code by switching off the Visibilty stuff throught the configure.in.in files. Thanks for your suggestion, Vardman! This got rid of the show-stopping bug for me! Now I am happily browsing my digital photo collection with version 0.7.3. (The compiler warnings I mentioned are still there though). You mentioned RPM-packages. SuSE does tend to supply fairly up-to-date ones, but they depend heavily on the accompanying "bleeding edge" KDE-packages. I have mixed experiences with those, so I don't want to install them on "production" systems. Greetings, and many thanks! just to note, I am running KDE 3.3.1 on FC3 and the problem exists. Modifying kdemacros.h resolved the problem; but upgrading KDE doesn't |