Paul Eggert wrote:
>
> Andreas B ¼ning <andreas.buening@xxxxxxxx> writes:
>
> > - The code that searches for the best shell (_AS_DETECT_BETTER_SHELL,
> > around line 234 in lib/m4sugar/m4sh.m4) doesn't use $ac_executable_extensions,
> > so for systems which use .exe extensions no shell can be found here.
> > Please, correct this. If you like I'll write the necessary one or two lines
> > to patch this.
>
> It might be more than one or two lines, I'm afraid. However, thanks
> for reporting it; I installed the following temporary workaround
> below.
What about the following patch? I think it would do. Btw, I forgot that
$PATH usually contains drive letters.
--------------------------------------
--- m4sh.m4.old Thu Jun 1 19:35:28 2006
+++ m4sh.m4 Thu Jun 8 21:17:26 2006
@@ -230,9 +230,11 @@
[as_candidate_shells=
_AS_PATH_WALK([/usr/bin/posix$PATH_SEPARATOR/bin$PATH_SEPARATOR/usr/bin$PATH_SEPARATOR$PATH],
[case $as_dir in
- /*)
+ /* | [A-Za-z]:/*)
for as_base in sh bash ksh sh5; do
- as_candidate_shells="$as_candidate_shells $as_dir/$as_base"
+ for ac_exec_ext in '' $ac_executable_extensions; do
+ as_candidate_shells="$as_candidate_shells $as_dir/$as_base$ac_exec_ext"
+ done
done;;
esac])
--------------------------------------
> By the way: on your host, does "test -x foo" succeed if foo.exe is
> executable?
No.
Btw, autoconf/automake create files using the system's standard line
break which is \r\n in my case. Would it be possible without too much
effort to produce \n on all systems? That way I wouldn't have to call
recode for configure, Makefile.in and other files to remove \r before
they work on a Unix system. I assume that all systems can handle a
simple \n line break because otherwise 100% of all provided configure
scripts would be useless to them.
This is just a naive user question. I don't mean you have to implement
this now.
Thanks,
Andreas Büning
_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf
