Not a great week for getting the cvs build to work on my linux machine.
This time it seems to be with r.le:
You have to run:
make mixclean
make mix
(better explained in INSTALL file).
because of directory changes today in 5.7 (which brings r.le to you).
At time you have two files in the same directory, which are
separated now into two directories in CVS to allow for compilation.
Markus Neteler
On Feb 10, 2004, at 12:03 PM, Markus Neteler wrote:
Not a great week for getting the cvs build to work on my linux machine.
This time it seems to be with r.le:You have to run:
make mixclean
make mix(better explained in INSTALL file).
This is certainly not the problem. I have successfully updated and built grass57 from cvs dozens of times, according to the INSTALL file. Something else is wrong here.
C.
--
Christopher J. Fonnesbeck ( c h r i s @ f o n n e s b e c k . o r g )
Georgia Cooperative Fish & Wildlife Research Unit, University of Georgia
On Tue, Feb 10, 2004 at 12:50:55PM -0500, Christopher Fonnesbeck wrote:
On Feb 10, 2004, at 12:03 PM, Markus Neteler wrote:
>>Not a great week for getting the cvs build to work on my linux
>>machine.
>>This time it seems to be with r.le:
>
>You have to run:
>
>make mixclean
>make mix
>
>(better explained in INSTALL file).
>This is certainly not the problem. I have successfully updated and
built grass57 from cvs dozens of times, according to the INSTALL file.
Something else is wrong here.
This *is* certainly the problem. This is the first time since month
that such a "heavy" chance was submitted. You have a file in that directory
linked from 5.3, which should be there any more.
There is no other way as following these rules:
cd /where/your/grass530/lives/
cvs update -dP
cd /where/your/grass57/lives/
make mixclean
#here verify, that grass57/raster/r.le/r.le.setup/polytocell/ does
# not contain any links to 5.3 (the file bmf_to_cll.c should not be there
# any more which is causing the problem on your computer).
cvs update -dP
make mix
configure ...
make
Then it should compile. If not, post the contents (ls) of above
directory.
M.
--
Markus Neteler <neteler itc it> http://mpa.itc.it
ITC-irst - Centro per la Ricerca Scientifica e Tecnologica
MPBA - Predictive Models for Biol. & Environ. Data Analysis
Via Sommarive, 18 - 38050 Povo (Trento), Italy
cvs update -dP
Helpful cvs hint of the day:
make a file called ~/.cvsrc and in it place:
-z3
diff -u
update -dP
then whenever you run cvs, it automatically gets the correct switches.
Hamish
Markus Neteler wrote:
> >>Not a great week for getting the cvs build to work on my linux
> >>machine.
> >>This time it seems to be with r.le:
> >
> >You have to run:
> >
> >make mixclean
> >make mix
> >
> >(better explained in INSTALL file).
> >
>
> This is certainly not the problem. I have successfully updated and
> built grass57 from cvs dozens of times, according to the INSTALL file.
> Something else is wrong here.This *is* certainly the problem. This is the first time since month
that such a "heavy" chance was submitted. You have a file in that directory
linked from 5.3, which should be there any more.There is no other way as following these rules:
cd /where/your/grass530/lives/
cvs update -dPcd /where/your/grass57/lives/
make mixclean
#here verify, that grass57/raster/r.le/r.le.setup/polytocell/ does
# not contain any links to 5.3 (the file bmf_to_cll.c should not be there
# any more which is causing the problem on your computer).
AFAICT, "make copymix" will fall down in this situation; perhaps that
option should be removed?
Also, this is one of the reasons why using tricks like:
OBJS = $(subst .c,.o,$(wildcard *.c))
is generally considered to be a bad idea.
--
Glynn Clements <glynn.clements@virgin.net>
On Wed, Feb 11, 2004 at 04:11:36AM +0000, Glynn Clements wrote:
Markus Neteler wrote:
> > >>Not a great week for getting the cvs build to work on my linux
> > >>machine.
> > >>This time it seems to be with r.le:
> > >
> > >You have to run:
> > >
> > >make mixclean
> > >make mix
> > >
> > >(better explained in INSTALL file).
> > >
> >
> > This is certainly not the problem. I have successfully updated and
> > built grass57 from cvs dozens of times, according to the INSTALL file.
> > Something else is wrong here.
>
> This *is* certainly the problem. This is the first time since month
> that such a "heavy" chance was submitted. You have a file in that directory
> linked from 5.3, which should be there any more.
>
> There is no other way as following these rules:
>
> cd /where/your/grass530/lives/
> cvs update -dP
>
> cd /where/your/grass57/lives/
> make mixclean
> #here verify, that grass57/raster/r.le/r.le.setup/polytocell/ does
> # not contain any links to 5.3 (the file bmf_to_cll.c should not be there
> # any more which is causing the problem on your computer).AFAICT, "make copymix" will fall down in this situation; perhaps that
option should be removed?Also, this is one of the reasons why using tricks like:
OBJS = $(subst .c,.o,$(wildcard *.c))
is generally considered to be a bad idea.
GRASS 5.7 is always open for new developers to improve it.
Markus Neteler
> > >>Not a great week for getting the cvs build to work on my linux
> > >>machine.
BTW, it is not required to compile GRASS 5.7/Linux yourself.
Every saturday (exceptionally also yesterday) a precompiled
GRASS 5.7/Linux binary package is offered here:
http://grass.itc.it/grass51/binary/linux/
(on the mirror sites as well)
So you may simply want to download and install.
Markus Neteler