> Not only gross, it wouldn't work on DOS anyway. DOS has a 8.3 filename
> limit. I think these kind of limitations will have to resort to cross
> building to the non-compliant systems. Leave it alone.
Actually, on DJGPP (and I think this is currently the only DOS environment
that is unixy enou
Akim Demaille wrote:
>
> > "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
>
> Alexandre> Not if acversion.m4.in appears after acversion.m4 in the
> Alexandre> tar-file. In this case, it would be overwritten.
>
> Pfff.
>
> >> Nevertheless, you'll see that the test suite uses co
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
Alexandre> Not if acversion.m4.in appears after acversion.m4 in the
Alexandre> tar-file. In this case, it would be overwritten.
Pfff.
>> Nevertheless, you'll see that the test suite uses config.hin to
>> make your life easier.
A
On Jan 18, 2001, Akim Demaille <[EMAIL PROTECTED]> wrote:
> | I'd like to request the following changes in file names for some future
> | version of autoconf:
> |
> | -) use acversion.in, not acversion.m4.in
> |reason: not all systems support multiple dots in filenames
> |
> | A similar pro
| I'd like to request the following changes in file names for some future
| version of autoconf:
|
| -) use acversion.in, not acversion.m4.in
|reason: not all systems support multiple dots in filenames
|
| A similar problem exists in the man directory (the config.guess and
| config.sub man
I'd like to request the following changes in file names for some future
version of autoconf:
-) use acversion.in, not acversion.m4.in
reason: not all systems support multiple dots in filenames
A similar problem exists in the man directory (the config.guess and
config.sub man pages), but that
