From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10301152031.AA13392@clio.rice.edu>
Subject: Re: [Fwd: stdarg.h problem(s)?]
To: djgpp-workers AT delorie DOT com
Date: Wed, 15 Jan 2003 14:31:05 -0600 (CST)
In-Reply-To: <3E25A793.3E5DE36A@phekda.freeserve.co.uk> from "Richard Dawe" at Jan 15, 2003 06:25:23 PM
X-Mailer: ELM [version 2.5 PL2]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> > I'm thinking about something like a checkversions tool may be needed.
> 
> That could be useful for the less-knowledgeable users. What would it check
> other than the libc version?

It would check the libc version used in each image in your djgpp directory
(maybe path) - and also in libc itself.  It might check .mft or .dsm files
for most recent version of each;  if the binaries had a fingerprint (build
date) it could check them also.

It would run from a version file which could ideally be manually updated 
or automatically wget'ed from a site if networking was installed.

I was also thinking it could do a quick diagnosis on your environment,
checking for DJGPP environment variable and in the path, etc and warn
if everything is not right (it would want to pull those values anyway
to find where to look).