#1622: Grass 7 error
----------------------------+-----------------------------------------------
Reporter: renatotonielli | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.0.0
Component: Display | Version: svn-trunk
Keywords: | Platform: MSWindows XP
Cpu: x86-64 |
----------------------------+-----------------------------------------------
I installed the new version of Grass 7, but after installation I received
this error.
'manpath' is not recognized as an internal or external command, operable
program or batch file.
Cleaning up temporary files...
Starting GRASS GIS...
ATTENZIONE: Il locking concorrente del mapset non Φ supportato in Windows.
Welcome to GRASS 7.0.svn
GRASS homepage: http://grass.osgeo.org
This version running through: shell
(C:\WINDOWS\system32\cmd.exe)
Help is available with the command: g.manual -i
See the licence terms with: g.version -c
If required, restart the GUI with: g.gui wxpython
When ready to quit enter: exit
Launching <wxpython> GUI in the background, please wait...
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.
E:\Program Files (x86)\GRASS GIS 7.0.svn\msys>3D view mode:
grass_imagery.7.0.svn not found.
'g.list' is not recognized as an internal or external command, operable
program or batch file.
'g.list' is not recognized as an internal or external command, operable
program or batch file.
GRASS module 'g.region' not found. Unable to start map display window.
GRASS module 'g.region' not found. Unable to start map display window.
It looks as though 7.0.svn Windows binaries have been broken since 10 March.
From the logs, WinGRASS-7.0.svn-r51025-179-Setup.exe should have g.region.exe
and many other modules which are missing from subsequent builds. I don't think
that this is a bug in GRASS, but rather in the Windows binary builds. Could
those caring for Windows builds please make
WinGRASS-7.0.svn-r51025-179-Setup.exe available as a stop-gap, and resolve the
problem when possible?
Until this is resolved, please restore the last build that wasn't broken,
r51025-179 of 10 March, which cannot now be downloaded. All the visible
daily builds are broken - the platform is Windows XP thru 7, and
presumably not just x64.
Replying to [comment:4 rsbivand]:
> Until this is resolved, please restore the last build that wasn't
broken, r51025-179 of 10 March, which cannot now be downloaded. All the
visible daily builds are broken - the platform is Windows XP thru 7, and
presumably not just x64.
I fixed it in r51112, the bug was introduced with direct pg support. This
is the second time that Vlib was broken because of the new pg support. I
would very much like to have this new feature tested (more than successful
compilation) by the developer implementing it before it becomes enabled by
default.
Replying to [comment:5 mmetz]:
> Replying to [comment:4 rsbivand]:
> > Until this is resolved, please restore the last build that wasn't
broken, r51025-179 of 10 March, which cannot now be downloaded. All the
visible daily builds are broken - the platform is Windows XP thru 7, and
presumably not just x64.
>
> I fixed it in r51112, the bug was introduced with direct pg support.
This is the second time that Vlib was broken because of the new pg
support. I would very much like to have this new feature tested (more than
successful compilation) by the developer implementing it before it becomes
enabled by default.