[GRASS-dev] [GRASS GIS] #1727: v.in.lines not work on Window 7 64 bit

GRASS GIS trac at osgeo.org
Thu Apr 18 04:08:12 PDT 2013


#1727: v.in.lines not work on Window 7 64 bit
------------------------------------+---------------------------------------
 Reporter:  antonioall              |       Owner:  grass-dev@…              
     Type:  defect                  |      Status:  new                      
 Priority:  critical                |   Milestone:  6.4.3                    
Component:  Vector                  |     Version:  svn-trunk                
 Keywords:  v.in.lines, g.tempfile  |    Platform:  MSWindows 7              
      Cpu:  x86-64                  |  
------------------------------------+---------------------------------------
Changes (by hamish):

  * keywords:  v.in.lines => v.in.lines, g.tempfile
  * priority:  normal => critical


Comment:

 ok, I can reproduce the error on XP 32bit with the latest nightly 6.5
 wingrass build, if I run it from the wxGUI File->Import vector data menu.

 you wrote:
 {{{
 C:/GRASS GIS 6.4.3svn/scripts/v.in.lines: line 108:
 /otherMyPath/PERMANENT/.tmp/4520.0: No such file or
 directory
 head: cannot open `/otherMyPath/PERMANENT/.tmp/4520.0' for reading: No
 such file or directory
 }}}

 the problem seems to be with g.tempfile, it's leaving the C: off the temp
 file name.
 It creates the tempfile ok, but I think in the script it needs to start
 with "/c/" ?
 .. right, changing v.in.lines to:
  TEMPFILE=/c"`g.tempfile pid=$$`"

 allows v.in.lines process the temp file. (but then v.in.mapgen chokes on
 its tempfile).

 `g.tempfile pid=123` run from the wxGUI Command Console shows the same
 behaviour: the tempfile name in the output canvas is "/Documents and
 Settings/Username/My Documents/GIS DataBase/spearfish60/user1/.tmp/123.0",
 without /c or C: to start it.
 (also not very good if you data is on D: but grass is installed to
 C:\Program Files)


 Hamish

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/1727#comment:7>
GRASS GIS <http://grass.osgeo.org>



More information about the grass-dev mailing list