Date: Sat, 22 Jun 2002 12:47:06 +0300
From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: djgpp-workers AT delorie DOT com
Message-Id: <9743-Sat22Jun2002124706+0300-eliz@is.elta.co.il>
X-Mailer: emacs 21.3.50 (via feedmail 8 I) and Blat ver 1.8.9
In-reply-to: <20020621153614.GB12418@kendall.sfbr.org> (message from JT
	Williams on Fri, 21 Jun 2002 10:36:14 -0500)
Subject: Re: automake 1.5, bison 1.35 and Fileutils 4.1 - y_tab.c vs. y.tab.c
References: <3D0E45A1 DOT C2941FB7 AT phekda DOT freeserve DOT co DOT uk> <Pine DOT SUN DOT 3 DOT 91 DOT 1020618083543 DOT 16082F-100000 AT is> <20020621153614 DOT GB12418 AT kendall DOT sfbr DOT org>
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

> Date: Fri, 21 Jun 2002 10:36:14 -0500
> From: JT Williams <jeffw AT darwin DOT sfbr DOT org>
> 
> Is there a shell idiom for testing for lfn support (e.g., within
> a Makefile)?  The LFN environment variable from djgpp.env isn't a
> reliable indicator.  Perhaps something like this:
> 
> touch .foo && [ -f .foo ] && echo "LFN capable" && rm -f .foo

Yes, that's the general idea: create a file which can only exist if
LFN is supported, then test for its existence.

You should probably send stdout and stderr to /dev/null, since
"touch .foo" will barf if LFN isn't supported.