Actually, I'm a little guilty, though I often ask others when
troubleshooting. I usually just run "make clean". If I see a change
in configure or a makefile, then I'll run "make distclean".
Occassionally I'll make distclean anyways, to be safe.
I don't know how valid my method is - assuming that only configure
and makefile changes require a distclean. But something in the build
instructions would probably be good.
On Aug 24, 2007, at 10:19 AM, Gerald Nelson wrote:
There have been lots of emails recently about compiling issues, and
one common thread is a question about whether you ran 'make
distclean' first.
Is there any reason NOT to always run make distclean? Should it be
part of the standard directions?
-----
William Kyngesburye <kyngchaos*at*kyngchaos*dot*com>
http://www.kyngchaos.com/
"Those people who most want to rule people are, ipso-facto, those
least suited to do it."
- A rule of the universe, from the HitchHiker's Guide to the Galaxy
_______________________________________________
grass-dev mailing list
[email protected]
http://grass.itc.it/mailman/listinfo/grass-dev
