From owner-freebsd-hackers  Mon May 15 23:27:14 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id XAA00601
          for hackers-outgoing; Mon, 15 May 1995 23:27:14 -0700
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA00595
          for <hackers@freebsd.org>; Mon, 15 May 1995 23:27:10 -0700
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id QAA24054; Tue, 16 May 1995 16:23:12 +1000
Date: Tue, 16 May 1995 16:23:12 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199505160623.QAA24054@godzilla.zeta.org.au>
To: peter@haywire.dialix.com, rgrimes@gndrsh.aac.dev.com
Subject: Re: Some makefile patches to stop the !#^%!& include files being touched
Cc: hackers@FreeBSD.org
Sender: hackers-owner@FreeBSD.org
Precedence: bulk

>Seriously though..  I suspect that a "cmp -s" will fail for many 
							     ^^^^all
>static libs, merely because of the "ranlib" or "ranlib -t" after the 
>install.. even though they are otherwise identical.

This can be avoided by setting RANTOUCH to `${ECHO} foo' in
/etc/make.conf.  Then you would probably have to install the
libraries without changing their timestamp to avoid getting
warnings about the symbol table being out of date.  There are
some hacked versions of `install' around that will do this.
I use one and never noticed the missing `cmp -s'.

Libraries often change anyway because the dates of files in
them change.  This shouldn't cause a relink, but it does because
most programs depend on the static libraries although they are
linked against the shared libraries.  Linking is fast, but after
relinking you have to reinstall in case something really changed.
Loop.

Bruce