GNOME Bugzilla – Bug 629806
Error during phase build of evolution-data-server
Last modified: 2013-09-14 16:53:56 UTC
error when Compiler from git master I get this make[4]: Entering directory `/home/fabio/checkout/gnome/evolution-data-server/calendar/libedata-cal' CC libedata_cal_1_2_la-e-data-cal-enumtypes.lo CC libedata_cal_1_2_la-e-cal-backend.lo CC libedata_cal_1_2_la-e-cal-backend-cache.lo CC libedata_cal_1_2_la-e-cal-backend-factory.lo CC libedata_cal_1_2_la-e-cal-backend-intervaltree.lo CC libedata_cal_1_2_la-e-cal-backend-sexp.lo CC libedata_cal_1_2_la-e-cal-backend-sync.lo CC libedata_cal_1_2_la-e-cal-backend-util.lo CC libedata_cal_1_2_la-e-cal-backend-store.lo CC libedata_cal_1_2_la-e-cal-backend-file-store.lo CC libedata_cal_1_2_la-e-data-cal.lo CC libedata_cal_1_2_la-e-data-cal-view.lo CCLD libedata-cal-1.2.la CC e_calendar_factory-e-data-cal-factory.o CC e_calendar_factory-e-data-cal-migrate.o CC e_calendar_factory-e-cal-backend-loader-factory.o CCLD e-calendar-factory /usr/bin/ld: warning: libproxy.so.0, needed by /home/fabio/gnome//lib/libgdata.so, may conflict with libproxy.so.1 ./.libs/libedata-cal-1.2.so: undefined reference to `e_cal_recur_ensure_end_dates' ./.libs/libedata-cal-1.2.so: undefined reference to `e_cal_recur_obtain_enddate' collect2: ld returned 1 exit status make[4]: *** [e-calendar-factory] Error 1 make[4]: Leaving directory `/home/fabio/checkout/gnome/evolution-data-server/calendar/libedata-cal' make[3]: *** [all] Error 2 make[3]: Leaving directory `/home/fabio/checkout/gnome/evolution-data-server/calendar/libedata-cal' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/fabio/checkout/gnome/evolution-data-server/calendar' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/fabio/checkout/gnome/evolution-data-server' make: *** [all] Error 2 *** Error during phase build of evolution-data-server: ########## Error running make *** [42/65]
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 628238 ***