From:	Alain Magloire <alainm AT rcsm DOT ece DOT mcgill DOT ca>
Message-Id:	<199905240106.VAA23378@mccoy2.ECE.McGill.CA>
Subject:	Re: Bash 2.03 final beta available
To:	djgpp-workers AT delorie DOT com
Date:	Sun, 23 May 1999 21:06:58 -0400 (EDT)
In-Reply-To:	<Pine.SUN.3.91.990523122045.26578D-100000@is> from "Eli Zaretskii" at May 23, 99 12:21:06 pm
X-Mailer:	ELM [version 2.4 PL25]
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> 
> > 2. ./configure seems to be wanting to use "getconf". Do you see this
> >    too? What is "getconf"?
> 
> It's a Linux tool that return system-configuration details.  To get it
> to work with DJGPP, create a script like this:

Not exactly, it's a well defined POSIX.1 program.  And many if not more
GNU packages use it to get information from the OS.  For example GNU grep
use it to guess if the underlying OS supports LARGEFILE,  at one point
I was discussing with (Jim) Meyering to add getconf in one of fetish package,
maybe sh-utils.  But we kind of back down form the idea since  getconf
was flirting to much with the OS and being to specific to a particular
OS. But I did code a very quick, proof of concept getconf, it uses
confstr() to get the limits and system-coonfiguration details
ftp://mccoy.ee.mcgill.ca/pub/alain/misc/getconf.tar.gz

> #!/bin/sh
> exit 0

Remind me after 2.03 to clean up for DJGPP.  It's not something hard
to do but only very tedious.

-- 
au revoir, alain
----
Aussi haut que l'on soit assis, on est toujours assis que sur son cul !!!

- Raw text -