RE: [ANNOUNCEMENT] Updated [experimental]: bash-3.1-7
Hellow everyone. I have tried to evaluate bash-3.1-7. Some hundreds of line script fails running dos file(ending line with \r\n) script on text mode mount. - $ mount | grep tmp D:\users\hagiwara\tmp on /tmp type user (binmode) D:\users\hagiwara\tmp on /tmp2 type system (textmode) $ $ bash --version GNU bash, version 3.1.17(7)-release (i686-pc-cygwin) Copyright (C) 2005 Free Software Foundation, Inc. $ $ bash0911 --version GNU bash, version 3.1.17(6)-release (i686-pc-cygwin) Copyright (C) 2005 Free Software Foundation, Inc. $ bash0911 /tmp/xxx Processing configuration file /users/hagiwara/AA/Config Platforms = Build tree root = /cygdrive/V $ $ bash0911 /tmp2/xxx Processing configuration file /users/hagiwara/AA/Config Platforms = Build tree root = /cygdrive/V $ $ bash /tmp/xxx : command not found 'tmp/xxx: line 37: syntax error near unexpected token ` 'tmp/xxx: line 37: `verify_environment() $ $ bash /tmp2/xxx /tmp2/xxx: line 377: riate: command not found /tmp2/xxx: line 384: tart: command not found /tmp2/xxx: line 385: art_msg: command not found /tmp2/xxx: line 386: cess: command not found /tmp2/xxx: line 387: ess_config: command not found $ - I am soryy I can't attach the full script file. The probrem hapens around the portion below. It's strange that some parts of comment lines are tried to execute. - 375 # 376 parse_parameters $* 377 378 # 379 # Verify that appropriate environment variables are set 380 # 381 verify_environment 382 383 # 389 # Output start message 390 # 391 output_start_msg 392 393 # 394 # Process the configuration file 395 # 396 process_config 397 - -- Kazuyuki Hagiwara ) -Original Message- ) From: [EMAIL PROTECTED] ) [mailto:[EMAIL PROTECTED] On Behalf Of Eric Blake ) Sent: Saturday, September 09, 2006 12:18 PM ) To: cygwin@cygwin.com ) Subject: [ANNOUNCEMENT] Updated [experimental]: bash-3.1-7 ) ) -BEGIN PGP SIGNED MESSAGE- ) Hash: SHA1 ) ) A new release of bash, 3.1-7, is available for experimental use. ) ) NOTICE: ) === ) This version removes several outdated #defines that were once ) necessary in older versions of cygwin, but which made bash on ) cygwin different and slower than bash on Linux. In the ) process, there is a major change in behavior - bash no longer ) forces text mode when reading scripts. If your script ) resides on a text mount point, you will not notice any difference. ) If your script resides on a binary mount point, and has ) normal unix \n line endings, you may notice a slight speedup. ) But if your script resides on a binary mount point, and has ) \r\n line endings, bash will most likely encounter syntax ) errors. The fix is simple - use d2u to convert script files ) residing on a binary mount point to be unix files, or if you ) must use DOS lines, use a text mount point. Because of this ) change in behavior, I am marking this version experimental ) for a while until I can gauge from mailing list traffic that ) it is safe to promote to current. ) ) NEWS: ) = ) This is a minor patch release. The only change is removing ) outdated cygwin-specific #ifdefs that are no longer necessary ) in light of improvements in cygwin itself. Remember, you ) must not have any bash or /bin/sh instances running when you ) upgrade the bash package. This release will work with ) cygwin-1.5.21-1 or later. ) ) DESCRIPTION: ) ) Bash is an sh-compatible shell that incorporates useful ) features from the Korn shell (ksh) and C shell (csh). It is ) intended to conform to the IEEE POSIX P1003.2/ISO 9945.2 ) Shell and Tools standard. It offers functional improvements ) over sh for both programming and interactive use. In ) addition, most sh scripts can be run by Bash without modification. ) ) As of the bash 3.0 series, cygwin /bin/sh defaults to bash, ) not ash, similar to Linux distributions. ) ) UPDATE: ) === ) To update your installation, click on the "Install Cygwin ) now" link on the http://cygwin.com/ web page. This downloads ) setup.exe to your system. ) Save it and run setup, answer the questions and pick up ) 'bash' in the 'Base' category (it should already be selected). ) ) DOWNLOAD: ) = ) Note that downloads from sources.redhat.com (aka cygwin.com) ) aren't allowed due to bandwidth limitations. This means that ) you will need to find a mirror which has this update, please ) choose the one nearest to you: ) http://cygwin.com/mirrors.html ) ) QUESTIONS: ) == ) If you want to make a point or ask a question the Cygwin ) mailing list is the appropriate place. ) ) - -- ) Eric Blake ) volunteer cygwin bash maintainer ) ) CYGWIN-ANNOUNCE UNSUBSCRIBE INFO: ) = ) To unsubscribe to the cygwin-announce mailing list, look at
rebuilding rebase
Building VLC, rebase core'd on the activex dll. I wanted to rebuild rebase 2.4.3 from source -- I got: [EMAIL PROTECTED] /usr/src/rebase-2.4.3-1 $ make make -C imagehelper imagehelper make[1]: Entering directory `/usr/src/rebase-2.4.3-1/imagehelper' g++ -O2 -c -o sections.o sections.cc sections.cc: In member function `bool Relocations::check()': sections.cc:288: error: ISO C++ forbids cast to non-reference type used as lvalue sections.cc: In member function `bool Relocations::fix()': sections.cc:331: error: ISO C++ forbids cast to non-reference type used as lvalue sections.cc: In member function `bool Relocations::relocate(int)': sections.cc:366: error: ISO C++ forbids cast to non-reference type used as lvalue make[1]: *** [sections.o] Error 1 make[1]: Leaving directory `/usr/src/rebase-2.4.3-1/imagehelper' make: *** [imagehelper] Error 2 Didn't see a way to set the C++ standard in g++ 3.4.4 The offending stacktrace had: [EMAIL PROTECTED] /usr/src/vlc-0.8.5-3 $ cat rebase.exe.stackdump Exception: STATUS_ACCESS_VIOLATION at eip=00403713 eax= ebx=6000 ecx=19668000 edx= esi= edi=2FC6D25E ebp=0022CA98 esp=0022CA60 program=C:\cygwin\bin\rebase.exe, pid 1300, thread main cs=001B ds=0023 es=0023 fs=003B gs= ss=0023 Stack trace: Frame Function Args 0022CA98 00403713 (006A0868, 6000, 0001, 6100213F) 0022CB48 00401BFD (0022CBC0, 00438044, 0001, ) 0022CB98 00401264 (0022CBC0, 0022CBBC, 61100070, 0035) 0022CCE8 0040113A (0005, 611682B4, 006A0090, 0022CC70) 0022CD98 61006168 (, 0022CDD0, 610054E0, 0022CDD0) 610054E0 61004416 (009C, A02404C7, E8610FF1, FF48) 27034 [main] rebase 1300 _cygtls::handle_exceptions: Error while dumping state (probably corrupted stack) marty -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: libungif and emacs-cvs
I didn't catch the beginning of this thread... but I frequently build cvs emacs (once a month) with cygwin and based on cygwin's x-windows. I do not have any probllem with ungif. * I do specify the following configure option ---with-gif * Last year's (of so) version of ungif had some problems, be sure to get the newest with setup.exe * The newest cygwin gtk windowning is broken somethwere, so I had to use ---with-Xaw3d (gtk people fix that!) > > checking gif_lib.h usability... yes > checking gif_lib.h presence... yes > checking for gif_lib.h... yes > checking for EGifPutExtensionLast in -lungif... no ^^ > --- > > so that it buids without ungif support: I am frequently building emacs from cvs and have not noticed this problem, but haven't looked It would probably be enlightening to look at config.log to see *why* configure thinks EGifPutExtensionLast is not in -lungif... > I do not remember this behaviour previously (but it could be), so I flag > this in the case it is a problem with libungif. Or something else completely unrelated that caused the test program to fail, thus making configure think that it didn't have a valid -lungif. HTH, Igor -- Perhaps try uninstalling and reinstalling the ungif library. Regards, Henman -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Mount does not show Samba files
Arun Biyani wrote: I am having some problems accessing files on a Linux server in Cygwin. The files are exported via Samba. I can see the whole directory using my computer, which shows a Y: directory on machine Goddard. However, "ls /y" prints no such file. What am I doing wrong? This used to work. Transcript below. Thx Arun [cygwin$:515] net use goddard\\abiyani y: The command completed successfully. You don't need to do this since you've mounted the UNC path below but since you did, what does 'ls /cygdrive/y' say? [cygwin$:516] ls /y ls: /y: No such file or directory [cygwin$:517] mount C:\win\cygwin\bin on /usr/bin type system (binmode) C:\win\cygwin\lib on /usr/lib type system (binmode) \\goddard\abiyani on /y type system (binmode,noexec) C:\win\cygwin on / type system (binmode) c: on /c type system (binmode,noumount) i: on /i type system (binmode,noumount) s: on /s type system (binmode,noumount) [cygwin$:518] ls /y ls: /y: No such file or directory What does 'ls //goddard/abiyani' say? [cygwin$:519] mount //goddard/abiyani /y mount: /y: Device or resource busy [cygwin$:520] Right. You've mounted here already. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
XP64 can't shut down cygrunsrv services
Used cygrunsrv to install sshd, inetd and exim. Logging out and/or shutting down takes a long time unless one first stops each of these services manually (net stop ...). The net stop command shuts each service down in just monents, and then a logout/shutdown proceeds in the usual amount of time. "Looks like" the windows shutdown signal isn't reaching the services and then windows is timing each of them out. 1) $ cygrunsrv -v cygrunsrv V1.17, Jun 19 2006 2) OpenSSH_4.3p2, OpenSSL 0.9.8b 04 May 2006 TIA Art Art LazanoffNASA Ames Research Center Senior Scientific Consultant Mail Stop 258-6 [EMAIL PROTECTED] (650) 604-1687Moffett Field, CA 94035-1000 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
cygwin installation batch file?
I have used cygwin for many years and now am in a situation where I need/want to install it on 30 or so windows xp boxes. Does someone have a batch file I can adapt to my situation? I've started on one at work (no access to it at the moment) that attempts to copy setup.exe from a local mirror I've created, c:, mkdir \cygwin, cd \cygwin, copy \\host\cygwin\setup.exe, and then I get into a problem trying to get setup.exe to run. The command (at work, so I'm going from memory) I'm trying to use is 'setup.exe --download --site http://host/cygwin --no-shortcuts --no-desktop perl rsync cvs ssh cygserv'. I am following up the installation with cd bin, bash.exe --login -i -c '/usr/bin/mkpasswd --local > /etc/passwd', bash --login -i -c '/usr/bin/mkgroup --local > /etc/group', bash ... wait, this is confusing... -- c: mkdir \cygwin cd \cygwin copy \\host\cygwin\setup.exe setup --download --site http://host/cygwin --no-shortcuts \ --no-desktop perl rsync cvs ssh cygserv bash.exe --login -i -c '/usr/bin/mkpasswd --local > /etc/passwd bash.exe --login -i -c '/usr/bin/mkgroup --local > /etc/group bash.exe --login -i -c '/usr/bin/ssh-keygen' bash.exe --login -i -c '/usr/bin/ssh-host-config --yes' net start sshd -- That's what I've tried so far (from memory). Does someone have a script that does the above and works? :) Mike -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: [ANNOUNCEMENT] Updated [experimental]: bash-3.1-7
Eric Blake wrote: mwoehlke tibco.com> writes: So $HOME is being set wrong. "echo $HOME | od -c" gives " / h o m e / m w o e h l k e \r \n". "echo %HOME%" from a fresh cmd.exe gives "C:/Documents and Settings/mwoehlke". I ran d2u on /etc/profile, /etc/default/etc/profile and /etc/passwd. I can't reproduce this. Have you tried 'bash -lvx' for a verbose trace, to see if some text-mode file is being sourced very early in your edited /etc/profile which does HOME=/home/mwoehlke? The fact that Windows %HOME% is defined differently than what you want in cygwin makes it seem like you are doing something in /etc/profile to override what cygwin would normally do for $HOME. I tried 'bash -x'. Alas I stupidly did it when already in bash (hey, my non-bash shells are hard to get to! ;-)). I did finally track it down; mwoehlke/.bash_profile in c:/documents and settings was DOS-format, and was re-invoking bash -l after changing HOME. I'm not sure how *that* wound up in DOS format; must've used Notepad the one-and-only time I edited it. Sorry for the trouble. :-) POSIXLY_CORRECT = '1' <-- what is setting this, and why? That is being set by cygcheck, just before invoking external programs. It probably had something to do with forcing external programs to not rearrange option arguments (for example, "ls foo --all" treats --all as an option, but "POSIXLY_CORRECT=1 ls foo --all" treats --all as a filename). But I think it is possible to get along without doing it (repeating the example, "ls -- foo --all" treats --all as a filename), and I personally think that cygcheck should be patched to QUIT setting POSIXLY_CORRECT, so that we can tell the masochists apart from normal users. Ah, ok, so seeing it in cygcheck is a false positive. Didn't think that cygcheck would tinker with my environment (maybe it should know it is doing so and preserve the invocation value and print that?), so I didn't think to actually 'echo $POSIXLY_CORRECT'. :-) IOW I agree with your suggestion. I just got a little freaked out thinking that Cygwin had unwittingly *made* me one of said users. ;-) -- Matthew KATE: Awesome Text Editor -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: [ANNOUNCEMENT] Updated [experimental]: bash-3.1-7
mwoehlke tibco.com> writes: > >> > >> So $HOME is being set wrong. "echo $HOME | od -c" gives " / h o m > >> e / m w o e h l k e \r \n". "echo %HOME%" from a > >> fresh cmd.exe gives "C:/Documents and Settings/mwoehlke". I ran d2u on > >> /etc/profile, /etc/default/etc/profile and /etc/passwd. I can't reproduce this. Have you tried 'bash -lvx' for a verbose trace, to see if some text-mode file is being sourced very early in your edited /etc/profile which does HOME=/home/mwoehlke? The fact that Windows %HOME% is defined differently than what you want in cygwin makes it seem like you are doing something in /etc/profile to override what cygwin would normally do for $HOME. What does 'env' say HOME is when invoked from cmd.exe? I would expect it to be a POSIX-translation of %HOME%, rather than /home/mwoelke\r, and that would be confirmation that something in (or called by) /etc/profile is the culprit. Also, I would recommend "echo $HOME- | od -c", so that you can distinguish between any \r actually in $HOME and ensure that echo is not outputting in text mode to the pipe. > No... > > I ran d2u on /etc/profile, /etc/default/etc/profile and /etc/passwd. > > Besides, $HOME is colon-separated, with data after it, so even if it > does/did, it seems like something else would be going wrong if this > caused $HOME to have a '\r' on the end. According to /etc/defaults/etc/profile, in the algorithm for setting $HOME, /etc/passwd is option 2, only used if %HOME% doesn't exist in the Windows environment as option 1. > POSIXLY_CORRECT = '1' <-- what is setting this, and why? That is being set by cygcheck, just before invoking external programs. It probably had something to do with forcing external programs to not rearrange option arguments (for example, "ls foo --all" treats --all as an option, but "POSIXLY_CORRECT=1 ls foo --all" treats --all as a filename). But I think it is possible to get along without doing it (repeating the example, "ls -- foo --all" treats --all as a filename), and I personally think that cygcheck should be patched to QUIT setting POSIXLY_CORRECT, so that we can tell the masochists apart from normal users. -- Eric Blake -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: [ANNOUNCEMENT] Updated [experimental]: bash-3.1-7
Christopher Faylor wrote: On Mon, Sep 11, 2006 at 01:04:30PM -0500, mwoehlke wrote: Eric Blake wrote: NOTICE: === This version removes several outdated #defines that were once necessary in older versions of cygwin, but which made bash on cygwin different and slower than bash on Linux. In the process, there is a major change in behavior - bash no longer forces text mode when reading scripts. If your script resides on a text mount point, you will not notice any difference. If your script resides on a binary mount point, and has normal unix \n line endings, you may notice a slight speedup. But if your script resides on a binary mount point, and has \r\n line endings, bash will most likely encounter syntax errors. The fix is simple - use d2u to convert script files residing on a binary mount point to be unix files, or if you must use DOS lines, use a text mount point. Because of this change in behavior, I am marking this version experimental for a while until I can gauge from mailing list traffic that it is safe to promote to current. When starting the experimental version with "c:\cygwin\bin\bash.exe -l". I get: mkdir: cannot create directory `/home/mwoehlke\r': No such file or directory Copying skeleton files. These files are for the user to personalise their cygwin experience. These will never be overwritten. /usr/bin/install: cannot create directory `/home/mwoehlke\r': No such file or directory /usr/bin/install: cannot create directory `/home/mwoehlke\r': No such file or directory /usr/bin/install: cannot create directory `/home/mwoehlke\r': No such file or directory : No such file or directory [EMAIL PROTECTED] /etc/skel $ So $HOME is being set wrong. "echo $HOME | od -c" gives " / h o m e / m w o e h l k e \r \n". "echo %HOME%" from a fresh cmd.exe gives "C:/Documents and Settings/mwoehlke". I ran d2u on /etc/profile, /etc/default/etc/profile and /etc/passwd. If I 'export HOME=/home/mwoehlke', then things work correctly. Somehow, before /etc/profile is executed, my $HOME is being set "funny". Any guesses? Does your /etc/passwd contain \r\n line endings? No... I ran d2u on /etc/profile, /etc/default/etc/profile and /etc/passwd. Besides, $HOME is colon-separated, with data after it, so even if it does/did, it seems like something else would be going wrong if this caused $HOME to have a '\r' on the end. I don't think this is the answer, but I'm attaching a new cygcheck output just in case. -- Matthew KATE: Awesome Text Editor Cygwin Configuration Diagnostics Current System Time: Mon Sep 11 13:17:44 2006 Windows XP Professional Ver 5.1 Build 2600 Service Pack 2 Path: C:\cygwin\opt\qt\3.3\bin C:\cygwin\opt\kde3.4\bin C:\cygwin\opt\kde3.4\lib C:\cygwin\opt\kde3.4\lib\kde3 C:\cygwin\usr\local\bin C:\cygwin\bin C:\cygwin\bin C:\cygwin\usr\X11R6\bin C:\cygwin\opt\qt\3.3\bin C:\cygwin\opt\kde3.4\bin C:\cygwin\opt\kde3.4\lib C:\cygwin\opt\kde3.4\lib\kde3 C:\cygwin\usr\local\bin C:\cygwin\bin C:\cygwin\bin C:\cygwin\usr\X11R6\bin c:\mks\mksnt c:\PROGRA~1\Oracle\jre\112EBD~1.7\bin c:\WINDOWS\system32 c:\WINDOWS c:\WINDOWS\System32\Wbem c:\Dev\Perforce c:\SFU\common\ [snip] [snip] [snip] c:\Program Files\QuickTime\QTSystem\ c:\Dev\Common\Tools\WinNT c:\Dev\Common\MSDev98\Bin c:\Dev\Common\Tools c:\Dev\VC98\bin Output from C:\cygwin\bin\id.exe (nontsec) UID: 1051(mwoehlke) GID: 513(None) 0(root) 513(None) 544(Administrators) 100(Users) Output from C:\cygwin\bin\id.exe (ntsec) UID: 1051(mwoehlke) GID: 513(None) 0(root) 513(None) 544(Administrators) 100(Users) SysDir: C:\WINDOWS\system32 WinDir: C:\WINDOWS USER = 'mwoehlke' PWD = '/etc' CYGWIN = 'tty' HOME = '/home/mwoehlke ' <-- oops! MAKE_MODE = 'unix' HOMEPATH = '\Documents and Settings\mwoehlke' APPDATA = 'C:\Documents and Settings\mwoehlke\Application Data' MANPATH = '/usr/local/man:/usr/man:/usr/share/man:/usr/autotool/devel/man:/usr/local/man:/usr/man:/usr/share/man:/usr/autotool/devel/man::/usr/ssl/man:/opt/qt/3.3/doc/man:/usr/X11R6/man:/usr/ssl/man:/opt/qt/3.3/doc/man:/usr/X11R6/man' HOSTNAME = 'Harkness' PROCESSOR_IDENTIFIER = 'x86 Family 6 Model 6 Stepping 2, AuthenticAMD' SHELL = 'C:/mks/mksnt/sh.exe' <-- doesn't seem to be it, I unset this to no effect (and also fixed it, but that won't pick up until reboot) TERM = 'cygwin' WINDIR = 'C:\WINDOWS' TMPDIR = '/cygdrive/c/WINDOWS/TEMP' KDEHOME = '/opt/kde3.4/home' OLDPWD = '/etc/skel' QTDIR = '/opt/qt/3.3' USERDOMAIN = 'HARKNESS' ALLUSERSPROFILE = 'C:\Documents and Settings\All Users' OS = 'Windows_NT' COMMONPROGRAMFILES = 'C:\Program Files\Common Files' TEMP = '/cygdrive/c/DOCUME~1/mwoehlke/LOCALS~1/Temp' LIB = 'C:\Dev\VC98\mfc\lib;C:\Dev\VC98\lib' ROOT
Re: [ANNOUNCEMENT] Updated [experimental]: bash-3.1-7
On Mon, Sep 11, 2006 at 01:04:30PM -0500, mwoehlke wrote: >Eric Blake wrote: >>NOTICE: >>=== >>This version removes several outdated #defines that were once necessary in >>older versions of cygwin, but which made bash on cygwin different and >>slower than bash on Linux. In the process, there is a major change in >>behavior - bash no longer forces text mode when reading scripts. If your >>script resides on a text mount point, you will not notice any difference. >> If your script resides on a binary mount point, and has normal unix \n >>line endings, you may notice a slight speedup. But if your script resides >>on a binary mount point, and has \r\n line endings, bash will most likely >>encounter syntax errors. The fix is simple - use d2u to convert script >>files residing on a binary mount point to be unix files, or if you must >>use DOS lines, use a text mount point. Because of this change in >>behavior, I am marking this version experimental for a while until I can >>gauge from mailing list traffic that it is safe to promote to current. > >When starting the experimental version with "c:\cygwin\bin\bash.exe -l". >I get: > >mkdir: cannot create directory `/home/mwoehlke\r': No such file or directory >Copying skeleton files. >These files are for the user to personalise >their cygwin experience. >These will never be overwritten. >/usr/bin/install: cannot create directory `/home/mwoehlke\r': No such >file or directory >/usr/bin/install: cannot create directory `/home/mwoehlke\r': No such >file or directory >/usr/bin/install: cannot create directory `/home/mwoehlke\r': No such >file or directory >: No such file or directory >[EMAIL PROTECTED] /etc/skel >$ > >So $HOME is being set wrong. "echo $HOME | od -c" gives " / h o m > e / m w o e h l k e \r \n". "echo %HOME%" from a >fresh cmd.exe gives "C:/Documents and Settings/mwoehlke". I ran d2u on >/etc/profile, /etc/default/etc/profile and /etc/passwd. > >If I 'export HOME=/home/mwoehlke', then things work correctly. > >Somehow, before /etc/profile is executed, my $HOME is being set "funny". >Any guesses? Does your /etc/passwd contain \r\n line endings? cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: [ANNOUNCEMENT] Updated [experimental]: bash-3.1-7
Eric Blake wrote: NOTICE: === This version removes several outdated #defines that were once necessary in older versions of cygwin, but which made bash on cygwin different and slower than bash on Linux. In the process, there is a major change in behavior - bash no longer forces text mode when reading scripts. If your script resides on a text mount point, you will not notice any difference. If your script resides on a binary mount point, and has normal unix \n line endings, you may notice a slight speedup. But if your script resides on a binary mount point, and has \r\n line endings, bash will most likely encounter syntax errors. The fix is simple - use d2u to convert script files residing on a binary mount point to be unix files, or if you must use DOS lines, use a text mount point. Because of this change in behavior, I am marking this version experimental for a while until I can gauge from mailing list traffic that it is safe to promote to current. When starting the experimental version with "c:\cygwin\bin\bash.exe -l". I get: mkdir: cannot create directory `/home/mwoehlke\r': No such file or directory Copying skeleton files. These files are for the user to personalise their cygwin experience. These will never be overwritten. /usr/bin/install: cannot create directory `/home/mwoehlke\r': No such file or directory /usr/bin/install: cannot create directory `/home/mwoehlke\r': No such file or directory /usr/bin/install: cannot create directory `/home/mwoehlke\r': No such file or directory : No such file or directory [EMAIL PROTECTED] /etc/skel $ So $HOME is being set wrong. "echo $HOME | od -c" gives " / h o m e / m w o e h l k e \r \n". "echo %HOME%" from a fresh cmd.exe gives "C:/Documents and Settings/mwoehlke". I ran d2u on /etc/profile, /etc/default/etc/profile and /etc/passwd. If I 'export HOME=/home/mwoehlke', then things work correctly. Somehow, before /etc/profile is executed, my $HOME is being set "funny". Any guesses? -- Matthew KATE: Awesome Text Editor -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Potential bug in sshd
Sorry about the double-post everyone. Because I sent the first email from a non list-registered address and assumed it wouldn't get through, I resent it from the address that I actually registered with Sorry, Mike On 9/11/06, Christopher Faylor <[EMAIL PROTECTED]> wrote: Please don't send the same message twice. On Mon, Sep 11, 2006 at 11:39:53AM -0400, Michael Sowka wrote: >... just when I thought I was nicely settled with WinXP and Cygwin >(being obligated to use Windows, cygwin makes the experience more >bearable ;) )... > >I don't consider myself a newbie, but we'll soon find out. I've >installed cygwin on a number of computers I frequently 'ssh'/'scp' >to/from. The setup is straight forward (time saving guide here: >http://pigtail.net/LRP/printsrv/cygwin-sshd.html). Other than the time >when I tried to change user groups manually and had to revert back to >get sshd working again, things have been running smooth. >[snip] >Problem reports: http://cygwin.com/problems.html If you are having problems with the instructions you found at a web site you should contact the person responsible for the instructions: nfong AT pigtail DOT net. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Potential bug in sshd
Please don't send the same message twice. On Mon, Sep 11, 2006 at 11:39:53AM -0400, Michael Sowka wrote: >... just when I thought I was nicely settled with WinXP and Cygwin >(being obligated to use Windows, cygwin makes the experience more >bearable ;) )... > >I don't consider myself a newbie, but we'll soon find out. I've >installed cygwin on a number of computers I frequently 'ssh'/'scp' >to/from. The setup is straight forward (time saving guide here: >http://pigtail.net/LRP/printsrv/cygwin-sshd.html). Other than the time >when I tried to change user groups manually and had to revert back to >get sshd working again, things have been running smooth. >[snip] >Problem reports: http://cygwin.com/problems.html If you are having problems with the instructions you found at a web site you should contact the person responsible for the instructions: nfong AT pigtail DOT net. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Resource Temporarily Unavailable
Chris McIntosh wrote: Hello, I work at a company where we have a complicated Linux build. We use cygwin to mimic this build on windows for some of our windows centric people. At different times when cygwin forks it will throw a Resource temporarily Unavailble error. I am tempted to call this "Random" because it doesn't manifest itself until a random time, but once manifested it will continue to fail at the exact same spot. This spot is different for all users but once it does happen it continues to fail. This is typically in our make flow when it is forking or spawning another process to execute a command. Here is a snip ../../../../..//class/mfs/engine/disp/gf100_engine.mfs /usr/bin/env: ../../../../..//bin/Win32/cfp: Resource temporarily unavailable makepp: Failed to build target gf100.xml One thing to note, the command that it fails on is different for all users. It actually fails when forking. Another example is /usr/bin/bash: fork: Resource temporarily unavailable make[4]: *** [ObjWin32/.PTreeVisitor.d] Error 128 After looking at the cygwin source I found that EAGAIN which produces this message is mapped to many windows errors. So after more investigation I found it to be Win32 error 234 which is ERROR_MORE_DATA. I then traced this down to when cygwin calls CreateProcessAsUser in spawn.cc So my question, has anyone seen this before. I don't think it is a cygwin bug since it the win api returning this error, but maybe it is something to do with the call. Any pointers or tips would be helpful. Hi all, I also have this problem. I use xfce as my desktop and window manager and after a totally arbitrary amount of time (sometimes 10 mins, sometimes days) I start getting this error "Failed to fork (Resource temporarily unavailable)" from the xfce4-panel and it refuses to launch anything. Xfdesktop usually goes shortly after as well. I also noticed by the time this starts happening the process stops showing up when I do a "ps -ef", It doesn't even show up when I pass it a -W either, I have to kill it from Task Manager and start a new one. About this time I also start repeatedly getting this exact error as well: http://www.cygwin.com/ml/cygwin/2006-07/msg00239.html when I build my companies tool in cygwin (with make-3.80). I've reinstalled cygwin several times, tried doing a rebaseall, tried changing the heap size, and none of that made any difference for me. (Have not tried the new dll posted in this thread but it was reported that did not solve his problem). I tried downgrading bash from 3.1-6 to 3.0-14 and it seemed like it had fixed both problems but then a week later it returned. I tried setting "CYGWIN=error_start=c:\cygwin\bin\gdb.exe codepage:oem" and verifyed it worked but it does not catch the sh.exe crash. I use the xfce4 ports from: http://www.amazepc.com/bamanzi/cygwin/xfce4/ (several versions, it happened with all of them) and have also tried the pkgs in ftp://sunsite.dk/projects/cygwinports. I had everything working perfectly for over a year with the xfce ports mentioned, then something happened to my cygwin install in a power outage so I did a clean reinstall. Ever since I have had all these nightmare problems. Any suggestions for what to try/check/install/log/debug would be greatly appreciated. Thanks, Nick -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Potential sshd bug
Hello, ... just when I thought I was nicely settled with WinXP and Cygwin (being obligated to use Windows, cygwin makes the experience more bearable ;) )... I don't consider myself a newbie, but we'll soon find out. I've installed cygwin on a number of computers I frequently 'ssh'/'scp' to/from. The setup is straight forward (time saving guide here: http://pigtail.net/LRP/printsrv/cygwin-sshd.html). Other than the time when I tried to change user groups manually and had to revert back to get sshd working again, things have been running smooth. Until, today my work desktop decided to spontaneously stop serving me ssh. Symptoms on the client side (putty from/to localhost, eliminating network problems) vary: - "Server unexpectedly closed network connection" - or simply times out (also note, it's not he windows firewall, necessary exception is there ;) ) When I 'net stop sshd' it stops "successfully" but then starting again fails. On inspecting Task Manager I find that sshd is still running :|. Ending the process, starting sshd service again has no effect. I have gone as far as cleaning out cygwin from my system, completely following the guide in the FAQ, and reinstalling to no effect. This makes me think that there must be some glitch/registry setting/new software I installed that's triggering some fault in cygwin/sshd. I have the latest cygwin, but here are the obligatory version numbers: cygwin : 1.5.21-2 openssh 4.3p2-3 Please tell me where to pull logs / debugging output from and I will send them your way. Thanks, Mike -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Potential bug in sshd
Hello, ... just when I thought I was nicely settled with WinXP and Cygwin (being obligated to use Windows, cygwin makes the experience more bearable ;) )... I don't consider myself a newbie, but we'll soon find out. I've installed cygwin on a number of computers I frequently 'ssh'/'scp' to/from. The setup is straight forward (time saving guide here: http://pigtail.net/LRP/printsrv/cygwin-sshd.html). Other than the time when I tried to change user groups manually and had to revert back to get sshd working again, things have been running smooth. Until, today my work desktop decided to spontaneously stop serving me ssh. Symptoms on the client side (putty from/to localhost, eliminating network problems) vary: - "Server unexpectedly closed network connection" - or simply times out When I 'net stop sshd' it stops "successfully" but then starting again fails. On inspecting Task Manager I find that sshd is still running :|. Ending the process, starting sshd service again has no effect. I have gone as far as cleaning out cygwin from my system, completely following the guide in the FAQ, and reinstalling to no effect. This makes me think that there must be some glitch/registry setting/new software I installed that's triggering some fault in cygwin/sshd. I have the latest cygwin, but here are the obligatory version numbers: cygwin : 1.5.21-2 openssh 4.3p2-3 Please tell me where to pull logs / debugging output from and I will send them your way. Thanks, Mike -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: setup.exe -> BSOD
On Mon, Sep 11, 2006 at 02:56:01PM +0100, Dave Korn wrote: > Googling "w22n51.sys" shows millions of hits about how it crashes all the > time. > > Try disabling your "Intel PRO/Wireless 2200 LAN Adapters" wireless network > card. And that did it. Thank you, gentlemen! John Smith -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: problem starting crontab services
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Pierre A. Humblet > Sent: Monday, September 11, 2006 9:55 AM > To: cygwin@cygwin.com > Cc: Jon Barber > Subject: Re: problem starting crontab services > > > > From: "Larry Hall (Cygwin)" > > To: cygwin > > Sent: Friday, September 08, 2006 10:27 PM > > Subject: Re: problem starting crontab services > > >> On 09/08/2006, Jon Barber wrote: > >> hello cygwin gurus > >> > >> i can't get crontab services to start. i just followed > the instruction > >> from running cron_diagnose.sh version 1.5, and there were > a number of > >> things it reported wrong that i tried to fix. the final > problem is when i > >> try to start cron, i get the following error: ... > > > Let me point out again that cron_diagnose does not handle W2K3 at all > and that cron-config should be used instead. > Much of the cron related traffic to this list is due to > misguided attempts > to use cron_diagnose. > > Pierre > Also, do not "download" cron_diagnose.sh separately. It is included in the cygwin distribution of 'cron' (/usr/bin/cron_diagnose.sh). Version 1.5 of the script is out of date. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: setup.exe -> BSOD
* John Smith (2006-09-11 13:49 +0100) > Having successfully installed Cygwin on my desktop machine (XP Home, > SP2, fully patched), I wanted to install it on my laptop (XP Pro, SP2, > fully patched). I downloaded the current setup.exe and ran it, > accepting the default values till I came to the "choice of mirror" > screen. I chose my mirror, and clicked on "Next". The machine showed > me a split-second Blue Screen of Death, then rebooted. Three repeated > attempts brought exactly the same result. > > I fully realise that I am not providing enough information for anyone > to solve my problem, but I do not know what else might be useful. I am > happy to supply whatever info might help. For now, I am definitively > stuck. Try disabling Antivirus -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Need Volunteers to test patch for gnu make
It works like a charm: C:\usr\local\cell\samples\fw>set CELL_SDK=C:\usr\local\cell C:\usr\local\cell\samples\fw>which make /usr/bin/make C:\usr\local\cell\samples\fw>make > stdout.txt C:\usr\local\cell\host-win32\ppu\bin\ppu-lv2-ar.exe: creating libfw.a Greetings, Olivier Langlois http://www.olivierlanglois.net > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf > Of Christopher Faylor > Sent: September 8, 2006 6:04 PM > To: cygwin@cygwin.com > Subject: Re: Need Volunteers to test patch for gnu make > > On Fri, Sep 08, 2006 at 03:34:58PM -0400, William A. Hoffman wrote: > >At 12:38 PM 9/8/2006, William A. Hoffman wrote: > >>Thanks Bob. OK, so that is three people that have tested this patch. > >>Please try the patch if you use make. DOS paths will be on by DEFAULT > >>and there will be no way to turn it off. We want to make sure this > >>does not break any POSIX based makefiles. > > > >Since folks seem to be adverse to building from source, I have made the > >patched make.exe available here: > > > >http://www.cmake.org/files/cygwin/make.exe > > > >Please try it, and report any problems on this list. > > To be clear: the only way this will *ever* show up in a Cygwin make > release is if I am satisfied that all of the people who complained about > this issue will not still be complaining after I make a new release. > > So anyone who previously expressed reservations about the current make > behavior should should try the binary that William has graciously made > available and report back here. > > And, no, I'm not going to produce a test release of make with this > change. Sending email is about the limit of the effort that I'm willing > to go to for this issue. > > cgf > > -- > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > Problem reports: http://cygwin.com/problems.html > Documentation: http://cygwin.com/docs.html > FAQ: http://cygwin.com/faq/ make --no-print-directory -f fw.mk C:\usr\local\cell/host-win32/ppu/bin/ppu-lv2-g++ -c -g -O2 -std=c++98 -fno-exceptions -W -Wall -Wuninitialized -Wcomment -Wchar-subscripts -Wdeprecated-declarations -Wendif-labels -Wformat=2 -Wformat-extra-args -Wimplicit -Wimport -Winline -Wmissing-braces -Wparentheses -Wpointer-arith -Wredundant-decls -Wreturn-type -Wshadow -Wsign-compare -Wswitch -Wunknown-pragmas -Wunused -Wwrite-strings -Iinclude -DPSGL -D_DEBUG -DCELL_DISPLAY_MODE=DisplayMode_720p -DCELL_DATA_DIR=\"usrlocalcell/sample_data\" -Wp,-MMD,objs/src/FWApplication.ppu.d,-MT,objs/src/FWApplication.ppu.o -o objs/src/FWApplication.ppu.o src/FWApplication.cpp C:\usr\local\cell/host-win32/ppu/bin/ppu-lv2-g++ -c -g -O2 -std=c++98 -fno-exceptions -W -Wall -Wuninitialized -Wcomment -Wchar-subscripts -Wdeprecated-declarations -Wendif-labels -Wformat=2 -Wformat-extra-args -Wimplicit -Wimport -Winline -Wmissing-braces -Wparentheses -Wpointer-arith -Wredundant-decls -Wreturn-type -Wshadow -Wsign-compare -Wswitch -Wunknown-pragmas -Wunused -Wwrite-strings -Iinclude -DPSGL -D_DEBUG -DCELL_DISPLAY_MODE=DisplayMode_720p -DCELL_DATA_DIR=\"usrlocalcell/sample_data\" -Wp,-MMD,objs/src/FWCamera.ppu.d,-MT,objs/src/FWCamera.ppu.o -o objs/src/FWCamera.ppu.o src/FWCamera.cpp C:\usr\local\cell/host-win32/ppu/bin/ppu-lv2-g++ -c -g -O2 -std=c++98 -fno-exceptions -W -Wall -Wuninitialized -Wcomment -Wchar-subscripts -Wdeprecated-declarations -Wendif-labels -Wformat=2 -Wformat-extra-args -Wimplicit -Wimport -Winline -Wmissing-braces -Wparentheses -Wpointer-arith -Wredundant-decls -Wreturn-type -Wshadow -Wsign-compare -Wswitch -Wunknown-pragmas -Wunused -Wwrite-strings -Iinclude -DPSGL -D_DEBUG -DCELL_DISPLAY_MODE=DisplayMode_720p -DCELL_DATA_DIR=\"usrlocalcell/sample_data\" -Wp,-MMD,objs/src/FWDebugConsole.ppu.d,-MT,objs/src/FWDebugConsole.ppu.o -o objs/src/FWDebugConsole.ppu.o src/FWDebugConsole.cpp C:\usr\local\cell/host-win32/ppu/bin/ppu-lv2-g++ -c -g -O2 -std=c++98 -fno-exceptions -W -Wall -Wuninitialized -Wcomment -Wchar-subscripts -Wdeprecated-declarations -Wendif-labels -Wformat=2 -Wformat-extra-args -Wimplicit -Wimport -Winline -Wmissing-braces -Wparentheses -Wpointer-arith -Wredundant-decls -Wreturn-type -Wshadow -Wsign-compare -Wswitch -Wunknown-pragmas -Wunused -Wwrite-strings -Iinclude -DPSGL -D_DEBUG -DCELL_DISPLAY_MODE=DisplayMode_720p -DCELL_DATA_DIR=\"usrlocalcell/sample_data\" -Wp,-MMD,objs/src/FWDebugFont.ppu.d,-MT,objs/src/FWDebugFont.ppu.o -o objs/src/FWDebugFont.ppu.o src/FWDebugFont.cpp C:\usr\local\cell/host-win32/ppu/bin/ppu-lv2-g++ -c -g -O2 -std=c++98 -fno-exceptions -W -Wall -Wuninitialized -Wcomment -Wchar-subscripts -Wdeprecated-declarations -Wendif-labels -Wformat=2 -Wformat-extra-args -Wimplicit -Wimport -Winline -Wmissing-braces -Wparentheses -Wpointer-arith -Wredundant-decls -Wreturn-type -Wshadow -Wsign-compare -Wswitch -Wunknown-pragmas -Wunused -Wwrite-strings -Iinclude -DPSGL -D_DEBUG -DCELL_DISPLAY_MODE=
RE: port forwarding, and routing.
On 11 September 2006 15:13, Robin-David Hammond %KB3IEN wrote: > Two problems : One problem: none of this has anything to do with cygwin. cheers, DaveK -- Can't think of a witty .sigline today -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
port forwarding, and routing.
Two problems : 1: I'm working on ms windows XP, I would like to forward localhost ports tcp 137-139 over ssh. THis is a trivial issue on some installs of windows, it works fine using putty, in other cases it does not. Has anyone had this experience before? I have even resorted to creating a virtual adapter with a reserved IP address, and forwarding both 0.0.0.0:137 and 5.0.0.1:137 to 192.168.1.250:137 neither works! add ing forwarding for port 22 using the exact same techniques works fine! I get an sshd handshake, so this seems to be a windows kernel issue. Extensive debugging on the remote (ssh) host confirms that no traffic for port 137 is forwarded. 2: my IP network is a CIDR /24 with the router on 192.168.102.0 windows cannot access IP addresses at the bottom of the subnet as unicast. two solutions seem to exist: make windows think the network a /22 and leave the router alone, move the router. Is there a patch to enable windows kernel to see .0 as a unicast ip? Both solaris and bsd seem to have this feature available, but off be default. I wonder how much of the bsd ip stack MS successfuly 'borrowed'. thanks all, Robin-David Hammond KB3IEN -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: problem starting crontab services
From: "Larry Hall (Cygwin)" To: cygwin Sent: Friday, September 08, 2006 10:27 PM Subject: Re: problem starting crontab services On 09/08/2006, Jon Barber wrote: hello cygwin gurus i can't get crontab services to start. i just followed the instruction from running cron_diagnose.sh version 1.5, and there were a number of things it reported wrong that i tried to fix. the final problem is when i try to start cron, i get the following error: $ cygrunsrv --start cron cygrunsrv: Error starting a service: QueryServiceStatus: Win32 error 1062: The service has not been started. attached is the output of 'cygcheck -srv > cygcheck.txt' any help very much appreciated jon barber my entire log of steps i tried is this: following the instructions here: http://sources.redhat.com/ml/cygwin/2004-03/msg00379.html, which involves successively running a diagnostic script to find config errors * i downloaded and ran the cron_diagnose.sh script * it first reported the following The permissions on the file /etc/passwd are not correct. Please run 'chmod +r /etc/passwd', and run this script again. * when i looked in /etc, i saw that many of the files were owned by "thadmin", which was the administrative account we originally used to setup the machine. * so i chown'ed most of those files to Administrator, and chmod'ed them +r, and ran the script again.* it still complained that /etc/passwd had incorrect permissions - turns out /etc/passwd is "-rwxr-xr--+", so i modified the script to accept the + sign in hopes that doesn't matter * it then reported the following The permissions on the file /etc/group are not correct. Please run 'chmod +r /etc/group', and run this script again. * so i chmod'ed it +r, and ran the script again.* it then reported the following The group membership of your crontab file should be SYSTEM, as documented in the file /usr/share/doc/Cygwin/cron.README. You can change this setting with: chgrp SYSTEM /var/cron/tabs/Administrator Please check your crontab's group membership, and run this script again. I wouldn't recommend this procedure. Better to run getfacl/setfacl to solve the problem of the extra permissions access. You're also using W2K3. The LocalSystem (SYSTEM) account on W2K3 doesn't have the permissions necessary to switch user contexts, which is necessary to run cron in the traditional way. Since you've already configured and installed OpenSSH, you can use the sshd_server as the user account for the cron service as well. sshd_server has the necessary permissions to switch user contexts. Doing this though will likely mean that the files you changed to be owned by SYSTEM need to have their ownerships changed to sshd_server. Rerunning cron_diagnose will likely catch other files that need to have the ownership changed. But use sshd_server in place of SYSTEM. You may want to update your cygwin package as well. This may not be enough to solve all your problems but it's not obvious to me where other problems may be but this should be a start. Let me point out again that cron_diagnose does not handle W2K3 at all and that cron-config should be used instead. Much of the cron related traffic to this list is due to misguided attempts to use cron_diagnose. Pierre -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: setup.exe -> BSOD
On 11 September 2006 14:47, John Smith wrote: > > This identifies the problem as DRIVER_IRQL_NOT_LESS_OR_EQUAL, and > cites the following technical info: > > *** STOP: 0X00D1 (0X8240, 0X0002, 0X, 0XF80B4988) > > *** w22n51.sys - Address F80B4988 base at F804, Datestamp 404c5c4c Googling "w22n51.sys" shows millions of hits about how it crashes all the time. Try disabling your "Intel PRO/Wireless 2200 LAN Adapters" wireless network card. cheers, DaveK -- Can't think of a witty .sigline today -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: setup.exe -> BSOD
On Mon, Sep 11, 2006 at 02:46:40PM +0100, John Smith wrote: >On Mon, Sep 11, 2006 at 09:17:26AM -0400, Larry Hall (Cygwin) wrote: >>BSOD situations point to a problem with the O/S kernel, not the app >>that may be running at the time they occur. Problematic drivers are >>the most common causes here. I'd recommend un-installing any recent >>additions made in this area and see if it helps. > >Difficult to guess what might be at fault. First guess (NX client) >made no difference. > >>On the flip side, if you'd like to get a better look at the BSOD, you >>can turn off the automatic reboot using the "System" applet in your >>control panel. > >This identifies the problem as DRIVER_IRQL_NOT_LESS_OR_EQUAL, and cites >the following technical info: > >*** STOP: 0X00D1 (0X8240, 0X0002, 0X, 0XF80B4988) > >*** w22n51.sys - Address F80B4988 base at F804, Datestamp 404c5c4c google would seem to be pretty instructive here. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: setup.exe -> BSOD
On 11 September 2006 13:49, John Smith wrote: > Having successfully installed Cygwin on my desktop machine (XP Home, > SP2, fully patched), I wanted to install it on my laptop (XP Pro, SP2, > fully patched). I downloaded the current setup.exe and ran it, > accepting the default values till I came to the "choice of mirror" > screen. I chose my mirror, and clicked on "Next". The machine showed > me a split-second Blue Screen of Death, then rebooted. Three repeated > attempts brought exactly the same result. Most likely your software firewall is buggy. Second most likely, your antivirus. cheers, DaveK -- Can't think of a witty .sigline today -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: setup.exe -> BSOD
On Mon, Sep 11, 2006 at 09:17:26AM -0400, Larry Hall (Cygwin) wrote: > BSOD situations point to a problem with the O/S kernel, not the app that > may be running at the time they occur. Problematic drivers are the most > common causes here. I'd recommend un-installing any recent additions made > in this area and see if it helps. Difficult to guess what might be at fault. First guess (NX client) made no difference. > On the flip side, if you'd like to get > a better look at the BSOD, you can turn off the automatic reboot using > the "System" applet in your control panel. This identifies the problem as DRIVER_IRQL_NOT_LESS_OR_EQUAL, and cites the following technical info: *** STOP: 0X00D1 (0X8240, 0X0002, 0X, 0XF80B4988) *** w22n51.sys - Address F80B4988 base at F804, Datestamp 404c5c4c John Smith -- Dr J. D. Smith * [EMAIL PROTECTED] Faculty of Oriental Studies * http://bombay.indology.info Sidgwick Avenue * Tel. +44 (0)1223 335140 Cambridge CB3 9DA* Fax +44 (0)1223 335110 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: setup.exe -> BSOD
On Mon, Sep 11, 2006 at 08:54:46AM -0400, Buchbinder, Barry (NIH/NIAID) [E] wrote: > Tried re-downloading setup.exe? Maybe it got corrupted. Tried that -- made no difference. > You might also try a setup snapshot. http://cygwin.com/setup/snapshots/ There are two available. 2.551 does exactly the same as the regular download. 2.529 stops responding just as I am due to enter the mirror list, and has to be killed via Ctrl-Alt-Del. John Smith -- Dr J. D. Smith * [EMAIL PROTECTED] Faculty of Oriental Studies * http://bombay.indology.info Sidgwick Avenue * Tel. +44 (0)1223 335140 Cambridge CB3 9DA* Fax +44 (0)1223 335110 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: setup.exe -> BSOD
John Smith wrote: Having successfully installed Cygwin on my desktop machine (XP Home, SP2, fully patched), I wanted to install it on my laptop (XP Pro, SP2, fully patched). I downloaded the current setup.exe and ran it, accepting the default values till I came to the "choice of mirror" screen. I chose my mirror, and clicked on "Next". The machine showed me a split-second Blue Screen of Death, then rebooted. Three repeated attempts brought exactly the same result. I fully realise that I am not providing enough information for anyone to solve my problem, but I do not know what else might be useful. I am happy to supply whatever info might help. For now, I am definitively stuck. BSOD situations point to a problem with the O/S kernel, not the app that may be running at the time they occur. Problematic drivers are the most common causes here. I'd recommend un-installing any recent additions made in this area and see if it helps. On the flip side, if you'd like to get a better look at the BSOD, you can turn off the automatic reboot using the "System" applet in your control panel. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: setup.exe -> BSOD
John Smith wrote: > Having successfully installed Cygwin on my desktop machine (XP Home, > SP2, fully patched), I wanted to install it on my laptop (XP Pro, > SP2, fully patched). I downloaded the current setup.exe and ran it, > accepting the default values till I came to the "choice of mirror" > screen. I chose my mirror, and clicked on "Next". The machine showed > me a split-second Blue Screen of Death, then rebooted. Three repeated > attempts brought exactly the same result. > > I fully realise that I am not providing enough information for anyone > to solve my problem, but I do not know what else might be useful. I > am happy to supply whatever info might help. For now, I am > definitively stuck. > > John Smith Tried re-downloading setup.exe? Maybe it got corrupted. You might also try a setup snapshot. http://cygwin.com/setup/snapshots/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
setup.exe -> BSOD
Having successfully installed Cygwin on my desktop machine (XP Home, SP2, fully patched), I wanted to install it on my laptop (XP Pro, SP2, fully patched). I downloaded the current setup.exe and ran it, accepting the default values till I came to the "choice of mirror" screen. I chose my mirror, and clicked on "Next". The machine showed me a split-second Blue Screen of Death, then rebooted. Three repeated attempts brought exactly the same result. I fully realise that I am not providing enough information for anyone to solve my problem, but I do not know what else might be useful. I am happy to supply whatever info might help. For now, I am definitively stuck. John Smith -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: "cannot open display"
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ogogon !!! wrote: > Good afternoon, colleagues! > > I have established CygWin to compile under Windows the program > developed in gcc. At compilation of console applications - all OK. > All applications, even rather complex, are started and work without > remarks. > > However, any attempt to create the program with GTK+, leads to that > at their start there is a message "Gtk-WARNING **: cannot open > display:". At distribution kit CygWin there is a program > gtk-demo.exe. Obviously, it it is guaranteed it is compiled without > mistakes. It is not started and also writes "Gtk-WARNING **: cannot > open display:". > > My OS - WindowsXP Pro (Rus). What do I do incorrectly? > > Yours faithfully, Ogogon. > > > -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > Problem reports: http://cygwin.com/problems.html > Documentation: http://cygwin.com/docs.html FAQ: > http://cygwin.com/faq/ > > Hi, is the EnvVariable "DISPLAY" set to the right display, e.g. "127.0.0.1:0.0" AND is some sort of XServer running? Jens - -- Dipl. Inform. Jens Wilken Software Developer OSC Embedded Systems AG Industriestr. 11 26121 Oldenburg - Germany Mail: [EMAIL PROTECTED] Tel.: +49-441-350 42-0 Fax.: +49-441-350 42-364 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFBVpB/nbz2tIAgUQRAlvsAJ4ixXxSDjuZfLvNuvLgZyWQXWb9WgCgky+7 4HGnZKC6I8wg2m2vnBMDLug= =S/1t -END PGP SIGNATURE- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: downgrading make version
If you are interested in downgrading to get dos driver letter specification to work. (i.e. c:/foo/bar.) Please try the patched version of make 3.81. http://www.cmake.org/files/cygwin/make.exe Please report back to this list if you have any issues with this version of make. -Bill At 02:21 PM 9/10/2006, Amit Partani wrote: >Hi, >The make version installed in my cygwin is GNU make 3.81. Can someone tell me >how can I downgrade it to GNU make 3.80. > >Thanks, >Amit > > > >-- >Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple >Problem reports: http://cygwin.com/problems.html >Documentation: http://cygwin.com/docs.html >FAQ: http://cygwin.com/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
