> Tim> Yes, but some platforms (like DJGPP) are not yet 100% supported
> Tim> directly - we need config.site to make path seraching work.
>
> :(
>
> I don't remember what remains to be done for DJGPP.
Not a lot really. There's probably a few places (AS_DIRNAME comes to
mind) where support for
> "Tim" == Tim Van Holder <[EMAIL PROTECTED]> writes:
>> Err, you're gonna laugh Pavel, but I don't know how to do this...
>>
>> If there is a config.site, then it's loaded *after* the option
>> processing (because it depends on $prefix). Therefore setting
>> --cache-file is not an option.
Hello, Akim!
> | I use a single cache file for all packages I configure (by setting
> | cache_file). When doing the tests ("make check" IIRC) for autoconf 2.50, it
> | seems to pollute this cache file. Specifically, it seems to be happening
> | around compile.at:154, where it sets CPP to "./myc
| In addition to the problem outlined in the message below, it seems the
| address [EMAIL PROTECTED] listed in the README is erroneous :)
Fixed, thanks!
| I am having problems installing the newly released autoconf 2.50.
|
| I use a single cache file for all packages I configure (by setting
|
