--* Received: from mailer.scri.fsu.edu by nags2.nag.co.uk (4.1/UK-2.1)
--* 	id AA01945; Tue, 2 Apr 96 06:24:45 BST
--* Received: from ibm4.scri.fsu.edu (ibm4.scri.fsu.edu [144.174.131.4]) by mailer.scri.fsu.edu (8.6.12/8.6.12) with SMTP id AAA05125; Tue, 2 Apr 1996 00:21:17 -0500
--* From: Tony Kennedy <adk@scri.fsu.edu>
--* Received: by ibm4.scri.fsu.edu (5.67b) id AA27077; Tue, 2 Apr 1996 00:19:22 -0500
--* Date: Tue, 2 Apr 1996 00:19:22 -0500
--* Message-Id: <199604020519.AA27077@ibm4.scri.fsu.edu>
--* To: ax-bugs
--* Subject: RE: AXL_F_LibOutOfDate
--* Cc: adk@mailer.scri.fsu.edu, edwards@mailer.scri.fsu.edu

--@ Fixed  by: <Who> <Date>
--@ Tested by: <Name of new or existing file in test directory>
--@ Summary:   <Description of real problem and the fix>

Sorry, the description of the problem with AXL_F_LibOutOfDate got omitted
from the previous bug report (whose number I do not yet know).

The problem is that the error message should not be fatal if the out of
date library file is not actually used. As it is at present if one library
element gets modified (or accidentally deleted or whatever) nothing will
compile until everything is up-to-date, even if the modified element is
completely irrelevant to what is being compiled. A warning message might
be more appropriate.
