[GRASS5] Re: [GRASSLIST:1116] compiling postgres modules

Hi Moritz,

On Tue, Nov 14, 2000 at 10:33:24AM +0100, mlennert@club.worldonline.be wrote:
> I have the feeling there is a problem with my cvs. I've update through cvs
> update -dP, but the Makefile and the configure file had not been updated. What
> am I doing wrong ?

The Makefile won't be updated as it is generated from Makefile.in.
The configure might not be updated, if it is already up-to-date.

Sorry, I wasn't clear enough: I wanted to say Makefile.in.
And no, neither one of the two had been updated yesterday when I did a 'cvs
update -dP' in my grass cvs directory. Now I can't check anymore, since I've
erased everything and redownloaded it via 'cvs -z3 co grass' (I did need grass
for work...). Now the files are the correct ones. I guess we'll just have to
wait until the next updates to check wether the problem reoccurs.

So, look for the Makefile.in timestamp.

Hope this helps

Markus

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'

On Tue, Nov 14, 2000 at 02:24:23PM +0100, mlennert@club.worldonline.be wrote:

> Hi Moritz,
>
> On Tue, Nov 14, 2000 at 10:33:24AM +0100, mlennert@club.worldonline.be wrote:
> > I have the feeling there is a problem with my cvs. I've update through cvs
> > update -dP, but the Makefile and the configure file had not been updated. What
> > am I doing wrong ?
>
> The Makefile won't be updated as it is generated from Makefile.in.
> The configure might not be updated, if it is already up-to-date.

Sorry, I wasn't clear enough: I wanted to say Makefile.in.
And no, neither one of the two had been updated yesterday when I did a 'cvs
update -dP' in my grass cvs directory. Now I can't check anymore, since I've
erased everything and redownloaded it via 'cvs -z3 co grass' (I did need grass
for work...). Now the files are the correct ones. I guess we'll just have to
wait until the next updates to check wether the problem reoccurs.

If you are interested, you can track the ongoing CVS updated "realtime":
http://www.geog.uni-hannover.de/grass/grasscvscommit.html

:slight_smile:

Cheers

Markus

----------------------------------------
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo@geog.uni-hannover.de with
subject 'unsubscribe grass5'