Another thing I just noticed looking at grass64svn script ArcGIS has set the variable PYTHONPATH=C:\Program Files (x86)\ArcGIS\bin
Could that be related? On Tue, Jul 6, 2010 at 8:54 AM, Daniel Victoria <[email protected]> wrote: > Hi all, > > I don't see any leftover cygwin instalation in my path. I even tried > removing python(xy) to see if that was the culprit. > Here are some of the environmental variables set in the msys shell > that I believe influences grass: > > PATH=.:/usr/local/bin:/mingw/bin:/bin:/c/Windows/system32:/c/Windows:/c/Windows/System32/Wbem:/c/Windows/System32/WindowsPowerShell/v1.0/:/c/Program > Files (x86)/OpenSSH/bin:/c/Windows/System32 > WD=C:\PROGRA~2\GRASS-~1\msys\bin\ > !C:=C:\Program Files (x86)\GRASS-64-SVN\msys > PART1=C:\PROGRA~2\GRASS-~1\msys\bin\ > OLDPWD=/c/Program Files (x86)/GRASS-64-SVN/msys > > But I did notice that in the python error that I get, the first error > uses forward slashes (/) and the following lines, the paths have back > slashes (\). Could that be related? > > $ Traceback (most recent call last): > File "c:/Program Files (x86)/GRASS-64-SVN/etc/wxpython/wxgui.py", > line 85, in <module> > import gui_modules.preferences as preferences > File "c:\Program Files > (x86)\GRASS-64-SVN\etc\wxpython\gui_modules\preferences.py", line 807, > in <module> > <more errors removed> > > Thanks for all your help > Daniel > > On Mon, Jul 5, 2010 at 9:59 PM, Daniel Victoria > <[email protected]> wrote: >> I just installed WinGrass in my home WinXP box and it's working fine. >> It also gives me the "Bourne Shell (/bin/sh)" line as reported by >> Luigi, instead of the ("GNU Bash (Cygwin) (/usr/bin/bash.exe)") I saw >> at my Win7 box. So chances are my Win7 has some left over cygwin >> installation and a messed up %PATH%. Will look into that tomorrow >> morning. >> >> Cheers and thanks >> Daniel >> >> On Mon, Jul 5, 2010 at 8:03 PM, Daniel Victoria >> <[email protected]> wrote: >>> It could be that I have some Cygwin install left over. I also have >>> python(x,y) installed but don't think that is what is messing with >>> WinGrass. I will take a look at my path environmental variables and >>> post an update tomorrow. >>> >>> Thanks >>> daniel >>> >>> On Mon, Jul 5, 2010 at 6:19 PM, Luigi Ponti <[email protected]> wrote: >>>> ...sorry: reposting with a decent subject line... >>>> >>>> Dear Daniel, >>>> >>>> I have a one-month-old (apologize) wingrass 6.4.svn installed from >>>> http://josef.fsv.cvut.cz/wingrass/ on windows7. >>>> >>>> Date: Mon, 5 Jul 2010 17:11:39 -0300 >>>> From: Daniel Victoria <[email protected]> >>>> >>>> >>>> [...] Opening a separate MSys console >>>> and executing /grass/bin/grass64svn will start the Select location >>>> window and after I click on Start, Grass crashes with the following >>>> error: >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------------------------------------ >>>> $ grass64svn >>>> Cleaning up temporary files ... >>>> Starting GRASS ... >>>> ATENÇÃO: Attention! >>>> ATENÇÃO: Locking is not supported on Windows! >>>> __________ ___ __________ _______________ >>>> / ____/ __ \/ | / ___/ ___/ / ____/ _/ ___/ >>>> / / __/ /_/ / /| | \__ \\_ \ / / __ / / \__ \ >>>> / /_/ / _, _/ ___ |___/ /__/ / / /_/ // / ___/ / >>>> \____/_/ |_/_/ |_/____/____/ \____/___//____/ >>>> >>>> Welcome to GRASS 6.4.0svn (2010) >>>> GRASS homepage: http://grass.osgeo.org/ >>>> This version running thru: GNU Bash (Cygwin) >>>> (/usr/bin/bash.exe) >>>> >>>> >>>> sounds like you are running through Cygwin ("GNU Bash (Cygwin) >>>> (/usr/bin/bash.exe)") -- on my machine the MSys desktop link triggers a >>>> welcome screen that at the same line says "Bourne Shell (/bin/sh)" (and >>>> everything works as expected including the wxpython GUI): >>>> >>>> Cleaning up temporary files ... >>>> Starting GRASS ... >>>> ATTENZIONE: Attention! >>>> ATTENZIONE: Locking is not supported on Windows! >>>> __________ ___ __________ _______________ >>>> / ____/ __ \/ | / ___/ ___/ / ____/ _/ ___/ >>>> / / __/ /_/ / /| | \__ \\_ \ / / __ / / \__ \ >>>> / /_/ / _, _/ ___ |___/ /__/ / / /_/ // / ___/ / >>>> \____/_/ |_/_/ |_/____/____/ \____/___//____/ >>>> >>>> Welcome to GRASS 6.4.0svn (2010) >>>> GRASS homepage: http://grass.osgeo.org/ >>>> This version running thru: Bourne Shell (/bin/sh) >>>> 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 >>>> >>>> GRASS 6.4> >>>> >>>> Do you by any chance have Cygwin bash.exe on your %PATH% environmental >>>> variable? >>>> >>>> As for the Python errors you mention, I am not sure but it may again be a >>>> problem related to %PATH% settings. It is indeed possible to have heritage >>>> Cygwin/GRASS and the new native Wingrass running on the same machine, but >>>> care must be taken to avoid messing with the global %PATH%. >>>> >>>> As for running R from GRASS, an approach I have found useful is to follow >>>> the advice by Glynn Clements, i.e. not running GRASS from MSys but instead >>>> use a simple DOS box started via a batch file that sets required >>>> environmental variables to run GRASS, and then call the shell executable >>>> sh.exe (shell scripts designed for Cygwin/GRASS run with minimal >>>> adjustments >>>> -- mostly to cope with MSys path conventions issues). Glynn has taken on >>>> this topic in a growing (thanks for your patience, Glynn!) number of posts >>>> -- see for example: >>>> http://osgeo-org.1803224.n2.nabble.com/grass-start-bat-in-windows-tp4492202p4492202.html >>>> >>>> Finally, when I have my GRASS-enabled DOS box, I just type R (of course R >>>> needs to be in the %PATH%) and I am pretty much done. >>>> >>>> I hope this helps and sorry if I misunderstood your questions, >>>> >>>> Luigi >>>> >>>> >>> >> > _______________________________________________ grass-user mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-user
