Sender: rich AT phekda DOT freeserve DOT co DOT uk
Message-ID: <3E1EB069.3BBB1776@phekda.freeserve.co.uk>
Date: Fri, 10 Jan 2003 11:37:13 +0000
From: Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.23 i586)
X-Accept-Language: de,fr
MIME-Version: 1.0
To: djgpp-workers AT delorie DOT com
Subject: Re: m4 port: return program name as 'm4' not '/some/path/m4.exe'[PATCH]
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> <1042196143 DOT 14887 DOT 41 DOT camel AT leeloo>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

Hello.

Tim Van Holder wrote:
[snip]
> 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).

Tim: In the packages I made of autoconf 2.57, I included the config.site you
sent me in your autoconf 2.57 patch set. Below is the 2.13 compatibility
section from that. It sets TEST_FINDS_EXE for 2.13.

...
# This is here for backward compatibility with 2.13 configures; the
conditional
# ensures it's disabled in the DJGPP package of autoconf 2.50 and above.
# FIXME: This conditional may change as autoconf evolves - autoconf should
#        really have some version variables.
if test -z "$as_ln_s"; then

  echo "Warning: This configure script was generated using an old version of
autoconf"
  echo "Warning: Newer versions have much better DJGPP compatibility"

  # In 2.5x, replaced by ac_executable_extensions
  export TEST_FINDS_EXE=y

  # Set automagically by 2.5x
  export PATH_SEPARATOR=:

  # $INSTALL must be an absolute path name, otherwise config.status
  # will try to prepend ./ and ../ to it when it goes into subdirs.
  export INSTALL=${INSTALL='/dev/env/DJDIR/bin/ginstall -c'}

  # Help out libtool
  ac_exeext=".exe"
  export lt_cv_sys_max_cmd_len=12288
  export lt_cv_prog_cc_pic_works=no

  # Force the test for 'ln -s' to report no.
  export LN_S="cp -p"
  ac_cv_prog_LN_S="cp -p"

else # autoconf 2.50 or higher
...
 
> 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.

I agree with that. Too many special cases just add to the number of things
that can go wrong, when you're using DJGPP in general and porting in
particular.

Bye, Rich =]

-- 
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]