On Mon, 29 Jul 2002, Mythran wrote: > Why? I know I should always edit Makefile.in then run configure. A slight correction. You should run config.status if nothing has changed since the last time you ran configure. It just remakes Makefile (unless you've changed conf.h.in, in which case it'd also remake conf.h) so it's faster and less spammy than running configure. > ..but once again, why? Alex answered why for you; I won't repeat that. Instead, I'll ask: given you know the reasons why, why not? -dak -- +---------------------------------------------------------------+ | FAQ: http://qsilver.queensu.ca/~fletchra/Circle/list-faq.html | | Archives: http://post.queensu.ca/listserv/wwwarch/circle.html | | Newbie List: http://groups.yahoo.com/group/circle-newbies/ | +---------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 06/25/03 PDT