Opened 15 years ago

Closed 15 years ago

Last modified 15 years ago

#889 closed defect (fixed)

Msys-based commands fail when winGRASS is installed in %ProgramFiles%

Reported by: Luigi Ponti Owned by: grass-dev@…
Priority: normal Milestone: 6.4.0
Component: Default Version: 6.4.0 RCs
Keywords: wingrass Cc:
CPU: x86-32 Platform: MSWindows Vista

Description

Current standalone winGRASS installer (I used that of 20 Jan 2010 on Windows 7) defaults to %ProgramFiles% and this seems to prevent all sh.exe-based commands to work properly. E.g. d.shadedmap and r.shaded.relief fail with the following error message:

r.shaded.relief map=dem                                                
/c/Program: Files\GRASS-64-SVN\msys\bin\sh.exe: No such file
or directory

This should be related to http://trac.osgeo.org/grass/ticket/714 http://lists.osgeo.org/pipermail/grass-dev/2010-January/048199.html

Also see this post: http://n2.nabble.com/GUI-with-python-scripts-tp4435076p4440590.html

which says that installing 6.4.0-SVN snapshots in %ProgramFiles% won't work until the recent changes to the G_spawn* functions have been back-ported. The current 6.4.0 code is known not to work with spaces in $GISBASE. 6.5 should work (although based upon recent comments, MSys might need to be installed in C:\msys).

Change History (4)

comment:1 by hamish, 15 years ago

Keywords: wingrass added

please use the 'wingrass' keyword for wingrass bugs, thanks. H

comment:2 by hamish, 15 years ago

hi, could you try the latest nightly wingrass build? I think this is now fixed.

Hamish

in reply to:  2 ; comment:3 by Luigi Ponti, 15 years ago

Resolution: fixed
Status: newclosed

Replying to hamish:

hi, could you try the latest nightly wingrass build? I think this is now fixed.

Hi, I tried r.shaded.relief with WinGRASS-6.4.SVN-r41137 and it works perfectly fine.
I changed the ticket to fixed: is this OK?
Thanks,
Luigi

Hamish

in reply to:  3 comment:4 by hamish, 15 years ago

Replying to lponti:

Hi, I tried r.shaded.relief with WinGRASS-6.4.SVN-r41137 and it works perfectly fine.

good

I changed the ticket to fixed: is this OK?

sure

Note: See TracTickets for help on using tickets.