Re: update cygwin and now X wont start!
I believe Windows Firewall has a setting for applications. Some PC firewalls do (the one I have does), meaning if the executable changes you have to tell the firewall it's ok for it to go again. Even though your post indicates it is failing at startup, the error is reporting socket access issues, meaning the network and therefore involving the firewall. You should find a Windows Firewall icon in Control Panel. Try poking around in there. I can't help you more than that because I don't have any XP boxes around here, just W2K. But I would start by looking for an entry for Xwin. If WXP does what it's supposed to do, when the exe changes it should turn off access at the firewall. The idiotic thing is that it should ask you for permission to turn on again. Unfortunately, it's not starting up enough for you to get to the network to actually cause a popup request for access, and somehow the security features probably in the firewall are locking out socket access. One thing you CAN check, to see if it's the firewall, is turn off the firewall completely before you start xwin. If that doesn't work, my Windows paranoia is also telling me to say that you might want to reboot with the firewall OFF and try to start xwin when it comes back up, but you have to disable the service to shut it off completely. If you use another firewall like Symantec's, you have to fiddle with that instead, for example, because that would substitute itself for Windows Firewall. Just in case you don't do much with firewalls, it goes without saying that you should not turn off your firewall if you are on the internet. But it won't be so bad if you are behind a cable/DSL router that has a builtin firewall/NAT router, because that will protect you for the limited time you need to test. Otherwise, if you are on campus Res LAN, for example, don't do it! BZ. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
erorr messages-cygwin
Dear Sir, I did the full installation of cygwin, but when I run it, it gives me the error messages below. Could you please help me resolving these errors or tell me what I did wrong? Thanks, Ahmed : command not foundtxwin.sh: line 8: : command not foundtxwin.sh: line 11: : command not foundtxwin.sh: line 12: : command not foundtxwin.sh: line 18: : command not foundtxwin.sh: line 19: : command not foundtxwin.sh: line 89: : command not foundtxwin.sh: line 90: : command not foundtxwin.sh: line 94: : command not foundtxwin.sh: line 95: : command not foundtxwin.sh: line 100: : command not foundtxwin.sh: line 102: Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 6.8.99.901-4 Contact: cygwin-xfree@cygwin.com winInitializeDefaultScreens - w 1280 h 1024 winInitializeDefaultScreens - Returning _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root XWin was started with the following command line: XWin 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 0007 winSetEngine - Using Shadow DirectDraw NonLocking winAdjustVideoModeShadowDDNL - Using Windows display depth of 32 bits per pixel winFinishScreenInitFB - Masks: 00ff ff00 00ff : command not foundtxwin.sh: line 103: 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: 0409 (0409) (--) Using preset keyboard for English (USA) (409), type 4 Rules = xorg Model = pc105 Layout = us Variant = (null) Options = (null ) : command not foundtxwin.sh: line 104: expected keysym, got XF86_Switch_VT_1: line 8 of xfree86 expected keysym, got XF86_Switch_VT_2: line 11 of xfree86 expected keysym, got XF86_Switch_VT_3: line 14 of xfree86 expected keysym, got XF86_Switch_VT_4: line 17 of xfree86 expected keysym, got XF86_Switch_VT_5: line 20 of xfree86 expected keysym, got XF86_Switch_VT_6: line 23 of xfree86 expected keysym, got XF86_Switch_VT_7: line 26 of xfree86 expected keysym, got XF86_Switch_VT_8: line 29 of xfree86 expected keysym, got XF86_Switch_VT_9: line 32 of xfree86 expected keysym, got XF86_Switch_VT_10: line 35 of xfree86 expected keysym, got XF86_Switch_VT_11: line 38 of xfree86 expected keysym, got XF86_Switch_VT_12: line 41 of xfree86 expected keysym, got XF86_Ungrab: line 45 of xfree86 expected keysym, got XF86_ClearGrab: line 48 of xfree86 expected keysym, got XF86_Next_VMode: line 51 of xfree86 expected keysym, got XF86_Prev_VMode: line 54 of xfree86 The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Multiple interpretations of NoSymbol+AnyOfOrNone(all) Using last definition for duplicate fields Warning: Multiple interpretations of NoSymbol+AnyOfOrNone(all) Using last definition for duplicate fields Warning: Multiple interpretations of NoSymbol+AnyOfOrNone(all) Using last definition for duplicate fields Warning: Multiple interpretations of NoSymbol+AnyOfOrNone(all) Using last definition for duplicate fields Warning: Multiple interpretations of NoSymbol+AnyOfOrNone(all) Using last definition for duplicate fields Warning: Multiple interpretations of NoSymbol+AnyOfOrNone(all) Using last definition for duplicate fields Warning: Multiple interpretations of NoSymbol+AnyOfOrNone(all) Using last definition for duplicate fields Warning: Multiple interpretations of NoSymbol+AnyOfOrNone(all) Using last definition for duplicate fields Warning: Multiple interpretations of NoSymbol+AnyOfOrNone(all) Using last definition for duplicate fields Warning: Multiple interpretations of NoSymbol+AnyOfOrNone(all) Using last definition for duplicate fields Warning: Multiple interpretations of NoSymbol+AnyOfOrNone(all) Using last definition for duplicate fields Warning: Multiple interpretations of NoSymbol+AnyOfOrNone(all) Using last definition for duplicate fields Warning: Multiple interpretations of NoSymbol+AnyOfOrNone(all) Using last definition for duplicate fields Warning: Multiple interpretations of NoSymbol+AnyOfOrNone(all) Using last definition for duplicate fields Warning: Multiple interpretations of NoSymbol+AnyOfOrNone(all) Using last definition for duplicate fields
Problems with terminal -tn setting TERM variable
Sorry for the crosspost - I posted this on the Cygwin list last week, but didn't get a response, and realized that it probably belonged better on this list, so I'm trying again. I'm sorry if there's an easy solution that I haven't found yet, but I'm wondering if anyone else is experiencing the same problem with Cygwin/X's xterm as I am. xterm -tn doesn't seem to properly set up the TERM variable. For example: xterm -tn xterm-16color -e bash -c 'echo TERM=$TERM; read x' pops up a Cygwin/X xterm window containing TERM=xterm Whereas rxvt -tn xterm-16color -e bash -c 'echo TERM=$TERM; read x' pops up a Cygwin/X rxvt window containing TERM=xterm-16color Can anyone else confirm this behavior, or offer a suggestion on how to deal with this behavior? I want to use xterm, since I couldn't get the same level of unicode support in rxvt cygwin native, rxvt cygwin x unicode, or rxvt cygwin. I also don't want to explicitly set TERM in one of my dot files, since I use the same ones on many computers. Thanks in advance for any help! ~Matt Wozniski Cygwin Configuration Diagnostics Current System Time: Fri Nov 03 10:21:18 2006 Windows XP Professional Ver 5.1 Build 2600 Service Pack 2 Path: c:\cygwin\usr\local\bin c:\cygwin\bin c:\cygwin\bin c:\cygwin\usr\X11R6\bin . c:\Program Files\Reflection c:\WINDOWS\system32 c:\WINDOWS c:\WINDOWS\System32\Wbem c:\Sybase\DLL c:\Sybase\BIN c:\Program Files\Sybase\Sybase Central\win32 c:\Sybase\ASEP Output from c:\cygwin\bin\id.exe (nontsec) UID: 112940(woznismj) GID: 10545(mkgroup-l-d) 0(root) 544(Administrators) 547(Power Users) 545(Users) 10545(mkgroup-l-d) Output from c:\cygwin\bin\id.exe (ntsec) UID: 112940(woznismj) GID: 10545(mkgroup-l-d) 0(root) 544(Administrators) 547(Power Users) 545(Users) 10545(mkgroup-l-d) SysDir: C:\WINDOWS\system32 WinDir: C:\WINDOWS HOME = '/cygdrive/c/Documents and Settings/woznismj' PWD = '/cygdrive/c/Documents and Settings/woznismj' USER = 'woznismj' MAKE_MODE = 'unix' ALLUSERSPROFILE = 'C:\Documents and Settings\All Users' APPDATA = 'C:\Documents and Settings\woznismj\Application Data' CLASSPATH = 'C:\Sybase\ASEP\Monclass.zip;C:\Sybase\ASEP\3pclass.zip;' CLIENTNAME = 'Console' COMMONPROGRAMFILES = 'C:\Program Files\Common Files' COMPUTERNAME = '197PRGRCOOP' COMSPEC = 'C:\WINDOWS\system32\cmd.exe' CYGWIN_ROOT = '\cygwin' EDITOR = 'vim' FP_NO_HOST_CHECK = 'NO' HOMEDRIVE = 'C:' HOMEPATH = '\Documents and Settings\woznismj' INCLUDE = 'C:\Sybase\INCLUDE' LIB = 'C:\Sybase\LIB' LOGONSERVER = '\\MLAS001' NUMBER_OF_PROCESSORS = '1' OS = 'Windows_NT' PATHEXT = '.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH' PROCESSOR_ARCHITECTURE = 'x86' PROCESSOR_IDENTIFIER = 'x86 Family 15 Model 2 Stepping 4, GenuineIntel' PROCESSOR_LEVEL = '15' PROCESSOR_REVISION = '0204' PROGRAMFILES = 'C:\Program Files' PROMPT = '$P$G' SESSIONNAME = 'Console' SYBASE = 'C:\Sybase' SYSTEMDRIVE = 'C:' SYSTEMROOT = 'C:\WINDOWS' TEMP = '/cygdrive/c/DOCUME~1/woznismj/LOCALS~1/Temp' TMP = '/cygdrive/c/DOCUME~1/woznismj/LOCALS~1/Temp' USERDNSDOMAIN = 'DUPONTNET.NET' USERDOMAIN = 'DUPONTNET' USERPROFILE = 'C:\Documents and Settings\woznismj' VISUAL = 'vim' WINDIR = 'C:\WINDOWS' TERM = 'xterm' COLORFGBG = 'default;default;0' DISPLAY = ':0' WINDOWID = '6832192' TZ = 'EST5EDT4,M4.1.0/2,M10.5.0/2' LOGNAME = 'woznismj' SHLVL = '1' OLDPWD = '/cygdrive/c/Documents and Settings/woznismj' PAGER = 'less' MANPATH = '/usr/local/man:/usr/share/man:/usr/man::/usr/ssl/man' INFOPATH = '/usr/local/info:/usr/share/info:/usr/info:' CVS_RSH = '/bin/ssh' PKG_CONFIG_PATH = '/usr/X11R6/lib/pkgconfig' SHELL = '/usr/bin/zsh' PRINTER = '\\mlps001\197-2' LD_LIBRARY_PATH_64 = '/cygdrive/c/Documents and Settings/woznismj/projects/grs/DDPCgrs/lib:' NO_TTY_MOUSE = '1' MINICOM = '-w -z -C /dev/null -c off' LS_COLORS = 'no=00:fi=00:di=01;34:ln=01;36:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.bz2=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.avi=01;35:*.fli=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.ogg=01;35:*.mp3=01;35:*.wav=01;35:' COLORSCHEME = 'light' HISTSIZE = '15000' SAVEHIST = '1' HISTFILE = '/cygdrive/c/Documents and Settings/woznismj/.zsh_history' DIRSTACKSIZE = '10' LANG = 'en_US.UTF-8' _ = '/usr/bin/cygcheck' POSIXLY_CORRECT = '1' HKEY_CURRENT_USER\Software\Cygnus Solutions HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2 (default) = '/cygdrive' cygdrive flags = 0x0022 HKEY_CURRENT_USER\Software\Cygnus
Re: Problems with terminal -tn setting TERM variable
On Fri, 3 Nov 2006, Matt Wozniski wrote: Sorry for the crosspost - I posted this on the Cygwin list last week, but didn't get a response, and realized that it probably belonged better on this list, so I'm trying again. I'm sorry if there's an easy solution that I haven't found yet, but I'm wondering if anyone else is experiencing the same problem with Cygwin/X's xterm as I am. xterm -tn doesn't seem to properly set up the TERM variable. For example: xterm -tn xterm-16color -e bash -c 'echo TERM=$TERM; read x' pops up a Cygwin/X xterm window containing TERM=xterm Whereas rxvt -tn xterm-16color -e bash -c 'echo TERM=$TERM; read x' pops up a Cygwin/X rxvt window containing TERM=xterm-16color Can anyone else confirm this behavior, or offer a suggestion on how to deal with this behavior? I want to use xterm, since I couldn't get the same level of unicode support in rxvt cygwin native, rxvt cygwin x unicode, or rxvt cygwin. I also don't want to explicitly set TERM in one of my dot files, since I use the same ones on many computers. I can reproduce your particular testcase, not surprisingly. According to the xterm manpage, This terminal type must exist in the terminal database (termcap or terminfo, depending on how xterm is built) and should have li# and co# entries. If the terminal type is not found, xterm uses the built-in list ``xterm'', ``vt102'', etc. xterm -tn ansi and xterm -tn vt100 both work. You need to look at your terminal database and figure out why xterm is not picking it up. HTH, Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ [EMAIL PROTECTED] | [EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_Igor Peshansky, Ph.D. (name changed!) |,4- ) )-,_. ,\ ( `'-'old name: Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte. But no -- you are no fool; you call yourself a fool, there's proof enough in that! -- Rostand, Cyrano de Bergerac -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
compilation problems
Hi, I'm new to the mailing list and cygwin/x development. I followed the directions on http://x.cygwin.com/docs/cg/prog-build-native.html to produce a Standard Build, but 'make World' fails at a certain point: make[7]: Leaving directory `/x-devel/build/std/lib/GL/mesa/shader/slang/library' make[6]: Leaving directory `/x-devel/build/std/lib/GL/mesa/shader/slang' make[5]: Leaving directory `/x-devel/build/std/lib/GL/mesa/shader' make[4]: Leaving directory `/x-devel/build/std/lib/GL/mesa' cleaning in lib/GL/glx... make[4]: Entering directory `/x-devel/build/std/lib/GL/glx' Makefile:8: *** missing separator. Stop. make[4]: Leaving directory `/x-devel/build/std/lib/GL/glx' make[3]: *** [clean] Error 2 make[3]: Leaving directory `/x-devel/build/std/lib/GL' make[2]: *** [clean] Error 2 make[2]: Leaving directory `/x-devel/build/std/lib' make[1]: *** [clean] Error 2 make[1]: Leaving directory `/x-devel/build/std' make: *** [World] Error 2 Is this an innocuous error which I can safely work around it by running make with the -i flag, or is there something really wrong that I need to fix? Thanks, TJ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Problems with terminal -tn setting TERM variable
On 11/3/06, Igor Peshansky [EMAIL PROTECTED] wrote: According to the xterm manpage, This terminal type must exist in the terminal database (termcap or terminfo, depending on how xterm is built) and should have li# and co# entries. If the terminal type is not found, xterm uses the built-in list ``xterm'', ``vt102'', etc. xterm -tn ansi and xterm -tn vt100 both work. You need to look at your terminal database and figure out why xterm is not picking it up. HTH, Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] | [EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_Igor Peshansky, Ph.D. (name changed!) |,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte. But no -- you are no fool; you call yourself a fool, there's proof enough in that! -- Rostand, Cyrano de Bergerac Well, mystery solved, it's using termcap instead of terminfo, but why would on earth would two Cygwin xterm packages (mine and Igor's) use two different terminal capability databases? The man page says that it depends on how it was built, but how could the two packages have been built differently? Igor: Does grep '^xterm' /etc/termcap give you more than just one line defining xterm-r6 and xterm? I'm just trying to figure out if yours is also using termcap and your termcap entry covers xterm-16color, or if yours is using terminfo like it ought to be. Thanks for any insight anyone can provide. ~Matt -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Problems with terminal -tn setting TERM variable
On Fri, 3 Nov 2006, Matt Wozniski wrote: On 11/3/06, Igor Peshansky [EMAIL PROTECTED] wrote: http://cygwin.com/acronyms/#PCYMTNQREAIYR. Thanks. According to the xterm manpage, This terminal type must exist in the terminal database (termcap or terminfo, depending on how xterm is built) and should have li# and co# entries. If the terminal type is not found, xterm uses the built-in list ``xterm'', ``vt102'', etc. xterm -tn ansi and xterm -tn vt100 both work. You need to look at your terminal database and figure out why xterm is not picking it up. Well, mystery solved, it's using termcap instead of terminfo, but why would on earth would two Cygwin xterm packages (mine and Igor's) use two different terminal capability databases? The man page says that it depends on how it was built, but how could the two packages have been built differently? Umm, actually, what I said was that I *could* reproduce your behavior. My xterm also uses /etc/termcap. No mystery here. Both ansi and vt100 are in /etc/termcap, and xterm-16color isn't. Igor: Does grep '^xterm' /etc/termcap give you more than just one line defining xterm-r6 and xterm? I'm just trying to figure out if yours is also using termcap and your termcap entry covers xterm-16color, or if yours is using terminfo like it ought to be. My termcap only has one entry for xterm. As for whether xterm should be using terminfo, you might want to ask the xterm maintainer to rebuild the package. HTH, Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] | [EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_Igor Peshansky, Ph.D. (name changed!) |,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte. But no -- you are no fool; you call yourself a fool, there's proof enough in that! -- Rostand, Cyrano de Bergerac -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Problems with terminal -tn setting TERM variable
Oh, I'm sorry, I misread. Well, then, that makes perfect sense. My mistake, Igor. :) Can anyone tell me who the xterm maintainer is? I was under the impression that the entirety of Cygwin/X is unmaintained. ~Matt On 11/4/06, Igor Peshansky [EMAIL PROTECTED] wrote: On Fri, 3 Nov 2006, Matt Wozniski wrote: On 11/3/06, Igor Peshansky [EMAIL PROTECTED] wrote: http://cygwin.com/acronyms/#PCYMTNQREAIYR. Thanks. According to the xterm manpage, This terminal type must exist in the terminal database (termcap or terminfo, depending on how xterm is built) and should have li# and co# entries. If the terminal type is not found, xterm uses the built-in list ``xterm'', ``vt102'', etc. xterm -tn ansi and xterm -tn vt100 both work. You need to look at your terminal database and figure out why xterm is not picking it up. Well, mystery solved, it's using termcap instead of terminfo, but why would on earth would two Cygwin xterm packages (mine and Igor's) use two different terminal capability databases? The man page says that it depends on how it was built, but how could the two packages have been built differently? Umm, actually, what I said was that I *could* reproduce your behavior. My xterm also uses /etc/termcap. No mystery here. Both ansi and vt100 are in /etc/termcap, and xterm-16color isn't. Igor: Does grep '^xterm' /etc/termcap give you more than just one line defining xterm-r6 and xterm? I'm just trying to figure out if yours is also using termcap and your termcap entry covers xterm-16color, or if yours is using terminfo like it ought to be. My termcap only has one entry for xterm. As for whether xterm should be using terminfo, you might want to ask the xterm maintainer to rebuild the package. HTH, Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] | [EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_Igor Peshansky, Ph.D. (name changed!) |,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte. But no -- you are no fool; you call yourself a fool, there's proof enough in that! -- Rostand, Cyrano de Bergerac -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
