From: Dan N. <dbn...@gm...> - 2010-03-26 13:49:10
|
On Wed, Mar 24, 2010 at 07:00:06AM -0700, STEVE555 wrote: > > Dear Jakob, > I did a ./autogen.sh and Mesa builds fine now,sorry about > that.I do run ./autogen.sh from time to time,I just thought ./configure > would be enough,oh well,I like to thank you for your help. When someone makes a commit to configure.ac, the configure file has to be regenerated. Usually automake adds rules so that if configure.ac is newer than configure, it runs autoconf again. We can try to add some rules like that to the toplevel Makefile, but I'd like to take a look at the way automake does it before adding some half baked hack. However, the takeaway is that if you're seeing build errors, you'll want to check that configure is up to date and that it's been run again. Here's a handy trick for regenerating the autotools and keeping your configure arguments: $ autoreconf -iv && ./config.status --recheck && ./config.status That's pretty much a surefire way to ensure the autotools (whichever ones) are refreshed, and the second part runs configure again with your arguments you used before. -- Dan |