On Sat, 21 Jan 2012, Glynn Clements wrote:
It's impossible to say without more information (e.g. exact errors
messages).
Hi, Glynn!
A screenshot is attached. Please let me know if I can provide more
information.
Thanks,
Richattachment:
Dear Helmut,
I don't see (see below) any Module.make after successgulyy install the
grass from elgis repo.
With regards,
Hrach
[root@wn1 grass-6.4.1]# pwd
/usr/lib64/grass-6.4.1
[root@wn1 grass-6.4.1]# ls
AUTHORS CHANGES COPYING fonts scripts
bin
Dear Helmut,
I don't see (see below) any Module.make after successful install the
grass from elgis repo.
With regards,
Hrach
[root@wn1 grass-6.4.1]# pwd
/usr/lib64/grass-6.4.1
[root@wn1 grass-6.4.1]# ls
AUTHORS CHANGES COPYING fonts scripts
bin
Hi,
2012/1/21 Hrachya Astsatryan hr...@sci.am:
I have installed successfully the Grass via elgis.repo (see below)
[root@wn1 grass-6.4.1]# yum list|grep grass|more
grass.x86_64 6.4.1-2.el5.elgis
installed
grass-devel.x86_64 6.4.1-2.el5.elgis
Hi,
Juts now I installed CVN binary in the
/usr/local/grass6.5.svn-x86_64-unknown-linux-gnu-21_01_2012, but when I
compile i get the follwoing error
gcc -L/usr/local/grass6.5.svn-x86_64-unknown-linux-gnu-21_01_2012/lib
On Sat, Jan 21, 2012 at 5:44 AM, Shane Litherland
litherland-f...@bigpond.com wrote:
Hi Markus and mailing list;
I tackled the svn setup today. after several hrs of web browsing,
uninstalling old versions, and trying a few approaches to svn commands,
I think I have succeeded. the 'info' under
Rich Shepard wrote:
Of course! I should mention that GRASS 6.5svn successfully built on this
laptop before. I ran 'svn up', configured, and tried to make it.
There should have been a make clean step in there somewhere.
Whenever you update the source code or re-run cnofigure, you should
On Sun, 22 Jan 2012, Glynn Clements wrote:
There should have been a make clean step in there somewhere. Whenever
you update the source code or re-run cnofigure, you should always run
make clean.
Yep. And that's what I forgot to do just after the previous build. Sigh.
I'll try to not make
Hi GRASSers,
I've just clarified something for myself, that I've only occasionally
noticed before because most of my work is with small vector files.
Starting to play with the North Carolina dataset highlighted this issue
for me again, as it has some 'larger' files in there (not that I'd
consider
