On 3/23/2011 11:22 AM, Ben Pfaff wrote:
Does it occur with Autoconf 2.67?
OK. Please report your results.
Curl daily tarball is reporting that configure is built by Autoconf 2.67.
Examination of that section of that generated configure file shows that
it is identical to the code generated by Autoconf 2.63.
I do not have any access to OpenVMS. And you say that you do not
have time to debug it. So we will probably have to just leave
this bug open and unresolved, unless some helpful person comes
along with a fix.
Currently I am using a quick patch script to get the curl configure
script to work. The patch is dependent on the generated configure
script not changing much, so it eventually will have to be replaced.
It would be useful if there was an easy fix for autoconf that if as_echo
was already assigned a value before Configure was started, that it would
just use that value instead of doing the tests for alternatives.
That way when OpenVMS gets support for "print -r or printf" as bash
builtins, it looks like everything may start working with out additional
hacks.
For the short term, OpenVMS is stuck at bash 1.14.8 and other tools of
that age.
It's hard for me to feel motivated about support for OpenVMS in
any case.
I seem to be one of the few OpenVMS programmers that are even trying to
run the configure scripts when porting OpenSource projects.
There is a VMS system for free / open access at Encompasserve.org that
has the older GNU tool chain set up on it. I am quite sure that
autoconf will not even begin to run on it at this time though.
Regards,
-John
wb8...@qsl.net
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
