Jean-Marc Lasgouttes <[EMAIL PROTECTED]> wrote:
> BTW, concerning OS/2, are there interesting things for OS/2 in
> autoconf 2.13? There is support for executable files suffixes (.exe)
> and such, but I do not know how to use it. It would be useful for
> windows, too.
>
> And what's the status of autoconf for OS/2? It seems that it is not in
> 2.13. What are the plans?
Short history:
1. Juan Jose Garcia Ripoll <[EMAIL PROTECTED]> wrote the
initial version of autoconf for OS/2 with support for
- executable and other files suffixes (.exe ...),
- ';' rather than ':' as the path separator according as
"uname -s" output,
- drive letters in path,
etc. He arranged system specific defaults in a single macro
so that support for other operating systems, such as Win32 and
DOS can be easily added.
2. He submitted his patch to the autoconf maintainers.
3. It is very typical of FSF. They adopted the basic parts and
ideas of JuanJo's patch, but rejected all the OS/2 support
stuffs. They rewrote them for Win32 support things and
released autoconf 2.13
4. Meanwhile JuanJo is assimilated to another operating system
when he upgraded his machine to Pentium II. He withdrew
autoconf and ash port for OS/2.
5. For a while there was no autoconf for OS/2 maintainer. At
last Hung-Chi Chu <[EMAIL PROTECTED]> has agreed to
succeed the maintainance. The patch for 2.13 is there now.
But apparently he has no intention to submit it to FSF.
Though I'm still using 2.12, I will soon upgrade to 2.13 and
try to submit patch for configure.in of LyX 1.1
Since, on UNIX systems, configure generated by autoconf for
OS/2 runs just the same way as the one generated by *official*
autoconf, I appreciate if you are going to use the portable
configure, config.sub, config.guess, mkinstalldirs and install-sh
although they are not the approved version of FSF.
Regards,
SMiyata
