trouble with cl in cygwin
tomph wrote on Mar 13, 2008
I've seen a few similar problems around but havnt been able to get it sorted yet
I have cygwin with x11 and all shells installed. Iraf was installed following the steps from http://www.iac.es/sieinvens/siepedia/pmwiki.php?n=HOWTOs.IrafCygwin
I get the following error message when i try to execute iraf with cl, I have created a login.cl file
ERROR: Cannot open connected subprocess <./x_system.e>
called as: 'prcache <directory>'
called as: 'cl <>'
called as: 'cl <>'
Error while reading login.cl file - may need to rebuild with mkiraf
Fatal startup error. CL dies
My experience is limited so all i have tried so far is retrying mkiraf. Sorry If this is a common problem but I've not been able to sort it
Cheers</em>
I have cygwin with x11 and all shells installed. Iraf was installed following the steps from http://www.iac.es/sieinvens/siepedia/pmwiki.php?n=HOWTOs.IrafCygwin
I get the following error message when i try to execute iraf with cl, I have created a login.cl file
ERROR: Cannot open connected subprocess <./x_system.e>
called as: 'prcache <directory>'
called as: 'cl <>'
called as: 'cl <>'
Error while reading login.cl file - may need to rebuild with mkiraf
Fatal startup error. CL dies
My experience is limited so all i have tried so far is retrying mkiraf. Sorry If this is a common problem but I've not been able to sort it
Cheers</em>
tomph wrote on Mar 13, 2008
oh on a further note that may help find the problem
before that error message it says
setting terminal type to xgterm...
ok so i tried the command xgterm on its own and this is what i get
/usr/local/bin/xgterm Xt error: Can't open display:
/usr/local/bin/xgterm Xt error: Can't open display:
/usr/local/bin/xgterm Xt error: Can't open display:
/usr/local/bin/xgterm Xt error: Can't open display:
/usr/local/bin/xgterm Xt error: Can't open display:
/usr/local/bin/xgterm Xt error: Can't open display:
before that error message it says
setting terminal type to xgterm...
ok so i tried the command xgterm on its own and this is what i get
/usr/local/bin/xgterm Xt error: Can't open display:
/usr/local/bin/xgterm Xt error: Can't open display:
/usr/local/bin/xgterm Xt error: Can't open display:
/usr/local/bin/xgterm Xt error: Can't open display:
/usr/local/bin/xgterm Xt error: Can't open display:
/usr/local/bin/xgterm Xt error: Can't open display:
Mike Fitzpatrick wrote on Mar 13, 2008
The two problems may be related, although I've never seen the first error message before. You'll need to start Cygwin/X11 *before* starting the xgterm window. You second message is telling you that the xgterm can't connect to the X11 server that needs to be running already.
In the first case, the CL will try to "cache" the x_system.e binary and the message means that either the binary can't be found or can't be executed. One thing to try is to start the binary manually to see whether a host-level error message is any more informative. For example, at the cygwin prompt type
If you get a '>' prompt it started normally and you can type 'bye' to quit it, otherwise please post the error message. A 'Command not found' error may mean the binaries weren't unpacked correctly and you should verify the file is actually there.
Cheers,
-Mike
In the first case, the CL will try to "cache" the x_system.e binary and the message means that either the binary can't be found or can't be executed. One thing to try is to start the binary manually to see whether a host-level error message is any more informative. For example, at the cygwin prompt type
% /iraf/iraf/bin.cygwin/x_system.eIf you get a '>' prompt it started normally and you can type 'bye' to quit it, otherwise please post the error message. A 'Command not found' error may mean the binaries weren't unpacked correctly and you should verify the file is actually there.
Cheers,
-Mike
tomph wrote on Mar 13, 2008
i tried the /iraf/iraf/bin.cygwin/x_system.e and
>
was displayed
Is this a good thing?
Sorry I'm fairly new to the guts of IRAF, thanks very much for your time though i much appreciate it
>
was displayed
Is this a good thing?
Sorry I'm fairly new to the guts of IRAF, thanks very much for your time though i much appreciate it
Mike Fitzpatrick wrote on Mar 13, 2008
Means the system executable can start correctly on its own. Now, start the X11 server, then fire up an xgterm and in that window try 'cl'.
-Mike
-Mike
tomph wrote on Mar 13, 2008
Ok from my cygwin window i tried initialising x with the following result, there seems to be a lot more information on the source of the problem here. I have tried reinstalling both x11 and iraf but keep getting the same result when trying cl as my original error
$ startx
Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 6.8.99.901-4
Contact: cygwin-xfree@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: 1280 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 shar
ed memory support in the kernel
(--) Setting autorepeat to delay=500, rate=31
(--) winConfigKeyboard - Layout: "00000809" (00000809)
(--) Using preset keyboard for "English (United Kingdom)" (809), type "4"
Rules = "xorg" Model = "pc105" Layout = "gb" Variant = "(null)" Options = "(null
)"
7 [main] X 26948 child_copy: linked dll data write copy failed, 0x3D3000..
0x3D4020, done 0, windows pid 24204, Win32 error 87
(EE) Couldn't load XKB keymap, falling back to pre-XKB keymap
(--) 5 mouse buttons found
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from li
st!
winPointerWarpCursor - Discarding first warp: 640 384
winInitMultiWindowWM - pthread_mutex_lock () returned.
winProcEstablishConnection - Hello
winInitClipboard ()
winInitMultiWindowWM - pthread_mutex_unlock () returned.
winMultiWindowXMsgProc - pthread_mutex_lock () returned.
winInitMultiWindowWM - DISPLAY=127.0.0.1:0.0
winMultiWindowXMsgProc - pthread_mutex_unlock () returned.
winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0
winClipboardProc - Hello
DetectUnicodeSupport - Windows NT/2000/XP
winClipboardProc - DISPLAY=127.0.0.1:0.0
winProcEstablishConnection - winInitClipboard returned.
winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the disp
lay.
winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the di
splay.
winClipboardProc - XOpenDisplay () returned and successfully opened the display.
winProcSetSelectionOwner - Clipboard not yet started, aborting.
winProcSetSelectionOwner - Clipboard not yet started, aborting.
xterm Xt error: Can't open display:
xterm: DISPLAY is not set
xterm Xt error: Can't open display:
xterm: DISPLAY is not set
xterm Xt error: Can't open display:
xterm: DISPLAY is not set
xterm Xt error: Can't open display:
xterm: DISPLAY is not set
xterm Xt error: Can't open display:
xterm: DISPLAY is not set
xterm Xt error: Can't open display:
xterm: DISPLAY is not set
waiting for X server to shut down winClipboardProc - winClipboardFlushWindowsMes
sageQueue trapped WM_QUIT message, exiting main loop.
winClipboardProc - XDestroyWindow succeeded.
winClipboardIOErrorHandler!
$ startx
Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 6.8.99.901-4
Contact: cygwin-xfree@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: 1280 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 shar
ed memory support in the kernel
(--) Setting autorepeat to delay=500, rate=31
(--) winConfigKeyboard - Layout: "00000809" (00000809)
(--) Using preset keyboard for "English (United Kingdom)" (809), type "4"
Rules = "xorg" Model = "pc105" Layout = "gb" Variant = "(null)" Options = "(null
)"
7 [main] X 26948 child_copy: linked dll data write copy failed, 0x3D3000..
0x3D4020, done 0, windows pid 24204, Win32 error 87
(EE) Couldn't load XKB keymap, falling back to pre-XKB keymap
(--) 5 mouse buttons found
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from li
st!
winPointerWarpCursor - Discarding first warp: 640 384
winInitMultiWindowWM - pthread_mutex_lock () returned.
winProcEstablishConnection - Hello
winInitClipboard ()
winInitMultiWindowWM - pthread_mutex_unlock () returned.
winMultiWindowXMsgProc - pthread_mutex_lock () returned.
winInitMultiWindowWM - DISPLAY=127.0.0.1:0.0
winMultiWindowXMsgProc - pthread_mutex_unlock () returned.
winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0
winClipboardProc - Hello
DetectUnicodeSupport - Windows NT/2000/XP
winClipboardProc - DISPLAY=127.0.0.1:0.0
winProcEstablishConnection - winInitClipboard returned.
winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the disp
lay.
winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the di
splay.
winClipboardProc - XOpenDisplay () returned and successfully opened the display.
winProcSetSelectionOwner - Clipboard not yet started, aborting.
winProcSetSelectionOwner - Clipboard not yet started, aborting.
xterm Xt error: Can't open display:
xterm: DISPLAY is not set
xterm Xt error: Can't open display:
xterm: DISPLAY is not set
xterm Xt error: Can't open display:
xterm: DISPLAY is not set
xterm Xt error: Can't open display:
xterm: DISPLAY is not set
xterm Xt error: Can't open display:
xterm: DISPLAY is not set
xterm Xt error: Can't open display:
xterm: DISPLAY is not set
waiting for X server to shut down winClipboardProc - winClipboardFlushWindowsMes
sageQueue trapped WM_QUIT message, exiting main loop.
winClipboardProc - XDestroyWindow succeeded.
winClipboardIOErrorHandler!
Mike Fitzpatrick wrote on Mar 13, 2008
xterm: DISPLAY is not set
xterm Xt error: Can't open display:
In your .cshrc file try setting:
setenv DISPLAY :0
or, if you use the bash shell edit your .bashrc or .profile to include
export DISPLAY = :0
This will tell the xterm to connect to the local X server.
-Mike
tomph wrote on Mar 13, 2008
thanks for the help but having loads of problems- im cutting my losses and restarting from scratch, if this fails i may look into trying iraf on ubumtu
cheers again
cheers again
tomph wrote on Mar 13, 2008
*ubuntu
tomph wrote on Mar 13, 2008
heya yeah i didnt realise you had to set it xgterm first because it kept saying 'setting terminal type to xgterm' when starting iraf
Im fairly new with iraf so thanks for the help
Im fairly new with iraf so thanks for the help
irojas wrote on Mar 13, 2008
Hello
I have the same problem, I installed iraf in cygwin and it worked, but for some unknown reason, now it do not work, try reinstalling did not work.
My starx is functional, as well as the xgterm. I tried mkiraf do not solve the problem, and tried the /iraf/iraf/bin.cygwin/x_system.e and
>
was displayed.
He tells me the following error:
$ cl
**:
^
ERROR: syntax error
called as: `cl`
called as: `cl`
Error while reading login.cl file - may be to rebuild whit mkiraf
Fatal startup error. CL dies.
Helpme please.
IsaÃas Rojas
I have the same problem, I installed iraf in cygwin and it worked, but for some unknown reason, now it do not work, try reinstalling did not work.
My starx is functional, as well as the xgterm. I tried mkiraf do not solve the problem, and tried the /iraf/iraf/bin.cygwin/x_system.e and
>
was displayed.
He tells me the following error:
$ cl
**:
^
ERROR: syntax error
called as: `cl`
called as: `cl`
Error while reading login.cl file - may be to rebuild whit mkiraf
Fatal startup error. CL dies.
Helpme please.
IsaÃas Rojas
Last post on Mar 13, 2008