Summary: | proxymodeltestsuite fails to build (on DragonFly) | ||
---|---|---|---|
Product: | [Unmaintained] kdelibs | Reporter: | Alex Hornung <alexh> |
Component: | kdeui | Assignee: | kdelibs bugs <kdelibs-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | christoph, rakuco, steveire |
Priority: | NOR | ||
Version: | SVN | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Other | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Alex Hornung
2010-11-02 22:54:09 UTC
CC'ing Stephen Kelly, the author of the tests. By the way, is DragonFly still on gcc 4.1? IIRC, Qt (and consequently KDE) officially support gcc from version 4.2 on. We also have gcc 4.4 in base, but it's not (yet) the default system compiler. It seems this works fine with gcc44. Isn't there a way to check for the gcc version without messing up other compilers when doing the cmake configuration? I thought there was a check in place already, but apparently FindKDE4Internal.cmake in kdelibs/cmake/modules only checks for the gcc version internally to set some compiler flags. It is possible to patch it locally to only compile those checks in case gcc > 4.1, but I think a cleaner approach would be to either export the gcc version in FindKDE4Internal.cmake or try to make the tests compile on gcc 4.1 -- I'll mail the kde-buildsystem mailing list about the former, and we can hope Steve can help on the latter. I have no idea why it doesn't build with that compiler. Are the EXPORT macros in front of the enums the problem? What happens if you remove them? Please retry with a KF6 version, thanks! |