Yeah, but no directions on when to do each. A conservative approach would be to do make distclean just to be sure. But would that ever cause problems?
Jerry ---- Original message ---- >Date: Fri, 24 Aug 2007 12:27:26 -0400 >From: "Patton, Eric" <[EMAIL PROTECTED]> >Subject: RE: [GRASS-dev] compile directions >To: "William Kyngesburye" <[EMAIL PROTECTED]>, "Gerald Nelson" <[EMAIL >PROTECTED]> >Cc: <[email protected]> > >There are instructions in the INSTALL file distributed with Grass on the >difference between the two: > >make clean - delete all files created by 'make' >make distclean - 'make clean' + delete all files created by './configure' > >~ Eric. > >-----Original Message----- >From: [EMAIL PROTECTED] on behalf of William Kyngesburye >Sent: Fri 8/24/2007 1:17 PM >To: Gerald Nelson >Cc: [email protected] >Subject: Re: [GRASS-dev] compile directions > >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/ > Gerald Nelson Professor, Dept. of Agricultural and Consumer Economics University of Illinois, Urbana-Champaign office: 217-333-6465 cell: 217-390-7888 315 Mumford Hall 1301 W. Gregory Urbana, IL 61801 _______________________________________________ grass-dev mailing list [email protected] http://grass.itc.it/mailman/listinfo/grass-dev
