GNOME Bugzilla – Bug 679983
Does not build with latest e-d-s
Last modified: 2012-07-16 09:07:50 UTC
When building evo-exchange with latest e-d-s 3.5.4, it fails with: In file included from e2k-freebusy.c:35:0: /usr/include/evolution-data-server-3.6/libedataserver/e-time-utils.h:12:2: error: #error "Only <libedataserver/libedataserver.h> should be included directly." make[4]: *** [libexchange_la-e2k-freebusy.lo] Error 1 make[4]: *** Waiting for unfinished jobs.... In file included from e2k-context.c:51:0: /usr/include/evolution-data-server-3.6/libedataserver/e-proxy.h:25:2: error: #error "Only <libedataserver/libedataserver.h> should be included directly." In file included from e2k-http-utils.c:26:0: /usr/include/evolution-data-server-3.6/libedataserver/e-time-utils.h:12:2: error: #error "Only <libedataserver/libedataserver.h> should be included directly." make[4]: *** [libexchange_la-e2k-context.lo] Error 1 make[4]: *** [libexchange_la-e2k-http-utils.lo] Error 1 In file included from e2k-utils.c:29:0: /usr/include/evolution-data-server-3.6/libedataserver/e-time-utils.h:12:2: error: #error "Only <libedataserver/libedataserver.h> should be included directly." make[4]: *** [libexchange_la-e2k-utils.lo] Error 1 In file included from e2k-autoconfig.c:66:0: /usr/include/evolution-data-server-3.6/libedataserver/e-data-server-util.h:23:2: error: #error "Only <libedataserver/libedataserver.h> should be included directly." In file included from e2k-autoconfig.c:67:0: /usr/include/evolution-data-server-3.6/libedataserver/e-url.h:29:2: error: #error "Only <libedataserver/libedataserver.h> should be included directly." In file included from e2k-autoconfig.c:68:0: /usr/include/evolution-data-server-3.6/libedataserverui/e-passwords.h:24:2: error: #error "Only <libedataserverui/libedataserverui.h> should be included directly." make[4]: *** [libexchange_la-e2k-autoconfig.lo] Error 1
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 679446 ***