[winGRASS] Re: [GRASS-user] grass.bat script for Cygwin GRASS
	6.2.2-1
    Luigi Ponti 
    lponti at infinito.it
       
    Fri Aug 31 03:30:45 EDT 2007
    
    
  
Hamish wrote:
> Luigi Ponti wrote:
>   
>> Installation instructions at 
>> <http://grass.itc.it/grass62/binary/mswindows/> say that "there's no 
>> grass.bat script", but (no matter what I try) there is no way for me to 
>> start grass with the recommended cygwin_grass.bat. It just works fine
>> if there is an X server already started from a previous grass.bat run.
>>
>> Below you find the error log I have obtained via the following command
>>     cygwin_grass.bat > c:\cygwin\all_out.txt 2>&1
>>     
> ..
>   
>> Starting GRASS ...
>> Application initialization failed: this isn't a Tk applicationcouldn't 
>> connect to display "localhost:0"
>> Error in startup script: dynamic loading is not currently available on 
>> this system
>>     while executing
>> "load /usr/local/lib/tk8.4/../libtk8.4.a Tk"
>>     
> ..
>
>
> Did you modify the bash line to run startx, launching X at startup?
>   bash --login -i -c startx
>
>   
Yes, I did. Here is my cygwin_grass.bat file:
    @echo off
    C:
    chdir C:\cygwin\bin
    set GRASS_AUTOSTART=1
    bash --login -i -c startx
If I run just the last line at the command prompt:
    bash --login -i -c startx > c:\cygwin\all_out.txt 2>&1
I get the following all_out.txt:
    Welcome to the XWin X Server
    Vendor: The Cygwin/X Project
    Release: 6.8.99.901-4
    Contact: cygwin-xfree at cygwin.com
    XWin was started with the following command line:
    X :0 -multiwindow -clipboard
    _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
    winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1
    (II) XF86Config is not supported
    (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more
    information
    winDetectSupportedEngines - Windows NT/2000/XP
    winDetectSupportedEngines - DirectDraw installed
    winDetectSupportedEngines - DirectDraw4 installed
    winDetectSupportedEngines - Returning, supported engines 00000007
    winSetEngine - Multi Window or Rootless => ShadowGDI
    winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits
    per pixel
    winAllocateFBShadowGDI - Creating DIB with width: 1024 height: 768
    depth: 32
    winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff
    winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d
    24 bpp 32
    null screen fn ReparentWindow
    null screen fn RestackWindow
    InitQueue - Calling pthread_mutex_init
    InitQueue - pthread_mutex_init returned
    InitQueue - Calling pthread_cond_init
    InitQueue - pthread_cond_init returned
    winInitMultiWindowWM - Hello
    winInitMultiWindowWM - Calling pthread_mutex_lock ()
    winMultiWindowXMsgProc - Hello
    winMultiWindowXMsgProc - Calling pthread_mutex_lock ()
    MIT-SHM extension disabled due to lack of kernel support
    XFree86-Bigfont extension local-client optimization disabled due to
    lack of shared memory support in the kernel
    (--) Setting autorepeat to delay=500, rate=31
    (--) winConfigKeyboard - Layout: "00000410" (00000410)
    (--) Using preset keyboard for "Italian" (410), type "4"
    Rules = "xorg" Model = "pc105" Layout = "it" Variant = "(null)"
    Options = "(null)"
    The XKEYBOARD keymap compiler (xkbcomp) reports:
     > Warning:          Type "ONE_LEVEL" has 1 levels, but <RALT> has 2
    symbols
     >                   Ignoring extra symbols
    Errors from xkbcomp are not fatal to the X server
    (--) 3 mouse buttons found
    Could not init font path element /usr/X11R6/lib/X11/fonts/TTF/,
    removing from list!
    Could not init font path element /usr/X11R6/lib/X11/fonts/Type1/,
    removing from list!
    Could not init font path element /usr/X11R6/lib/X11/fonts/CID/,
    removing from list!
    Could not init font path element /usr/X11R6/lib/X11/fonts/100dpi/,
    removing from list!
    winPointerWarpCursor - Discarding first warp: 512 384
    winInitMultiWindowWM - pthread_mutex_lock () returned.
    winProcEstablishConnection - Hello
And X does start (it is an X terminal and if I type grass62 and hit 
return, GRASS starts just fine). But if I manually run at promt:
    set GRASS_AUTOSTART=1
    bash --login -i -c startx
the next thing I see is the GRASS startup message
    Cleaning up temporary files.....
    Starting GRASS ...
And no X runs. GRASS starts in text mode but then it tries to load a GUI 
and off course this fails.
Hope I provided some useful info. Thanks in advance,
Luigi
P.S. I also added the following at the and of .bashrc
#################
# Start GRASS
if [ -n "$DISPLAY" ] && [ -n "$GRASS_AUTOSTART" ] ; then
   unset GRASS_AUTOSTART
   exec grass62
fi
#################
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/grass-windows/attachments/20070831/853d7f6a/attachment.html
    
    
More information about the grass-windows
mailing list