Subject:	Re: m4 port: return program name as 'm4' not '/some/path/m4.exe'
From:	Tim Van Holder <tim DOT van DOT holder AT pandora DOT be>
To:	djgpp-workers AT delorie DOT com
In-Reply-To:	<200301092210.h09MA1523166@brother.ludd.luth.se>
References:	<200301092210 DOT h09MA1523166 AT brother DOT ludd DOT luth DOT se>
Organization:
Message-Id:	<1042192954.14890.0.camel@leeloo>
Mime-Version:	1.0
X-Mailer:	Ximian Evolution 1.2.1
Date:	10 Jan 2003 11:02:35 +0100
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

On Thu, 2003-01-09 at 23:10, Martin Str|mberg wrote:
> According to Tim Van Holder:
> > 'test -x'.  Because of that, autoconf was changed to use executable
> > extensions instead; this has (currently) zero overhead and breakage
> > on Unixy systems (as the set of extensions needs to come from
> > environment/config.site at the moment), while also easy to use for a
> > djgpp port (ie adding a variable to our config.site).
> 
> Perhaps I'm missing something, but that would break a script called
> "do_this" (without extension) using the "#!/path/to/executable"
> feature, wouldn't it?

Not really, as '' (the empty string) is considered a valid executable
extension.

-- 
Tim Van Holder <tim DOT van DOT holder AT pandora DOT be>

- Raw text -