After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 710498 - evolution-3.10.1 linking errors on compilation: undefined reference to `e_mail_part_list_is_empty'
evolution-3.10.1 linking errors on compilation: undefined reference to `e_mai...
Status: RESOLVED DUPLICATE of bug 710852
Product: evolution
Classification: Applications
Component: Calendar
3.10.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2013-10-19 09:31 UTC by Chris Vine
Modified: 2014-03-13 17:29 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Chris Vine 2013-10-19 09:31:10 UTC 
evolution-3.10.1 fails to compile with this:

make[4]: Entering directory `/usr/local/src/gnome-3/updates/evolution-3.10.1/calendar/alarm-notify'
  CC       evolution_alarm_notify-alarm.o
  CC       evolution_alarm_notify-alarm-notify.o
  CC       evolution_alarm_notify-alarm-notify-dialog.o
  CC       evolution_alarm_notify-alarm-queue.o
  CC       evolution_alarm_notify-config-data.o
  CC       evolution_alarm_notify-notify-main.o
  CC       evolution_alarm_notify-util.o
  CCLD     evolution-alarm-notify
../../composer/.libs/libevolution-mail-composer.so: undefined reference to `e_mail_part_list_is_empty'
collect2: error: ld returned 1 exit status
make[4]: *** [evolution-alarm-notify] Error 1

This is a compile against evolution-data-server-3.10.1, using gcc-4.8.1

Evolution-3.10.0 compiles cleanly.
Comment 1 Baste 2013-10-23 16:47:13 UTC 
Hi,

Same problem(same error) to compile evolution-3.10.1

Fine with evolution-3.10.0

gcc version : 4.7.2
evolution-data-server version: 3.10.1
Comment 2 Milan Crha 2014-03-13 17:29:12 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 710852 ***