[Evolution-hackers] Excessive relinking with "make install"

[Lee Revell <rlrevell joe-job com>]

Hello,

If I configure, make, then make install Evolution from CVS, the make
install step takes a *long* time, due to lots of this:

/bin/sh ../../mkinstalldirs /usr/local/lib/evolution/2.4/components
 /bin/sh ../../libtool --mode=install /usr/bin/install -c  libevolution-calendar.la /usr/local/lib/evolution/2.4/components/libevolution-calendar.la
libtool: install: warning: relinking `libevolution-calendar.la'
(cd /home/rlrevell/cvs/evolution-new/calendar/gui; /bin/sh ../../libtool
--mode=relink gcc -g -O2 -Wall -Wmissing-prototypes -Wno-sign-compare -o
libevolution-calendar.la -rpath /usr/local/lib/evolution/2.4/components
-avoid-version -module evolution-calendar-common.lo
evolution-calendar-skels.lo evolution-calendar-stubs.lo
Evolution-Composer-common.lo Evolution-Composer-skels.lo
Evolution-Composer-stubs.lo e-calendar-marshal.lo

etc

Sometimes it seems to relink more components than others.  Why do we
need to relink everything, doesn't "make" do this?

This is a problem because I'm cross compiling using my fast machine as a
build host, then I just "make install" from an NFS mount on the slow
(600Mhz) machine.  But "make install" still takes 20 minutes on the slow
machine.  (I have verified that all installed packages are identical on
the two systems, and ruled out NFS as the source of the problem).

Lee