> AC_PATH_PROG should now use the pattern '?:[/\\]' in the generated
Err, make that:
?:[/\\]*
> It make sense to me. What are the conditions to see a \ instead of a
> /?
DOS and Windows, once you get past command.com, accept both
slashes and backslashes. So filenames like 'c:/djgpp/gnu/autoconf-2.13'
are just as valid as 'c:\djgpp\gnu\autoconf-2.13'. Which is why
AC_PATH_PROG should n
> "Earnie" == Earnie Boyd <[EMAIL PROTECTED]> writes:
Earnie> I have a local patch for this. I create a variable named
Earnie> path_separator, set a default of ":" and set
Earnie> IFS=${path_separator}. Then use the --path-separator switch
Earnie> to control it's value.
I'm interested in s
> "Mark" == Mark E <[EMAIL PROTECTED]> writes:
Mark> After looking at what Autoconf actually generates, instead of
Mark> the raw source which is a challenge to understand, perhaps
Mark> you're right and the absolute case should be '/* | ?:[/\\]*'. In
Mark> the generated configure script, I se
--- "Mark E." <[EMAIL PROTECTED]> wrote:
> > There is one effect I don't understand well in fact: that of
> > AC_PATH_PROG. You now let Autoconf accept PERL=a:relative/to/perl
> > where before it required PERL=a:/absolute/to/perl. Why is it so?
>
> One reason is to avoid the second case in AC_P
>> There is one effect I don't understand well in fact: that of
>> AC_PATH_PROG. You now let Autoconf accept PERL=a:relative/to/perl
>> where before it required PERL=a:/absolute/to/perl. Why is it so?
>
> Hm, I miss a point here: I don't quite understand how it relates with
> AC_PATH_PROG since
> "Mark" == Mark E <[EMAIL PROTECTED]> writes:
>> There is one effect I don't understand well in fact: that of
>> AC_PATH_PROG. You now let Autoconf accept PERL=a:relative/to/perl
>> where before it required PERL=a:/absolute/to/perl. Why is it so?
Mark> One reason is to avoid the second ca
> There is one effect I don't understand well in fact: that of
> AC_PATH_PROG. You now let Autoconf accept PERL=a:relative/to/perl
> where before it required PERL=a:/absolute/to/perl. Why is it so?
One reason is to avoid the second case in AC_PATH_PROG which
searches the path by setting IFS=":
