FYI, autoconf 2.5x contains a cache system which aims at
    giving back some of the speed the heavy macro usage took
    away.  The cache system does not properly maintain
    dependencies (e.g. it apparently does not track sinclude()
    usage) and thus autoconf 2.5x will sometimes use stale data.
    We work around that by flushing all autoconf-created data
    before invoking autoconf.

    - Sascha


-- 
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to