Help:Problem withv.in.dxf/ v.support (cont)
G. Zacharioudakis
GIORGOS at ers.bham.ac.uk
Thu Feb 1 07:00:00 EST 1996
Hello,
Thanks to every body and especially Bill Brown for their
valuable help up to now.
We are gradually getting there...
Bill I followed your advice and the problem with v.support
was solved!
Now v.in.dxf and v.support runs perfectly!!!!
I have to say that our machine is a 64-bit one and during the
compilation I noticed 'internal tests' during which there was the
assumption and acceptance that long=integer=32bit.
However that does not agree with the 64-bit compiler.
Apart from v.support there were problems with v.digit and d.vect.
So we thought that the problems might exist because GRASS operates
with the above assumption.
We tried to locate the error messages that crash v.digit and we ended
up to source/src/mapdev/diglib/portable.h and portable.c.
There we defined that long=64 bit (the length of long=64) and
compiled again.
Suprisingly this released the operation of v.digit, and v.digit seems
to run o.k. (it is true that we need some time to test all the
options).
The easy solution would be to change the appropriate compilation flag
and recompile everything using a 32-bit option.
What is the general opinion of the users?
Carry on debugging the commands that do not work or recompile
everything using the 32-bit option?
Of cource choosing the second it will result lack of the capabilities
of the 64-bit machine......
Any ideas about problem with d.vect? (I get all the messages on the
unix screen but there is no vector plotted on the graphics screen!)
I will tidy up what we've done and let you know in detail.
Once more thanks to every body that helped me and I look forward to
hearing from you
Giorgos
Giorgos Zacharioudakis
School of Earth Sciences
University of Birmingham
Edgbaston B15 2TT
Birmingham
UK
Tel 0044 121 4146146
Fax 0044 121 4143971
e-mail:giorgos at ers.bham.ac.uk
More information about the grass-user
mailing list