X-Authentication-Warning:	kendall.sfbr.org: jeffw set sender to jeffw AT darwin DOT sfbr DOT org using -f
Date:	Fri, 21 Jun 2002 10:36:14 -0500
From:	JT Williams <jeffw AT darwin DOT sfbr DOT org>
To:	djgpp-workers AT delorie DOT com
Subject:	Re: automake 1.5, bison 1.35 and Fileutils 4.1 - y_tab.c vs. y.tab.c
Message-ID:	<20020621153614.GB12418@kendall.sfbr.org>
Mail-Followup-To:	djgpp-workers AT delorie DOT com
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>
Mime-Version:	1.0
In-Reply-To:	<Pine.SUN.3.91.1020618083543.16082F-100000@is>
User-Agent:	Mutt/1.3.27i
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

-: From my experience, it is better to test if y.tab.c exists, and if so,
-: "mv y.tab.c y_tab.c".

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

- Raw text -