Subject: Re: m4 port: return program name as 'm4' not '/some/path/m4.exe'
	[PATCH]
From: Tim Van Holder <tim DOT van DOT holder AT pandora DOT be>
To: djgpp-workers AT delorie DOT com
In-Reply-To: <3E1DB6DD.2016D6A4@phekda.freeserve.co.uk>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1030109192933 DOT 26716A-100000 AT is>
	 <3E1DB6B1 DOT 9168FDB1 AT phekda DOT freeserve DOT co DOT uk>
	 <3E1DB6DD DOT 2016D6A4 AT phekda DOT freeserve DOT co DOT uk>
Content-Type: text/plain
Organization: 
Message-Id: <1042196143.14887.41.camel@leeloo>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.1 
Date: 10 Jan 2003 11:55:43 +0100
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

On Thu, 2003-01-09 at 18:52, Richard Dawe wrote:
> Hello.
> 
> Richard Dawe wrote:
> > 
> > Hello.
> > 
> > Eli Zaretskii wrote:
> > >
> > > On Thu, 9 Jan 2003, Richard Dawe wrote:
> > >
> > > > But can you rely on that being set? For configure: config.site for
> > > > autoconf 2.13 port and earlier: yes; config.site for autoconf 2.50 and
> > > > later: no.
> > >
> > > The config.site files in the ported packages should set this variable.
> > 
> > They don't at the moment.
> 
> Sorry. Hit send too fast. config.site from 2.50 and later doesn't.

It shouldn't set it in the 2.50 section (as that has proper support),
but IIRC there is a compatibility section that gets used for older
configures; it could be added there (though that would only matter for
Unix-born configures; our old 2.13 port used test -x anyway I believe).

I strongly disagree with TEST_FINDS_EXE in general though; I do NOT want
test -f to return true for ANY reason if the file does not actually
exist.  Using it as a workaround for getting old, unix-born configure
scripts to run (better) on DJGPP is about the limit of its usefulness
IMHO.

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