Created attachment 53779 [details] [review]
patch against configure.in

Changing the order of $LFFLAGS fixes this.

Can reproduce the problem on machines w/o pilot-link-devel packages. What is the
pilot-link-devel version on your system, if it is installed? Installing the
package lets configure to go through successfully.

I do not see how swapping the order of LD_FLAGS fixes the problem - perhaps we
should probe deeper for the actual issue.

Going to dig deeper into this soon. Sorry for the delay.

*** Bug 305660 has been marked as a duplicate of this bug. ***

guenther: ping?

pong.  Still on my ever growing todo list... :/

guenther: ping, again. or shall i close this as incomplete, dude? ;-)

Reassigning to me...

please take care of this bug, it's a really small fix, and I made a duplicate because there is so many open bugs about evolution that it is hard to find. (bug #396536)

*** Bug 396536 has been marked as a duplicate of this bug. ***

Reopening as bug 396536 has an identical patch and this should be the proper way to fix this.
Reordering libraries in the link command fixes this because the ordering of arguments (object file listing, static libraries and shared libraries) matters to the linker, despite popular misconception that it doesn't.
See the section "Importance of linking order" in the following documentation for example: http://www.gentoo.org/proj/en/qa/asneeded.xml

This patch has been applied to all 2.8.x and 2.9.x versions in Gentoo, and is working great.

Thanks, guys, for the additional comments and info. :)

Committed to trunk and gnome-2-18 branch.