➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author loewis
Recipients christian.heimes, collinwinter, gregory.p.smith, jyasskin, loewis, mark.dickinson, pitrou, schuppenies, vstinner
Date 2009-02-18.21:33:19
SpamBayes Score 2.5025422e-06
Marked as misclassified No
Message-id <499C7E9D.7080905@v.loewis.de>
In-reply-to <1234991766.01.0.0743405110978.issue4258@psf.upfronthosting.co.za>
Content 
> Maybe configure didn't get updated properly?  I'm almost sure I found a 
> case where autoconf and autoheader just reused the stuff in the 
> autom4te.cache directory even though configure.in had been changed.
> I've been doing:  rm -fr autom4te.cache; autoconf; autoheader
> each time.

I think the docs say to run autoheader first, then autoconf.
History
Date User Action Args
2009-02-18 21:33:21loewissetrecipients: + loewis, collinwinter, gregory.p.smith, mark.dickinson, pitrou, vstinner, christian.heimes, jyasskin, schuppenies
2009-02-18 21:33:19loewislinkissue4258 messages
2009-02-18 21:33:19loewiscreate