Packages keep being installed again
A few packages keep showing up in my setup for installation and are installed again every time even though they have been installed already; currently it's: glib lapack -- Thomas
Weird %SystemDrive% directories
On my home machine, setup keeps creating subdirectory trees when installing certain packages, like: /E/cygwin/%SystemDrive%/Dokumente und Einstellungen/towo/Anwendungsdaten/Microsoft/SystemCertificates/My/Certificates /E/cygwin/%SystemDrive%/Dokumente und Einstellungen/towo/Anwendungsdaten/Microsoft/SystemCertificates/My/CRLs /E/cygwin/%SystemDrive%/Dokumente und Einstellungen/towo/Anwendungsdaten/Microsoft/SystemCertificates/My/CTLs (I had mentioned this before in a side note, http://www.cygwin.com/ml/cygwin-apps/2009-11/msg00041.html, but didn't follow up so far because it's not really harmful.) By the names, my guess was it's somehow related to access rights handling, maybe ACLs. This is on a FAT drive (USB-connected) on Windows XP home. I have now noticed that there are a few more directory trees of the same name and structure, in: /lib (i.e. /E/cygwin/lib) /bin /usr/share/terminfo/* (in every subdirectory) /... (one more, don't remember) and this seems to correlate with those directories in which chmod is applied to some files during postinstall. Does that give a clue on the cause? -- Thomas
Re: ITP: arj 3.10.22
On Jan 14 17:53, Jari Aalto wrote: Corinna Vinschen corinna-cyg...@cygwin.com writes: Packaging looks basically ok, but the executables in /usr/bin are missing the .exe suffix. Fixed: wget \ http://cante.net/~jaalto/tmp/cygwin/arj/arj-3.10.22-1-src.tar.bz2 \ http://cante.net/~jaalto/tmp/cygwin/arj/arj-3.10.22-1.tar.bz2 \ http://cante.net/~jaalto/tmp/cygwin/arj/setup.hint I'm getting a 404 not found message on all of these files. Small fix on the server, should be there now. Looks good, uploaded. Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
RE: Packages keep being installed again
Thomas Wolff sent the following at Friday, January 15, 2010 4:55 AM A few packages keep showing up in my setup for installation and are installed again every time even though they have been installed already; currently it's: glib lapack I also get tetex
RFU: stgit-0.15-1
New upstream release: wget \ http://cante.net/~jaalto/tmp/cygwin/stgit/setup.hint \ http://cante.net/~jaalto/tmp/cygwin/stgit/stgit-0.15-1-src.tar.bz2 \ http://cante.net/~jaalto/tmp/cygwin/stgit/stgit-0.15-1.tar.bz2 jari
Re: RFU: stgit-0.15-1
On Jan 15 23:13, Jari Aalto wrote: wget \ http://cante.net/~jaalto/tmp/cygwin/stgit/setup.hint \ http://cante.net/~jaalto/tmp/cygwin/stgit/stgit-0.15-1-src.tar.bz2 \ http://cante.net/~jaalto/tmp/cygwin/stgit/stgit-0.15-1.tar.bz2 Uploaded. Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: Cygwin 1.7.x upgrade: Xterm history messes up prompt
I discovered that the problem is specific to my PS1 settings, but a bug
nevertheless. The prompt I've used for years is:
PS1='\[\033]0;\w\007\033[32m\][\h]: \[\033[33m ${PWD##*/}\033[0m\] '
This shows [current machine] : current folder where the current machine
is greenish and the current folder is yellowish. Something about the latest
version doesn't like the special characters that produce the colors anymore
... at least how I have them specified.
--
View this message in context:
http://old.nabble.com/Cygwin-1.7.x-upgrade%3A-Xterm-history-messes-up-prompt-tp27163806p27180596.html
Sent from the cygwin-xfree mailing list archive at Nabble.com.
--
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/
can or can't startx
I already follow Jerry Lowry's suggestion delete the whold cygwin folder and reloand the cygwin at a newsite http://cygwin.lowprofilelinks.com but it did not have cygwin-x folder and startx still nobt work -- Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.7.3.0 (10703000) Build Date: 2009-12-22 Contact: cygwin-xfree@cygwin.com XWin was started with the following command line: /usr/bin/X :0 -auth /home/DELL/.serverauth.1704 ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1920 h 1200 winInitializeDefaultScreens - Returning 2010-01-14 17:02:06 _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6 2010-01-14 17:02:06 _XSERVTransOpen: transport open failed for inet6/delluser:0 2010-01-14 17:02:06 _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6 2010-01-14 17:02:06 winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 2010-01-14 17:02:06 (II) xorg.conf is not supported 2010-01-14 17:02:06 (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information 2010-01-14 17:02:06 winPrefsLoadPreferences: /etc/X11/system.XWinrc 2010-01-14 17:02:06 LoadPreferences: Done parsing the configuration file... 2010-01-14 17:02:06 winGetDisplay: DISPLAY=:0.0 2010-01-14 17:02:06 winDetectSupportedEngines - Windows NT/2000/XP 2010-01-14 17:02:06 winDetectSupportedEngines - DirectDraw installed 2010-01-14 17:02:06 winDetectSupportedEngines - DirectDraw4 installed 2010-01-14 17:02:06 winDetectSupportedEngines - Returning, supported engines 0007 2010-01-14 17:02:06 winSetEngine - Using Shadow DirectDraw NonLocking 2010-01-14 17:02:06 winAdjustVideoModeShadowDDNL - Using Windows display depth of 32 bits per pixel 2010-01-14 17:02:07 winFinishScreenInitFB - Masks: 00ff ff00 00ff 2010-01-14 17:02:07 Screen 0 added at XINERAMA coordinate (0,0). 2010-01-14 17:02:07 MIT-SHM extension disabled due to lack of kernel support 2010-01-14 17:02:07 XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel 2010-01-14 17:02:07 (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so 2010-01-14 17:02:07 (II) GLX: Initialized DRISWRAST GL provider for screen 0 2010-01-14 17:02:07 [dix] Could not init font path element /usr/share/fonts/TTF/, removing from list! 2010-01-14 17:02:07 [dix] Could not init font path element /usr/share/fonts/OTF/, removing from list! 2010-01-14 17:02:07 [dix] Could not init font path element /usr/share/fonts/Type1/, removing from list! 2010-01-14 17:02:07 (EE) XKB: Could not invoke xkbcomp 2010-01-14 17:02:07 (EE) XKB: Couldn't compile keymap 2010-01-14 17:02:07 XKB: Failed to compile keymap 2010-01-14 17:02:07 Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config. 2010-01-14 17:02:07 Fatal server error: 2010-01-14 17:02:07 Failed to activate core devices. please help, Eric -- 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: Cygwin 1.7.x upgrade: Xterm history messes up prompt
2010/1/15 Derek Greer:
I discovered that the problem is specific to my PS1 settings, but a bug
nevertheless. The prompt I've used for years is:
PS1='\[\033]0;\w\007\033[32m\][\h]: \[\033[33m ${PWD##*/}\033[0m\] '
Only non-printing must be enclosed in \[ ... \] , but you've got
${PWD##*/} in there as well. As a consequence, readline thinks the
prompt is shorter than it actually is.
Andy
--
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/
Cygwin 1.7 xterm
After my last install of 1.7 software the X server does start and the blank X windows do go away. But when I start an Xterm the blank X windows stay around. Anyway to start Xterm with them going away once started. Also, the Xterm that starts looks like a version from back in the 80's. Has Main Options, VT Options, VT Fonts accross the top. Any way to change this back to what I was running under 1.5? thanks -- --- Jerold Lowry IT Manager / Software Engineer Engineering Design Team (EDT), Inc. a HEICO company 1400 NW Compton Drive, Suite 315 Beaverton, Oregon 97006 (U.S.A.) Phone: 503-690-1234 / 800-435-4320 Fax: 503-690-1243 Web: _www.edt.com http://www.edt.com/_ -- 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: Cygwin 1.7 xterm
On Fri, 15 Jan 2010, Jerry Lowry wrote: After my last install of 1.7 software the X server does start and the blank X windows do go away. But when I start an Xterm the blank X windows stay around. Anyway to start Xterm with them going away once started. Also, the Xterm that starts looks like a version from back in the 80's. Has Main Options, VT Options, VT Fonts accross the top. Any way to change this back to what I was running under 1.5? man xterm (command-line options) +tb This option indicates that xterm should not set up a toolbar. (resources) toolBar (class ToolBar) Specifies whether or not the toolbar should be displayed. The default is true. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- 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: Cygwin 1.7 xterm
On Fri, 15 Jan 2010, Jerry Lowry wrote: Okay, I understand that, but I did not have to do this under 1.5. Did they change the default in 1.7? I've been seeing comments about this for a while - perhaps a year or so. It might be a change in 1.7. I use the toolbar configuration most of the time, but see my comment here http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=406169 Any ideas as to why the blank X windows still continue to stick around after the Xterm windows opens? no - one of the comments said that might be DOS windows (but I don't have 1.7 to see). thanks Thomas Dickey wrote: On Fri, 15 Jan 2010, Jerry Lowry wrote: After my last install of 1.7 software the X server does start and the blank X windows do go away. But when I start an Xterm the blank X windows stay around. Anyway to start Xterm with them going away once started. Also, the Xterm that starts looks like a version from back in the 80's. Has Main Options, VT Options, VT Fonts accross the top. Any way to change this back to what I was running under 1.5? man xterm (command-line options) +tb This option indicates that xterm should not set up a toolbar. (resources) toolBar (class ToolBar) Specifies whether or not the toolbar should be displayed. The default is true. -- 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/ -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- 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: 1.7.1: no xdmcp login prompt after upgrade
Is your IPTRACE from the remote host's perspective, or from your cygwin-X perspective...??? I ask because I too am using 1.7.3 with -query and I'm having problems... but only after successfully logging onto the remote system. -Original Message- From: cygwin-xfree-ow...@cygwin.com [mailto:cygwin-xfree-ow...@cygwin.com] On Behalf Of Paxton, Michael Sent: Friday, January 15, 2010 12:33 PM To: cygwin-xfree@cygwin.com Subject: 1.7.1: no xdmcp login prompt after upgrade After upgrading to Cygwin/X 1.7.1, XDMCP query to any remote host no longer produces a login prompt. All XDMCP connections functioned correctly prior to upgrade. Examination of an iptrace report (ipreport10.out) on the remote host shows that Cygwin/X is not continuing the connection sequence after the remote host replies to the initial port 177 communication. To verify that X connectivity was still available on the remote host, connection was attempted from another local system with Cygwin/X 1.5.25. That connection functioned as expected, and its IP exchange was also captured on the remote host as a benchmark. (An attempt to include that traced was rejected by mailer-dae...@sourceware.org). Please advise as to any fix or workaround available. Alternately, please advise as to the best way to revert to Cygwin/X 1.5.25. Respectfully, D. Michael Paxton, Esq., M.B.A. FBI/CJIS Systems Agency Information Security Officer Indiana State Police (317) 232-5686 Is your IPTRACE from the remote host's perspective, or from your cygwin-X perspective...??? I ask because I too am using 1.7.3 with -query and I'm having problems... but only after successfully logging onto the remote system. Meaning I'm getting further than you. Here's my startup (note I'm using a fontserver on the XDM host): XWin -logverbose 255 \ -ac \ -query dmsdev.con-way.com \ -fp \tcp/dmsdev.con-way.com:8000,/usr/share/fonts/100dpi/,/usr/share/fonts/75dpi/,/usr/share/fonts/Type1/\ Thanks, -tony -- 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: Cygwin 1.7 xterm
From: cygwin-xfree-ow...@cygwin.com [mailto:cygwin-xfree- ow...@cygwin.com] On Behalf Of Jerry Lowry Sent: Friday, January 15, 2010 2:27 PM Okay, I understand that, but I did not have to do this under 1.5. Did they change the default in 1.7? I think a settings file went away. To get rid of the toolbar, put XTerm*toolBar: false (note case) in ~/.Xdefaults. Note that ~ is defined by /etc/passwd, not HOME. HTH, Mike
Re: Cygwin 1.7 xterm
would this be the case with the blank X windows hanging around (i.e. missing a definition in the .Xdefaults). Also, I just start X server and got this error trying to start the xterm from the startxwin.bat: 1 [main] xterm 3156 C:\Xwin\bin\xterm.exe: *** fatal error - couldn't allo cate heap, Win32 error 487, base 0x7D, top 0x91, reserve_size 1306624, a llocsize 1310720, page_const 4096 Mike Ayers wrote: From: cygwin-xfree-ow...@cygwin.com [mailto:cygwin-xfree- ow...@cygwin.com] On Behalf Of Jerry Lowry Sent: Friday, January 15, 2010 2:27 PM Okay, I understand that, but I did not have to do this under 1.5. Did they change the default in 1.7? I think a settings file went away. To get rid of the toolbar, put XTerm*toolBar: false (note case) in ~/.Xdefaults. Note that ~ is defined by /etc/passwd, not HOME. HTH, Mike -- 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: Cygwin 1.7 xterm
From: cygwin-xfree-ow...@cygwin.com [mailto:cygwin-xfree- ow...@cygwin.com] On Behalf Of Jerry Lowry Sent: Friday, January 15, 2010 3:07 PM Also, I just start X server and got this error trying to start the xterm from the startxwin.bat: Don't do that, read the release notes instead, or search the mail list archive (FAQ still needs an update): C:\ C:\cygwin\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe HTH, Mike
src/winsup/cygwin ChangeLog posix.sgml
CVSROOT:/cvs/src Module name:src Changes by: cori...@sourceware.org 2010-01-15 14:22:42 Modified files: winsup/cygwin : ChangeLog posix.sgml Log message: * posix.sgml: Mention dup3 and pipe2 as GNU extensions. Patches: http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/ChangeLog.diff?cvsroot=srcr1=1.4768r2=1.4769 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/posix.sgml.diff?cvsroot=srcr1=1.40r2=1.41
winsup/doc ChangeLog faq-setup.xml
CVSROOT:/cvs/uberbaum Module name:winsup Changes by: c...@sourceware.org 2010-01-15 18:47:31 Modified files: doc: ChangeLog faq-setup.xml Log message: * faq-setup.xml: Add missing setup options. Sort options. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/winsup/doc/ChangeLog.diff?cvsroot=uberbaumr1=1.253r2=1.254 http://sourceware.org/cgi-bin/cvsweb.cgi/winsup/doc/faq-setup.xml.diff?cvsroot=uberbaumr1=1.24r2=1.25
src/winsup/cygwin ChangeLog fhandler_socket.cc ...
CVSROOT:/cvs/src Module name:src Changes by: cori...@sourceware.org 2010-01-15 21:34:27 Modified files: winsup/cygwin : ChangeLog fhandler_socket.cc net.cc Log message: * fhandler_socket.cc (fhandler_socket::accept4): Set nonblocking flag exactly according to flags, as on Linux. * net.cc (cygwin_accept): Maintain BSD semantics here. Patches: http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/ChangeLog.diff?cvsroot=srcr1=1.4770r2=1.4771 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/fhandler_socket.cc.diff?cvsroot=srcr1=1.257r2=1.258 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/net.cc.diff?cvsroot=srcr1=1.269r2=1.270
src/winsup/doc ChangeLog faq-using.xml
CVSROOT:/cvs/src Module name:src Changes by: cori...@sourceware.org 2010-01-15 21:41:47 Modified files: winsup/doc : ChangeLog faq-using.xml Log message: * faq-using.xml (faq.using.bloda): Clarify wxvault.dll. Patches: http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/doc/ChangeLog.diff?cvsroot=srcr1=1.254r2=1.255 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/doc/faq-using.xml.diff?cvsroot=srcr1=1.27r2=1.28
Re: dup3/O_CLOEXEC/F_DUPFD_CLOEXEC
On Jan 14 17:09, Corinna Vinschen wrote: On Jan 14 08:39, Pierre A. Humblet wrote: At 08:17 AM 1/14/2010, Corinna Vinschen wrote: On Jan 14 06:02, Eric Blake wrote: In a multi-threaded app, any fd that is opened only temporarily, such as the one in mq_open, should be opened with O_CLOEXEC, so that no other thread can win a race and do a fork/exec inside the window when the temporary fd was open. So even though mq_open does not leak an fd to the current process, it should pass O_CLOEXEC as part of its internal open() call in order to avoid leaking the fd to unrelated child processes. Uh, ok, that makes sense. I'll send a revised patch later today. It will also include the pipe2 implementation. For the same reason we should also have SOCK_CLOEXEC, and SOCK_NONBLOCK while we are at it. I would use them in minires. Sure, but probably not yet, as far as my hack time is concerned. But of course SHTDI, PTC, and all that. I'd be glad for it, actually. It was simpler than I anticipated. I just applied a patch to implement accept4, and SOCK_NONBLOCK as well as SOCK_CLOEXEC for socket, socketpair and accept4. HTH, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: dup3/O_CLOEXEC/F_DUPFD_CLOEXEC
- Original Message - From: Corinna Vinschen To: cygwin-patches Sent: Friday, January 15, 2010 10:42 | On Jan 14 17:09, Corinna Vinschen wrote: | On Jan 14 08:39, Pierre A. Humblet wrote: | | For the same reason we should also have SOCK_CLOEXEC, and | SOCK_NONBLOCK while we are at it. I would use them in minires. | | Sure, but probably not yet, as far as my hack time is concerned. But | of course SHTDI, PTC, and all that. I'd be glad for it, actually. | | It was simpler than I anticipated. I just applied a patch to implement | accept4, and SOCK_NONBLOCK as well as SOCK_CLOEXEC for socket, | socketpair and accept4. Thanks, I was just looking into that. I see an issue with accept/accept4 and was going to ask you how to handle it. Before your changes in Cygwin the socket returned by accept had the same blocking (and async) property as the listening socket. Apparently this conforms to BSD but not to Linux (even old versions without accept4), http://www.kernel.org/doc/man-pages/online/pages/man2/accept.2.html POSIX is silent on the topic. After your changes the new socket is non-blocking if either the listening socket was non-blocking or SOCK_NONBLOCK is specified. This does not conform to Linux. Why not have accept4 conform to Linux but keep the old behavior of accept by changing accept in net.cc to res = fh-accept4 (peer, len, fh-is_nonblocking () ? SOCK_NONBLOCK : 0); There is a similar Linux discrepancy with async_io. Pierre
Re: dup3/O_CLOEXEC/F_DUPFD_CLOEXEC
On Jan 15 21:22, Corinna Vinschen wrote: On Jan 15 15:04, Pierre A. Humblet wrote: I see an issue with accept/accept4 and was going to ask you how to handle it. Before your changes in Cygwin the socket returned by accept had the same blocking (and async) property as the listening socket. Apparently this conforms to BSD but not to Linux (even old versions without accept4), http://www.kernel.org/doc/man-pages/online/pages/man2/accept.2.html POSIX is silent on the topic. After your changes the new socket is non-blocking if either the listening socket was non-blocking or SOCK_NONBLOCK is specified. This does not conform to Linux. Why not have accept4 conform to Linux but keep the old behavior of accept by changing accept in net.cc to res = fh-accept4 (peer, len, fh-is_nonblocking () ? SOCK_NONBLOCK : 0); There is a similar Linux discrepancy with async_io. I have no problem to change the SOCK_NONBLOCK stuff as you proposed. I don't like the idea to introduce such a new flag for ASYNC which doesn't exist on Linux, though. How important is the async mode anyway? Will we really get any problems with existing apps if we switch to the Linux behaviour for async? Oh, hang on. I guess we should better stick to the BSD behaviour. Any call to WSAAsyncSelect or WSAEventSelect clears Winsock's internal network event queue. This could lead to connection errors. Given that, the switch to a specific mode should stay the responsibility of the application, shouldn't it? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: dup3/O_CLOEXEC/F_DUPFD_CLOEXEC
- Original Message - From: Corinna Vinschen To: cygwin-patches Sent: Friday, January 15, 2010 15:34 | On Jan 15 21:22, Corinna Vinschen wrote: | On Jan 15 15:04, Pierre A. Humblet wrote: | I see an issue with accept/accept4 and was going to ask you how to | handle it. | | Before your changes in Cygwin the socket returned by accept had the | same blocking (and async) property as the listening socket. | Apparently this conforms to BSD but not to Linux (even old versions | without accept4), | http://www.kernel.org/doc/man-pages/online/pages/man2/accept.2.html | POSIX is silent on the topic. | | After your changes the new socket is non-blocking if either the | listening socket was non-blocking or SOCK_NONBLOCK is specified. This | does not conform to Linux. | | Why not have accept4 conform to Linux but keep the old behavior of accept by | changing accept in net.cc to | res = fh-accept4 (peer, len, fh-is_nonblocking () ? SOCK_NONBLOCK : 0); | | There is a similar Linux discrepancy with async_io. | | I have no problem to change the SOCK_NONBLOCK stuff as you proposed. | | I don't like the idea to introduce such a new flag for ASYNC which | doesn't exist on Linux, though. How important is the async mode anyway? | Will we really get any problems with existing apps if we switch to the | Linux behaviour for async? | | Oh, hang on. I guess we should better stick to the BSD behaviour. | Any call to WSAAsyncSelect or WSAEventSelect clears Winsock's internal | network event queue. This could lead to connection errors. Given | that, the switch to a specific mode should stay the responsibility | of the application, shouldn't it? I know next to nothing about this but notice that :accept4 calls fdsock which calls init_events which calls WSAEventSelect . Isn't that what you want to avoid? On the other hand I don't see how you can avoid it given this: Any WSAEventSelect association and network events selection set for the listening socket apply to the accepted socket. For example, if a listening socket has WSAEventSelect association of hEventObject with FD_ACCEPT, FD_READ, and FD_WRITE, then any socket accepted on that listening socket will also have FD_ACCEPT, FD_READ, and FD_WRITE network events associated with the same hEventObject. If a different hEventObject or network events are desired, the application should call WSAEventSelect, passing the accepted socket and the desired new information. Pierre
Re: dup3/O_CLOEXEC/F_DUPFD_CLOEXEC
On Jan 15 16:33, Pierre A. Humblet wrote:
From: Corinna Vinschen
| Oh, hang on. I guess we should better stick to the BSD behaviour.
| Any call to WSAAsyncSelect or WSAEventSelect clears Winsock's internal
| network event queue. This could lead to connection errors. Given
| that, the switch to a specific mode should stay the responsibility
| of the application, shouldn't it?
I know next to nothing about this but notice that :accept4 calls fdsock
which calls init_events which calls WSAEventSelect .
Isn't that what you want to avoid?
Oh, right. I'm wondering how this is supposed to work at all in
WinSock, if an application is using, say, blocking listening sockets and
only wants to use event driven IO on the accepted sockets. It looks
like this is impossible without the danger of losing information. In
theory, if the peer sends exactly one packet, the accepting socket could
wait forever for the packet if it arrived before WSAEventSelect has been
called. The FD_READ will never show up. The alternative is I'm just
exaggerating the potential problem. I don't know.
On the other hand I don't see how you can avoid it given this:
Any WSAEventSelect association and network events selection set for the
listening socket apply
to the accepted socket. For example, if a listening socket has WSAEventSelect
association of
hEventObject with FD_ACCEPT, FD_READ, and FD_WRITE, then any socket accepted
on that listening
socket will also have FD_ACCEPT, FD_READ, and FD_WRITE network events
associated with the same
hEventObject. If a different hEventObject or network events are desired, the
application should
call WSAEventSelect, passing the accepted socket and the desired new
information.
The event mask is not the problem since the mask given to WSAEventSelect
is always the same in Cygwin, the whole set, regardless of how the
socket is used. The problem is that every socket needs its own
event object so WSAEventSelect has to be called anyway.
What this means is, the accepted socket isn't in async mode anymore
since the WSAEventSelect call in init_events has ended it. So the async
flag is erroneously preserved and we will have to apply this patch AFAICS.
Index: fhandler_socket.cc
===
RCS file: /cvs/src/src/winsup/cygwin/fhandler_socket.cc,v
retrieving revision 1.258
diff -u -p -r1.258 fhandler_socket.cc
--- fhandler_socket.cc 15 Jan 2010 21:34:27 - 1.258
+++ fhandler_socket.cc 15 Jan 2010 22:00:08 -
@@ -1216,7 +1216,7 @@ fhandler_socket::accept4 (struct sockadd
fhandler_socket *sock = (fhandler_socket *) res_fd;
sock-set_addr_family (get_addr_family ());
sock-set_socket_type (get_socket_type ());
- sock-async_io (async_io ());
+ sock-async_io (false); /* fdsock switches async mode off. */
if (get_addr_family () == AF_LOCAL)
{
sock-set_sun_path (get_sun_path ());
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
Re: dup3/O_CLOEXEC/F_DUPFD_CLOEXEC
- Original Message - From: Corinna Vinschen To: cygwin-patches Sent: Friday, January 15, 2010 17:03 | On Jan 15 16:33, Pierre A. Humblet wrote: | From: Corinna Vinschen | | Oh, hang on. I guess we should better stick to the BSD behaviour. | | Any call to WSAAsyncSelect or WSAEventSelect clears Winsock's internal | | network event queue. This could lead to connection errors. Given | | that, the switch to a specific mode should stay the responsibility | | of the application, shouldn't it? | | I know next to nothing about this but notice that :accept4 calls fdsock | which calls init_events which calls WSAEventSelect . | Isn't that what you want to avoid? | | Oh, right. I'm wondering how this is supposed to work at all in | WinSock, if an application is using, say, blocking listening sockets and | only wants to use event driven IO on the accepted sockets. It looks | like this is impossible without the danger of losing information. In | theory, if the peer sends exactly one packet, the accepting socket could | wait forever for the packet if it arrived before WSAEventSelect has been | called. The FD_READ will never show up. The alternative is I'm just | exaggerating the potential problem. I don't know. | | On the other hand I don't see how you can avoid it given this: | | Any WSAEventSelect association and network events selection set for the listening socket apply | to the accepted socket. For example, if a listening socket has WSAEventSelect association of | hEventObject with FD_ACCEPT, FD_READ, and FD_WRITE, then any socket accepted on that listening | socket will also have FD_ACCEPT, FD_READ, and FD_WRITE network events associated with the same | hEventObject. If a different hEventObject or network events are desired, the application should | call WSAEventSelect, passing the accepted socket and the desired new information. | | The event mask is not the problem since the mask given to WSAEventSelect | is always the same in Cygwin, the whole set, regardless of how the | socket is used. The problem is that every socket needs its own | event object so WSAEventSelect has to be called anyway. I agree. It would be nice if the new event could be initialized to the value of the old. Then we could have too many events for the new socket, but that's OK. I am also wondering if we are misreading the doc. It says: For FD_READ, FD_OOB, and FD_ACCEPT network events, network event recording and event object signaling are level-triggered. and it goes on to provide an example where the event is reenabled if there is still data. The example given about the clears the internal network event record is of a completely different nature. The scenario you describe (one packet only, with a long delay between accept and WSAEventSelect) could easily be tested to settle the matter. Put a sleep before fdsock ! | What this means is, the accepted socket isn't in async mode anymore | since the WSAEventSelect call in init_events has ended it. So the async | flag is erroneously preserved and we will have to apply this patch AFAICS. At least we follow Linux :) Pierre
msiexec
I would like using msiexec.exe /i package.msi /qn My package haven't got any control panel. It is work in the local cygwin on the computer. But when i try in a ssh session it doesn't work . Why ? ssh administrat...@ip cd /cygdrive/c/app/ ;msiexec /i app.msi /qn -- View this message in context: http://old.nabble.com/msiexec-tp27173350p27173350.html Sent from the Cygwin list mailing list archive at Nabble.com. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: How to print textfiles in Cygwin 1.7?
Andy Koppe schrieb: One workaround is to convert the file manually using iconv, e.g.: $ iconv -f utf-8 -t iso-8859-1 bla.txt | a2ps -o bla.ps This works ok. Thanks! I will try to make an alias for it. Please note that 'nano' also doesn't support UTF-8 yet. While entering characters looks like it works initially, nano will internally think that you've entered two characters when you enter an umlaut. Hence things get wonky when you try to edit them. So that may be why I get some strange behavior of nano (disappearing letters and such) when editing files with umlauts. Thanks again! Niklaus -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Another nodosfilewarning warning
Jeremy Bopp wrote: Gary . wrote: cygwin warning: MS-DOS style path detected: c:\programme\develop\ruby\bin\inputrc.euro Preferred POSIX equivalent is (blah) Okay. Except I can't find a file anywhere containing any mention of inputrc.euro... (in fact the mentioned path doesn't even exist any more Check your environment variables to ensure that none of them point to that file. Aside from that, it would help if you gave more details regarding what exactly you're doing/running when you see this warning. You're right, it was a Windows environment variable which for whatever reason was not being converted. Maybe because the path doesn't exist? Thanks. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: How to print textfiles in Cygwin 1.7?
Thomas Wolff schrieb: So the easiest practical solution is to use a Windows tool: notepad /p filename This works, too. Thanks! Niklaus -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: How to print textfiles in Cygwin 1.7?
Thomas Wolff schrieb: 1. notepad /p prints to your default printer 2. for font configuration, invoke notepad manually; if you want a fixed-width font for text printing, these are recommendable for a good coverage of Unicode: Lucida Console, Courier New, Andale Mono, Everson Mono configure 10 pt font size to make sure 80 characters fit on a line, 11 pt for 72 characters 3. can somebody check/confirm this still works on Vista, please? Yes, this printing command still works in Vista, and also the font switching procedure. Niklaus -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: gcc4: FHS nit
Yaakov (Cygwin/X) wrote: I just came across this in FHS[1]: If a C preprocessor is installed, /lib/cpp must be a reference to it, for historical reasons. Yes, it's nitpicking, and I personally don't really care, but adding a /lib/cpp - /usr/bin/cpp-4.exe to the gcc4-core alternatives would make this compliant. Shouldn't it be /lib/cpp - /etc/alternatives/cpp then? -- Thomas -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Man pages garbled in 1.7.1
Hi, I upgraded to 1.7.1. But now I see my man page very difficult read; for instance it replaces hyphens with a-cap, and stuff like that. Could somebody suggest a solution? Thanks :J -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Redirecting $TEMP or a certain directory to /tmp
On Jan 15 07:53, Thomas Wiedmann wrote: mount -f E:/Temp /tmp Thanks, that worked. And, if you want this to be permanent you need to *put* it in /etc/fstab. My /etc directory in Cygwin has no fstab. Can I create it manually in Cygwin and does it work like in LINUX/UNIX or are additional steps be required? Did you try the User's Guide? http://cygwin.com/cygwin-ug-net/using.html#mount-table Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Another nodosfilewarning warning
On Jan 15 09:58, Gary . wrote: Jeremy Bopp wrote: Gary . wrote: cygwin warning: MS-DOS style path detected: c:\programme\develop\ruby\bin\inputrc.euro Preferred POSIX equivalent is (blah) Okay. Except I can't find a file anywhere containing any mention of inputrc.euro... (in fact the mentioned path doesn't even exist any more Check your environment variables to ensure that none of them point to that file. Aside from that, it would help if you gave more details regarding what exactly you're doing/running when you see this warning. You're right, it was a Windows environment variable which for whatever reason was not being converted. Maybe because the path doesn't exist? Cygwin can't know which environment variables have to be converted and which don't. Therefore only a small subset know to contain paths and necessary for its own operation is converted. The User's Guide contains a section about this: http://cygwin.com/cygwin-ug-net/setup-env.html Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: minor error from /etc/fstab
On Jan 14 16:21, Paul McFerrin wrote: I always get the following error when cygwin1.dll gets loaded for the first time: 1 [main] ksh 3000 read_flags: invalid fstab option - '0' Anyone know why I see such a message. Your /etc/fstab or /etc/fstab.d/$USER file has a broken line. Check against the required layout as described in the ... User's Guide: http://cygwin.com/cygwin-ug-net/using.html#mount-table Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: msiexec
On Jan 15 00:20, geoffrey wrote: I would like using msiexec.exe /i package.msi /qn My package haven't got any control panel. It is work in the local cygwin on the computer. But when i try in a ssh session it doesn't work . Why ? ssh administrat...@ip If msiexec requires the GUI, then you're out of luck anyway since the ssh session is not attached to a desktop. If that isn't it, maybe the User's Guide explains it: http://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-setuid-overview Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: 1.7.1 hangs on 000-cygwin-post-install.sh
2010/1/14 David Sherrets: I too experienced the same problem. The fix for me was this... I have a newer Dell machine. The hardware encryption API DLL (wxvault.dll) interferes with many Cygwin packages. This can be fixed stopping this DLL from loading at startup. (use Autoruns from Microsoft Sysinternals at http://www.microsoft.com/technet/sysinternals) I can't take credit for this, as it was my co-workers in Sweden who found the fix, but I though there are many here who might benefit! YES!!! A *BIG* thank you to your Swedish co-worker, and to you for telling here! This solved the problem for me as well. I have a Dell as well, my is almost three years old. That dll was on the AppInit tab and it was used by docmgr.exe that can be found as Document Manager on the Logon tab. I disabled them both and made a backup of my cygwin15 installation (including the mount keys in the registry). After all of this I restarted my Windows, run the setup and upgraded to 1.7 without any problem. Once again a big thank you! Maybe it is an idea to put this on the BLODA list? Regards, Frank -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: [cfe-dev] cygwin updates (was: dladdr and Dl_info)
On 14/01/2010 14:20, Reini Urban wrote: I have a working cygwin llvm and llvm-gcc, but had no time to produce a proper package yet. Attached are my cygport files and my local config. No patches were needed. But I haven't bothered to build clang yet, just the Clang llvmc plugin and llvm-gcc, which I thought is harder to build and gives us more gcc compatibility. Here's what I have so far for llvm/clang 2.6; the .cygport may be missing something, it's been a few weeks since I've looked at it. On the cygwin mailinglist we came to some required clang patches. http://cygwin.com/ml/cygwin/2010-01/msg00587.html Sorry, untested, as I got unrelated linker errors. The change to tools/CIndex/CIndexer.cpp looks fine if it works. The change to tools/driver/driver.cpp isn't really right; the code really needs to be refactored. The changes to the non-C++ include paths in lib/Frontend/InitHeaderSearch.cpp look a bit suspicious, but it's okay anyway. The change to lib/Headers/stddef.h is completely wrong; what is it supposed to fix? Still don't understand why cygwin doesn't implement dladdr, it would avoid some ugly ifdef... -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Can't set variables in a while loop that is passed to the rest of the script.
Eric Blake wrote: According to Damo, David on 1/14/2010 3:39 PM: Hi, I had a script that worked on UNIX, but on Cygwin it does not work. When I set a variable in a while loop I can't use it after the loop. However, this worked in UNIX. Any ideas why? Yes. ksh vs. bash. http://tiswww.case.edu/php/chet/bash/FAQ, E4. Not cygwin-specific. As was responded before, this isn't supposed to work in a pipe. Not in ksh either, I think, and I tried it, with ksh on a Sun and pdksh on cygwin. So I don't think this is a ksh vs bash issue. David, maybe you happened to have set the variable you checked before callling the script already? -- Thomas -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: How to print textfiles in Cygwin 1.7?
Corinna Vinschen schrieb: On Jan 12 15:59, Niklaus Kuehnis wrote: Hi, I've upgraded to Cygwin 1.7 (release version, clean install) and now am unable to print text files with non-ascii characters (i.e. German umlauts) from commandline. Did you read the User's Guide, especially http://cygwin.com/cygwin-ug-net/setup-locale.html ? I've now read that page. As UTF-8 is generally the preferred charset, I would like to stick to it. Does changing the language, e.g. to de_CH, change umlaut handling? It doesn't seem to, here. Best wishes, Niklaus -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: SOLVED: cygwin programs hang or return STATUS_ACCESS_VIOLATION in Windows Vista/2008/7
On Jan 14 14:13, Seth Wegner wrote: No action or response requested, this is for the next hapless googler. If Windows DEP is set to Turn on DEP for all programs and services except those I select certain cygwin-dependent exe files (in my case, ssh.exe) will hang or return errors. The solution is to either select those programs as DEP-safe or disable DEP. Works fine for me on W7 and Windows 2008. The only know problem related to this setting is if Terminal Services (TS) are installed on your 200X Server machine. In this case you can heal it by switching off DEP. But the actual problem is that Cygwin executables are not marked as TS-aware. That's a bit in the PE/COFF header, which isn't set by gcc, unless you use the latest gcc-4 release to build your applications. If the TS-aware fkag is not set, Windows loads a special DLL very early at process startup which is supposed to check the application for some sort of compatibility. While doing that, it potentially breaks the application by setting page protection flags to invalid values. I filed a service request at Microsoft, but the proble won't get fixed since there is a solution. The solution is to set the TS-aware bit in the executable. You can do that with a tool from the rebase package: peflags --tsaware=true your_application.exe Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: How to print textfiles in Cygwin 1.7?
Niklaus Kuehnis wrote: 1. notepad /p prints to your default printer ... Yes, this printing command still works in Vista, and also the font switching procedure. Thanks for checking. Please note that 'nano' also doesn't support UTF-8 yet. ... So that may be why I get some strange behavior of nano (disappearing letters and such) when editing files with umlauts. Maybe you'd like to give mined a try? (Improved version to come soon.) -- Thomas -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: How to print textfiles in Cygwin 1.7?
On Jan 15 11:08, Niklaus Kuehnis wrote: Corinna Vinschen schrieb: On Jan 12 15:59, Niklaus Kuehnis wrote: Hi, I've upgraded to Cygwin 1.7 (release version, clean install) and now am unable to print text files with non-ascii characters (i.e. German umlauts) from commandline. Did you read the User's Guide, especially http://cygwin.com/cygwin-ug-net/setup-locale.html ? I've now read that page. As UTF-8 is generally the preferred charset, I would like to stick to it. Does changing the language, e.g. to de_CH, change umlaut handling? It doesn't seem to, here. It does, though. If you read the page you have learned that setting LANG to just a language (de_CH), without a charset (.UTF-8) will set the character set to the Windows codepage which is the default ANSI codepage on your machine. In your case this is probably CP1252. If you want to be sure to use UTF-8, then say so: export LANG=de_CH.UTF-8. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: [cfe-dev] cygwin updates (was: dladdr and Dl_info)
On Jan 15 11:07, Vincent R. wrote: On 14/01/2010 14:20, Reini Urban wrote: I have a working cygwin llvm and llvm-gcc, but had no time to produce a proper package yet. Attached are my cygport files and my local config. No patches were needed. But I haven't bothered to build clang yet, just the Clang llvmc plugin and llvm-gcc, which I thought is harder to build and gives us more gcc compatibility. Here's what I have so far for llvm/clang 2.6; the .cygport may be missing something, it's been a few weeks since I've looked at it. On the cygwin mailinglist we came to some required clang patches. http://cygwin.com/ml/cygwin/2010-01/msg00587.html Sorry, untested, as I got unrelated linker errors. The change to tools/CIndex/CIndexer.cpp looks fine if it works. The change to tools/driver/driver.cpp isn't really right; the code really needs to be refactored. The changes to the non-C++ include paths in lib/Frontend/InitHeaderSearch.cpp look a bit suspicious, but it's okay anyway. The change to lib/Headers/stddef.h is completely wrong; what is it supposed to fix? Still don't understand why cygwin doesn't implement dladdr, it would avoid some ugly ifdef... http://cygwin.com/acronyms/#SHTDI http://cygwin.com/acronyms/#PTC Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: How to print textfiles in Cygwin 1.7?
On Jan 15 11:18, Corinna Vinschen wrote: On Jan 15 11:08, Niklaus Kuehnis wrote: Corinna Vinschen schrieb: http://cygwin.com/cygwin-ug-net/setup-locale.html I've now read that page. As UTF-8 is generally the preferred charset, I would like to stick to it. Does changing the language, e.g. to de_CH, change umlaut handling? It doesn't seem to, here. It does, though. If you read the page you have learned that setting LANG to just a language (de_CH), without a charset (.UTF-8) will set the character set to the Windows codepage which is the default ANSI codepage on your machine. In your case this is probably CP1252. If you want to be sure to use UTF-8, then say so: export LANG=de_CH.UTF-8. Without the trailing dot, of course. Sorry 'bout that. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[Re:] Language vs character settings [Re: How to print textfiles in Cygwin 1.7?]
Niklaus Kuehnis wrote:
... As UTF-8 is generally the preferred charset, I would like to stick
to it. Does changing the language, e.g. to de_CH, change umlaut
handling? It doesn't seem to, here.
That depends...
If you just have LANG in your environment to indicate the UTF-8
character set, or even no environment variable (meaning UTF-8 on cygwin),
and then set LANG=de_CH inside a terminal session, your environment and
your actual terminal encoding will become inconsistent,
with the consequence that many programs (esp. all modern programs
using the locale mechanism) will apply the wrong assumption about your
terminal.
That's why my suggestion for a more practical setting is:
export LC_CTYPE=C.UTF-8
to establish a more persistent declaration of your terminal's behaviour.
Then you can simply set LANG as you like to adjust other properties with
any applications that honour it.
This didn't become the standard scenario, however, due to other
considerations and compatibility with Linux distributions.
So my suggestion is to include this in your .profile:
export LC_CTYPE=${LANG-C.UTF-8}
to gain flexibility in changing LANG later.
--
Thomas
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: [cfe-dev] cygwin updates (was: dladdr and Dl_info)
On Fri, 15 Jan 2010 11:19:27 +0100, Corinna Vinschen
corinna-cyg...@cygwin.com wrote:
On Jan 15 11:07, Vincent R. wrote:
On 14/01/2010 14:20, Reini Urban wrote:
I have a working cygwin llvm and llvm-gcc,
but had no time to produce a proper package yet.
Attached are my cygport files and my local config.
No patches were needed.
But I haven't bothered to build clang yet,
just the Clang llvmc plugin and llvm-gcc,
which I thought is harder to build and gives us more gcc
compatibility.
Here's what I have so far for llvm/clang 2.6; the .cygport may be
missing something, it's been a few weeks since I've looked at it.
On the cygwin mailinglist we came to some required clang patches.
http://cygwin.com/ml/cygwin/2010-01/msg00587.html
Sorry, untested, as I got unrelated linker errors.
The change to tools/CIndex/CIndexer.cpp looks fine if it works. The
change to tools/driver/driver.cpp isn't really right; the code really
needs to be refactored. The changes to the non-C++ include paths in
lib/Frontend/InitHeaderSearch.cpp look a bit suspicious, but it's
okay
anyway. The change to lib/Headers/stddef.h is completely wrong; what
is it supposed to fix?
Still don't understand why cygwin doesn't implement dladdr, it would
avoid
some
ugly ifdef...
http://cygwin.com/acronyms/#SHTDI
http://cygwin.com/acronyms/#PTC
It's not too difficult to add Dl_info definition (We will support only
retrieving path name):
typedef struct
{
const char*dli_fname[PATH_MAX]; /* Filename of defining object */
void *dli_fbase; /* NA */
const char*dli_sname; /* NA */
void *dli_saddr; /* NA */
} Dl_info;
int dladdr(void *addr, Dl_info *info)
{
// see
http://trac.enlightenment.org/e/browser/trunk/PROTO/evil/src/lib/dlfcn/dlfcn.c
// for an implementation
}
Regards
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: How to print textfiles in Cygwin 1.7?
Corinna Vinschen schrieb: I've now read that page. As UTF-8 is generally the preferred charset, I would like to stick to it. Does changing the language, e.g. to de_CH, change umlaut handling? It doesn't seem to, here. It does, though. If you read the page you have learned that setting LANG to just a language (de_CH), without a charset (.UTF-8) will set the character set to the Windows codepage which is the default ANSI codepage on your machine. In your case this is probably CP1252. If you want to be sure to use UTF-8, then say so: export LANG=de_CH.UTF-8. I set this variable (and also LC_CTYPE and LC_ALL), and printing with umlauts with bare a2ps works fine now. Thanks! Niklaus -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: 1.7.1: problem with public key authentication on domain accounts
Corinna Vinschen corinna-cygwin at cygwin.com writes: On Jan 14 17:32, Andrew Ng wrote: What I did was to change the group of my domain user to be Administrators in /etc/passwd rather than the domain group. This stops the following error from occurring every time I try to ssh to my machine as my domain user: - 1 [main] -tcsh 13776 C:\Cygwin\bin\tcsh.exe: *** fatal error - couldn't dynamically determine load address for 'WSAGetLastError' (handle 0x), Win32 error 126 In fact making the group Users also works fine, just not the domain group. Using the domain group seems to result in no file access permissions to the system libraries and hence the error above when starting the tcsh shell. This isn't ideal as I would really prefer to be using the domain group but it's better than having to start sshd manually which was my previous workaround. By the way I'm running on Windows XP Pro x64 SP2. http://cygwin.com/ml/cygwin/2010-01/msg00334.html Corinna Thanks for the link. That does explain what's going on in this situation. I think your suggestion of adding the local BUILTIN\Users group would be nice. I'm not too sure our IT will be too keen on adding a domain user for Cygwin sshd purposes. Regards, Andrew -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: How to print textfiles in Cygwin 1.7?
2010/1/15 Niklaus Kuehnis: If you want to be sure to use UTF-8, then say so: export LANG=de_CH.UTF-8. I set this variable (and also LC_CTYPE and LC_ALL), and printing with umlauts with bare a2ps works fine now. Thanks! I can't confirm that. Sure you were printing a UTF-8 file there? Andy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
ps -eaf not listing all server processes on Windows Server 2008
Using Cygwin 1.7.1-1 on Windows Server 2008. Using ps -eaf. I need a listing of all server processes, but on Windows Server 2008 and Cygwin 1.7.1-1 you can only get a list of the processes, owned by you and not all servers processes. This is a new behavior. Is it possiple to get all the servers processes listed with ps on Windows Server 2008? -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: ps -eaf not listing all server processes on Windows Server 2008
On Jan 15 13:04, Bengt Albjerg wrote: Using Cygwin 1.7.1-1 on Windows Server 2008. Using ps -eaf. I need a listing of all server processes, but on Windows Server 2008 and Cygwin 1.7.1-1 you can only get a list of the processes, owned by you and not all servers processes. This is a new behavior. Is it possiple to get all the servers processes listed with ps on Windows Server 2008? That's contrary to what I see. Cygwin 1.7 introduced a new way to keep track of all Cygwin processes, even if they are running under another user account and in another session. Cygwin 1.5.x was not able to do that starting with Windows Server 2003. Consequentially, when running Cygwin 1.7, I see something like this: $ ps -ef UID PIDPPID TTY STIME COMMAND corinna1664 1 con 14:23:49 /usr/bin/tcsh cyg_serv1052 1 ? 14:23:55 /usr/bin/cygrunsrv cyg_serv33921052 ? 14:23:55 /usr/sbin/sshd corinna3208 1 con 14:23:57 /usr/bin/tcsh corinna 9361664 con 14:24:28 /usr/bin/ps As you can imagine, the processes running under the cyg_server account are services running in session 0, while my own processes are running in the GUI session 2. I see the same output, regardless of running under UAC or in an elevated shell. Unless, of course, the processes are running under another Cygwin DLL. Processe trees running under different Cygwin DLLs are isolated against each others. They don't share any common IPC objects. As for `ps -W' output, that's still subject to Windows security considerations. If you run it in a UAC-controlled shell or under a non-privileged account, you can only see the processes running in your own session. If you run it in an elevated shell, you'll see all processes. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: 1.7.1 hangs on 000-cygwin-post-install.sh
On Jan 15 11:03, Frank Fesevur wrote: 2010/1/14 David Sherrets: I too experienced the same problem. The fix for me was this... I have a newer Dell machine. The hardware encryption API DLL (wxvault.dll) interferes with many Cygwin packages. This can be fixed stopping this DLL from loading at startup. (use Autoruns from Microsoft Sysinternals at http://www.microsoft.com/technet/sysinternals) I can't take credit for this, as it was my co-workers in Sweden who found the fix, but I though there are many here who might benefit! YES!!! A *BIG* thank you to your Swedish co-worker, and to you for telling here! This solved the problem for me as well. I have a Dell as well, my is almost three years old. That dll was on the AppInit tab and it was used by docmgr.exe that can be found as Document Manager on the Logon tab. I disabled them both and made a backup of my cygwin15 installation (including the mount keys in the registry). After all of this I restarted my Windows, run the setup and upgraded to 1.7 without any problem. Once again a big thank you! Maybe it is an idea to put this on the BLODA list? It's already in the list: http://cygwin.com/faq/faq.using.html#faq.using.bloda Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Can't set variables in a while loop that is passed to the rest of the script.
On Friday, January 15, 2010, Thomas Wolff wrote:
As was responded before, this isn't supposed to work in a pipe. Not in ksh
either, I think,
No, it works in real ksh. If the last command in a pipeline is a
builtin, it is run in the current shell.
$ unset foo bar
$ echo ${foo=hiya} | read bar
$ echo foo=$foo bar=$bar
the above will set bar but not foo in ksh. Some shells will set foo
but not bar. Current bash sets neither. No shell sets both.
But not Cygwin-related.
--
Mark J. Reed markjr...@gmail.com
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Man pages garbled in 1.7.1
On Fri, Jan 15, 2010 at 7:08 PM, Niklaus Kuehnis kuehnik_0...@gmx-topmail.de wrote: Jeenu V schrieb: I upgraded to 1.7.1. But now I see my man page very difficult read; for instance it replaces hyphens with a-cap, and stuff like that. Could somebody suggest a solution? Manpages get better if you switch your terminal to mintty. Unfortunately here this broke non-ascii characters in nano. Perhaps you don't have non-ascii characters. I'm sorry; I forgot to mention that it was OK before the upgrade. I used and still use PuTTYCyg. -- :J -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
RE: Man pages garbled in 1.7.1
From: Jeenu V Sent: Friday, January 15, 2010 04:32 To: cygwin@cygwin.com Subject: Man pages garbled in 1.7.1 Hi, I upgraded to 1.7.1. But now I see my man page very difficult read; for instance it replaces hyphens with a-cap, and stuff like that. Could somebody suggest a solution? Thanks :J You might review the recent related message thread: http://cygwin.com/ml/cygwin/2010-01/msg00499.html --Ken Nellis
Re: [cfe-dev] cygwin updates (was: dladdr and Dl_info)
On Jan 15 11:40, Vincent R. wrote:
It's not too difficult to add Dl_info definition (We will support only
retrieving path name):
typedef struct
{
const char *dli_fname[PATH_MAX]; /* Filename of defining object */
void*dli_fbase; /* NA */
const char *dli_sname; /* NA */
void*dli_saddr; /* NA */
} Dl_info;
int dladdr(void *addr, Dl_info *info)
{
// see
http://trac.enlightenment.org/e/browser/trunk/PROTO/evil/src/lib/dlfcn/dlfcn.c
// for an implementation
}
The implementation won't work on Cygwin for functions exported by the
Cygwin DLL itself. At least not as you expect it to work. Every such
symbol will return the application's pathname in dli_fname. The reason
is the way the functions are exported from libcygwin.a. You always get
the address of the function stub linked statically to the executable.
I fear this needs more work for Cygwin.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] New: arj 3.10.22-1 -- archiver for .arj files
PACKAGE DESCRIPTION === Homepage: http://www.sourceforge.net/projects/arj License : GPL An open source version of the arj archiver. This version has been created with the intent to preserve maximum compatibility and retain the feature set of original ARJ archiver as provided by ARJ Software, Inc. CHANGES SINCE LAST RELEASE == See /usr/share/doc/arj-*/rev_hist.txt INSTALL OR UPGRADE NOTES Standard Cygwin install. CYGWIN INSTALLATION INFORMATION === To install this package, click on the Install Cygwin now link on the http://cygwin.com/ web page. This downloads setup.exe to your system. Then, run setup and answer all of the questions. You'll find the package listed in the All category. After installation, read the documentation at directories: /usr/share/doc/package-version/* /usr/share/doc/Cygwin/package-version.README If you have questions or comments, please send them to the Cygwin mailing list at cygwin@cygwin.com. CYGWIN-ANNOUNCE UNSUBSCRIBE INFO This message has been sent to cygwin-announce list. If you want to unsubscribe from the mailing list, look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com More information on unsubscribing can be found: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at the above URL. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: [cfe-dev] cygwin updates (was: dladdr and Dl_info)
On Fri, 15 Jan 2010 15:18:28 +0100, Corinna Vinschen
On Jan 15 11:40, Vincent R. wrote:
It's not too difficult to add Dl_info definition (We will support only
retrieving path name):
typedef struct
{
const char *dli_fname[PATH_MAX]; /* Filename of defining object
*/
void *dli_fbase; /* NA */
const char *dli_sname; /* NA */
void *dli_saddr; /* NA */
} Dl_info;
int dladdr(void *addr, Dl_info *info)
{
// see
http://trac.enlightenment.org/e/browser/trunk/PROTO/evil/src/lib/dlfcn/dlfcn.c
// for an implementation
}
The implementation won't work on Cygwin for functions exported by the
Cygwin DLL itself. At least not as you expect it to work. Every such
symbol will return the application's pathname in dli_fname. The reason
is the way the functions are exported from libcygwin.a. You always get
the address of the function stub linked statically to the executable.
I fear this needs more work for Cygwin.
I understand but I suppose it would work for other dlls and it's not
important if
it doesn't work for cygwin dll itself because until now you didn't need
it.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: How to print textfiles in Cygwin 1.7?
Andy Koppe schrieb: 2010/1/15 Niklaus Kuehnis: If you want to be sure to use UTF-8, then say so: export LANG=de_CH.UTF-8. I set this variable (and also LC_CTYPE and LC_ALL), and printing with umlauts with bare a2ps works fine now. Thanks! I can't confirm that. Sure you were printing a UTF-8 file there? You're right. I probably produced the file with rxvt that seems to run in Latin1. Niklaus -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: 1.7.1 hangs on 000-cygwin-post-install.sh
2010/1/15 Corinna Vinschen: On Jan 15 11:03, Frank Fesevur wrote: 2010/1/14 David Sherrets: I have a newer Dell machine. The hardware encryption API DLL (wxvault.dll) interferes with many Cygwin packages. This can be fixed stopping this DLL from loading at startup. (use Autoruns from Microsoft Sysinternals at http://www.microsoft.com/technet/sysinternals) Maybe it is an idea to put this on the BLODA list? It's already in the list: http://cygwin.com/faq/faq.using.html#faq.using.bloda I don't have the mentioned fingerprint reader software, so therefore I overlooked this. I have Embassy Security Center also by Wave Systems Corp. This also uses this wxvault.dll. I would suggest to change this line to something like: Various programs by Wave Systems Corp using wxvault.dll, including Embassy Trust Suite and Embassy Security Center. Since I found this on all Dell workstations (not on servers) I have checked here at the office, maybe even add that it is pre-installed on many Dell systems. Regards, Frank -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
missing setup command line arguments in the FAQ.
The command line arguments listed in the FAQ http://cygwin.com/faq/faq-nochunks.html#faq.setup.cli are incomplete. The following are missing. -O --only-site Ignore all sites except for -s -P --packages Specify packages to install -C --categoriesSpecify entire categories to install -p --proxy HTTP/FTP proxy (host:port) -X --no-verify Don't verify setup.ini signatures -K --pubkeyPath to extra public key file (gpg format) -S --sexpr-pubkey Extra public key in s-expr format -u --untrusted-keysUse untrusted keys from last-extrakeys -U --keep-untrusted-keys Use untrusted keys and retain all I apologize for the lack of a patch. - Barry Disclaimer: Statements made herein are not made on behalf of NIAID. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Redirecting $TEMP or a certain directory to /tmp
On Fri, Jan 15, 2010 at 07:53:43AM +0100, Thomas Wiedmann wrote: mount -f E:/Temp /tmp Thanks, that worked. And, if you want this to be permanent you need to *put* it in /etc/fstab. My /etc directory in Cygwin has no fstab. Can I create it manually in Cygwin and does it work like in LINUX/UNIX or are additional steps be required? In that case you probably are not running Cygwin 1.7.1. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: minor error from /etc/fstab
On Fri, Jan 15, 2010 at 10:58:19AM +0100, Corinna Vinschen wrote: On Jan 14 16:21, Paul McFerrin wrote: I always get the following error when cygwin1.dll gets loaded for the first time: 1 [main] ksh 3000 read_flags: invalid fstab option - '0' Anyone know why I see such a message. Your /etc/fstab or /etc/fstab.d/$USER file has a broken line. Check against the required layout as described in the ... User's Guide: http://cygwin.com/cygwin-ug-net/using.html#mount-table This is rather unprecedented isn't it? There is a problem with a data file, an error is reported on same? I wonder if this will catch on. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: [cfe-dev] cygwin updates (was: dladdr and Dl_info)
On Fri, Jan 15, 2010 at 11:19:27AM +0100, Corinna Vinschen wrote: On Jan 15 11:07, Vincent R. wrote: On 14/01/2010 14:20, Reini Urban wrote: I have a working cygwin llvm and llvm-gcc, but had no time to produce a proper package yet. Attached are my cygport files and my local config. No patches were needed. But I haven't bothered to build clang yet, just the Clang llvmc plugin and llvm-gcc, which I thought is harder to build and gives us more gcc compatibility. Here's what I have so far for llvm/clang 2.6; the .cygport may be missing something, it's been a few weeks since I've looked at it. On the cygwin mailinglist we came to some required clang patches. http://cygwin.com/ml/cygwin/2010-01/msg00587.html Sorry, untested, as I got unrelated linker errors. The change to tools/CIndex/CIndexer.cpp looks fine if it works. The change to tools/driver/driver.cpp isn't really right; the code really needs to be refactored. The changes to the non-C++ include paths in lib/Frontend/InitHeaderSearch.cpp look a bit suspicious, but it's okay anyway. The change to lib/Headers/stddef.h is completely wrong; what is it supposed to fix? Still don't understand why cygwin doesn't implement dladdr, it would avoid some ugly ifdef... http://cygwin.com/acronyms/#SHTDI http://cygwin.com/acronyms/#PTC And most importantly: http://cygwin.com/acronyms/#WJM cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: missing setup command line arguments in the FAQ.
On Fri, Jan 15, 2010 at 12:32:12PM -0500, Buchbinder, Barry (NIH/NIAID) [E] wrote: The command line arguments listed in the FAQ http://cygwin.com/faq/faq-nochunks.html#faq.setup.cli are incomplete. The following are missing. -O --only-site Ignore all sites except for -s -P --packages Specify packages to install -C --categoriesSpecify entire categories to install -p --proxy HTTP/FTP proxy (host:port) -X --no-verify Don't verify setup.ini signatures -K --pubkeyPath to extra public key file (gpg format) -S --sexpr-pubkey Extra public key in s-expr format -u --untrusted-keysUse untrusted keys from last-extrakeys -U --keep-untrusted-keys Use untrusted keys and retain all I apologize for the lack of a patch. I've added these to the FAQ. I haven't published the changes yet though. Thanks. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: [cfe-dev] cygwin updates (was: dladdr and Dl_info)
On Fri, 15 Jan 2010 13:40:53 -0500, Christopher Faylor cgf-use-tqsdqsdqsd...@cygwin.com wrote: On Fri, Jan 15, 2010 at 11:19:27AM +0100, Corinna Vinschen wrote: On Jan 15 11:07, Vincent R. wrote: On 14/01/2010 14:20, Reini Urban wrote: I have a working cygwin llvm and llvm-gcc, but had no time to produce a proper package yet. Attached are my cygport files and my local config. No patches were needed. But I haven't bothered to build clang yet, just the Clang llvmc plugin and llvm-gcc, which I thought is harder to build and gives us more gcc compatibility. Here's what I have so far for llvm/clang 2.6; the .cygport may be missing something, it's been a few weeks since I've looked at it. On the cygwin mailinglist we came to some required clang patches. http://cygwin.com/ml/cygwin/2010-01/msg00587.html Sorry, untested, as I got unrelated linker errors. The change to tools/CIndex/CIndexer.cpp looks fine if it works. The change to tools/driver/driver.cpp isn't really right; the code really needs to be refactored. The changes to the non-C++ include paths in lib/Frontend/InitHeaderSearch.cpp look a bit suspicious, but it's okay anyway. The change to lib/Headers/stddef.h is completely wrong; what is it supposed to fix? Still don't understand why cygwin doesn't implement dladdr, it would avoid some ugly ifdef... http://cygwin.com/acronyms/#SHTDI http://cygwin.com/acronyms/#PTC And most importantly: http://cygwin.com/acronyms/#WJM No sorry you should add this one : IRHA (I Really Hate Acronyms) -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Fwd: cygwin 1.7.1 cygrunsrv-sshd - unable to login
Hi all. I am trying to set up ssh server as service in standalone Windows 2003. Sorry if this already was questioned but I did not find anything related in near maillist archive. After ssh-host-config I'm getting sshd service, which does not accept any logins (log -d -d attached, found nothing helpful there). However if I run /usr/sbin/sshd from cygwin shell, it starts and I am able to login with both certificate and keyboard-interactive methods. If I change ssh service login user to my login then I am able to login also. What may be wrong? problem 2: first trials to set up service leaded to starting two cygrunsrv processes (parent and child) and one sshd. But now I am getting one cygrunsrv process and one sshd, and parent of sshd is not running. To stop process, I have to manually kill sshd. I already removed and reinstalled service and config file, but behavior persists. -- LogicDaemon debug2: load_server_config: filename /etc/sshd_config debug2: load_server_config: done config len = 212 debug2: parse_server_config: config /etc/sshd_config len 212 debug1: sshd version OpenSSH_5.3p1 debug1: read PEM private key done: type RSA debug1: private host key: #0 type 1 RSA debug1: read PEM private key done: type DSA debug1: private host key: #1 type 2 DSA debug1: rexec_argv[0]='/usr/sbin/sshd' debug1: rexec_argv[1]='-d' debug1: rexec_argv[2]='-d' debug1: rexec_argv[3]='-D' debug2: fd 3 setting O_NONBLOCK debug1: Bind to port 22 on 0.0.0.0. Server listening on 0.0.0.0 port 22. debug1: fd 4 clearing O_NONBLOCK debug1: Server will not fork when running in debugging mode. debug1: rexec start in 4 out 4 newsock 4 pipe -1 sock 7 debug1: inetd sockets after dupping: 3, 3 Connection from 192.168.1.9 port 1264 debug1: Client protocol version 2.0; client software version PuTTY_Release_0.60 debug1: no match: PuTTY_Release_0.60 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.3 debug2: fd 3 setting O_NONBLOCK debug1: list_hostkey_types: ssh-rsa,ssh-dss debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-...@lysator.liu.se debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-...@lysator.liu.se debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac...@openssh.com,hmac-ripemd160,hmac-ripemd...@openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac...@openssh.com,hmac-ripemd160,hmac-ripemd...@openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,z...@openssh.com debug2: kex_parse_kexinit: none,z...@openssh.com debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes256-ctr,aes256-cbc,rijndael-...@lysator.liu.se,aes192-ctr,aes192-cbc,aes128-ctr,aes128-cbc,blowfish-ctr,blowfish-cbc,3des-ctr,3des-cbc,arcfour256,arcfour128 debug2: kex_parse_kexinit: aes256-ctr,aes256-cbc,rijndael-...@lysator.liu.se,aes192-ctr,aes192-cbc,aes128-ctr,aes128-cbc,blowfish-ctr,blowfish-cbc,3des-ctr,3des-cbc,arcfour256,arcfour128 debug2: kex_parse_kexinit: hmac-sha1,hmac-sha1-96,hmac-md5 debug2: kex_parse_kexinit: hmac-sha1,hmac-sha1-96,hmac-md5 debug2: kex_parse_kexinit: zlib,none debug2: kex_parse_kexinit: zlib,none debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: mac_setup: found hmac-sha1 debug1: kex: client-server aes256-ctr hmac-sha1 none debug2: mac_setup: found hmac-sha1 debug1: kex: server-client aes256-ctr hmac-sha1 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST_OLD received debug1: SSH2_MSG_KEX_DH_GEX_GROUP sent debug2: dh_gen_key: priv key bits set: 254/512 debug2: bits set: 2035/4096 debug1: expecting SSH2_MSG_KEX_DH_GEX_INIT debug2: bits set: 2088/4096 debug1: SSH2_MSG_KEX_DH_GEX_REPLY sent debug2: kex_derive_keys debug2: set_newkeys: mode 1 debug2: cipher_init: set keylen (16 - 32) debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug2: set_newkeys: mode 0 debug2: cipher_init: set keylen (16 - 32) debug1: SSH2_MSG_NEWKEYS received debug1: KEX done debug1: userauth-request for user logicdaemon service ssh-connection method none debug1: attempt 0 failures 0 debug2: parse_server_config: config reprocess config len 212 Invalid
Re: Fwd: cygwin 1.7.1 cygrunsrv-sshd - unable to login
On 01/15/2010 02:18 PM, LogicDaemon wrote: Hi all. I am trying to set up ssh server as service in standalone Windows 2003. Sorry if this already was questioned but I did not find anything related in near maillist archive. After ssh-host-config I'm getting sshd service, which does not accept any logins (log -d -d attached, found nothing helpful there). However if I run /usr/sbin/sshd from cygwin shell, it starts and I am able to login with both certificate and keyboard-interactive methods. If I change ssh service login user to my login then I am able to login also. What may be wrong? problem 2: first trials to set up service leaded to starting two cygrunsrv processes (parent and child) and one sshd. But now I am getting one cygrunsrv process and one sshd, and parent of sshd is not running. To stop process, I have to manually kill sshd. I already removed and reinstalled service and config file, but behavior persists. Forwarding multiple copies of the same message to this list will not gain you any friends on this list. I suggest you look at the email archives for issues with 'sshd' installations. Most of them result from bad configuration, as is the case with yours (*never* run 'sshd' directly from the command line as a user other than the one that runs it as a service). I also recommend two other things: 1. Read the Users Guide for information about switching users. I highly recommend you implement the LSA package option. http://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-setuid-overview 2. To quickly recover from the hole you're in, wipe your Cygwin installation and start over, using the configuration scripts (ssh-host-config, ssh-user-config) at your disposal and your new found knowledge from the Users Guide, email archives, and even the README. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
RE: Can't set variables in a while loop that is passed to the rest of the script.
The pipe is what spawns the sub shell. In Unix the last process runs in your
current shell. In Linux the first process of the pipe runs in the current
shell. The difference is that when the while statement (which is run in the
sub shell) finishes the sub shell dies and any variable changes are lost. In
Unix the variables remain in the current shell.
Sincerely,
Brian S. Wilson
===
Home: (678) 376-9258 Cell: (678) 232-9357 wil...@ds.net
===
-- Original Message ---
From: Damo, David david.d...@cibc.com
To: Damo, David david.d...@cibc.com, cygwin@cygwin.com
cygwin@cygwin.com
Sent: Thu, 14 Jan 2010 18:23:28 -0500
Subject: RE: Can't set variables in a while loop that is passed to the rest
of the script.
Hi,
I have fixed the problem. It seems in cygwin it spawns a subshell
even under bash. I used a for loop instead and everything worked nicely.
for line in `sed 's/\$/^/g' $propfile`
do
nvpair=$(echo $line | awk -F= '{print $1,$2}')
set -- $nvpair
if [ ! $1 = ]; then
eval $1=\$2\
fi
done
-Original Message-
From: Damo, David
Sent: Thursday, January 14, 2010 5:40 PM
To: 'cygwin@cygwin.com'
Subject: Can't set variables in a while loop that is passed to the
rest of the script.
Hi,
I had a script that worked on UNIX, but on Cygwin it does not work.
When I set a variable in a while loop I can't use it after the loop.
However, this worked in UNIX. Any ideas why? All variables set after
the done command are blank, but can be seen in the while loop.
propfile=${SCRIPT_HOME}/${propfilename}
sed 's/\$/^/g' $propfile | while read line
do
export david=Hello
nvpair=$(echo $line | awk -F= '{print $1,$2}')
set -- $nvpair
if [ ! $1 = ]; then
eval $1=\$2\
fi
done
echo $david
echo Setting siteminder_home
echo $siteminder_home
Thanks,
David
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
--- End of Original Message ---
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Can't set variables in a while loop that is passed to the rest of the script.
Brian Wilson wilson at ds.net writes: The pipe is what spawns the sub shell. In Unix the last process runs in your current shell. In Linux the first process of the pipe runs in the current shell. The difference is that when the while statement (which is run in the sub shell) finishes the sub shell dies and any variable changes are lost. In Unix the variables remain in the current shell. Don't top-post. Also, your terminology is incorrect. The correct formulation is that: The use of a single pipe in a shell historically created TWO subshells, one for each side (a pipeline with two | created three subshells, for the three commands, etc.). Then some shells decided to optimize. The most common optimization is that the last pipe in the pipeline is done in the current shell, but POSIX went one step further and said that ANY, or even ALL, of the pipe commands in the pipeline can be executed in the current shell. However, I don't know of any shell offhand that optimizes only the first command in isolation, nor of any shell that attempts to optimize more than one pipe command per pipeline. In other words, the optimization tends to be a question between last vs. none, and not between last vs. first. Furthermore, it is not Unix vs. Linux that decides whether a subshell is created for each side of the pipe, but the implementation of the particular shell you are running (ksh vs. zsh vs. bash...) and how much they chose to optimize. In all cases, the shell calls pipe(2) (well, actually ksh uses socketpair(2), but the effect is the same), and that behaves identically across all platforms. The difference in the number of subshells is thus how many fork (2) calls are made after the pipe is created, and not how the pipe(2) call behaved. Bash follows the traditional behavior (no pipeline optimizations whatsoever), whereas dash tries to optimize as much as possible. But the bash behavior of no optimization will be the same whether bash is running on Cygwin, on a traditional Unix machine like Solaris, or on Linux; likewise the dash behavior of optimizing whatever it can, regardless of platform. But if you step back and look at the bigger picture, and realize that which shell is chosen to implement /bin/sh on the various platforms, then you can understand why the behavior differs as you change machines (for example, Linux tends to favor bash as /bin/sh, while Solaris tends to favor ksh). Since POSIX allows both behaviors (either the creation of a subshell, or the optimization into the current shell), the only portable way to work with pipelines is to make no assumption about which shell will be running a command within a pipeline. Thus, any variable assignments made in a pipe (and that includes via the read builtin) will affect subsequent commands only on those shells that chose to optimize that part of the pipeline into the current shell. -- Eric Blake -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: 1.7.1 hangs on 000-cygwin-post-install.sh
On Jan 15 16:48, Frank Fesevur wrote: 2010/1/15 Corinna Vinschen: On Jan 15 11:03, Frank Fesevur wrote: 2010/1/14 David Sherrets: I have a newer Dell machine. The hardware encryption API DLL (wxvault.dll) interferes with many Cygwin packages. This can be fixed stopping this DLL from loading at startup. (use Autoruns from Microsoft Sysinternals at http://www.microsoft.com/technet/sysinternals) Maybe it is an idea to put this on the BLODA list? It's already in the list: http://cygwin.com/faq/faq.using.html#faq.using.bloda I don't have the mentioned fingerprint reader software, so therefore I overlooked this. I have Embassy Security Center also by Wave Systems Corp. This also uses this wxvault.dll. I would suggest to change this line to something like: Various programs by Wave Systems Corp using wxvault.dll, including Embassy Trust Suite and Embassy Security Center. Done. Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: missing setup command line arguments in the FAQ.
On Jan 15 13:47, Christopher Faylor wrote: On Fri, Jan 15, 2010 at 12:32:12PM -0500, Buchbinder, Barry (NIH/NIAID) [E] wrote: The command line arguments listed in the FAQ http://cygwin.com/faq/faq-nochunks.html#faq.setup.cli are incomplete. The following are missing. -O --only-site Ignore all sites except for -s -P --packages Specify packages to install -C --categoriesSpecify entire categories to install -p --proxy HTTP/FTP proxy (host:port) -X --no-verify Don't verify setup.ini signatures -K --pubkeyPath to extra public key file (gpg format) -S --sexpr-pubkey Extra public key in s-expr format -u --untrusted-keysUse untrusted keys from last-extrakeys -U --keep-untrusted-keys Use untrusted keys and retain all I apologize for the lack of a patch. I've added these to the FAQ. I haven't published the changes yet though. I've just published the latest FAQ changes. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
1.7.1: terminal not passing Ctrl-C to sub-sub cygwin processes
From within cygwin python, if I call os.system running a cygwin sub-process, and I hit Ctrl-C while that cygwin sub-process is running, the Ctrl-C does nothing (absolutely nothing -- nothing is printed, nothing terminates, no sound is made -- it's as if I didn't press the key at all). I've attached a simple script which easily reproduces the situation. When I run the script as ./ctrlc.py 0, Ctrl-C kill the process, but when I run it with an argument of 1 or more, hitting Ctrl-C has no effect. I have not testing this with anything other than python, but I have a feeling that it's not python related. Cygwin Configuration Diagnostics Current System Time: Fri Jan 15 10:16:37 2010 Windows XP Professional Ver 5.1 Build 2600 Service Pack 3 Running in Terminal Service session Path: C:\cygwin\usr\local\bin C:\cygwin\bin C:\cygwin\bin C:\Program Files\Microsoft Office\OFFICE11\ C:\WINDOWS\system32 C:\WINDOWS C:\WINDOWS\System32\Wbem C:\Program Files\Microsoft SQL Server\90\Tools\binn\ C:\Program Files\Common Files\GTK\2.0\bin C:\Program Files\GNU\GnuPG\pub C:\Program Files\QNX Software Systems\bin C:\WINDOWS\system32\WindowsPowerShell\v1.0 F:\QNX641\host\win32\x86\usr\bin Output from C:\cygwin\bin\id.exe UID: 13689(rcampbell)GID: 10513(Domain Users) 0(root) 544(Administrators) 545(Users) 1008(Debugger Users) 10513(Domain Users) SysDir: C:\WINDOWS\system32 WinDir: C:\WINDOWS MAKEFLAGS = '-IF:/QNX641/target/qnx6/usr/include' USER = 'rcampbell' PWD = '/home/rcampbell' HOME = '/home/rcampbell' HOMEPATH = '\Documents and Settings\rcampbell' MANPATH = '/usr/local/man:/usr/share/man:/usr/man::/usr/ssl/man' APPDATA = 'C:\Documents and Settings\rcampbell\Application Data' SSH_AGENT_PID = '3028' HOSTNAME = 'rcampbell' VS71COMNTOOLS = 'C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Tools\' QNX_CONFIGURATION = 'C:\Program Files\QNX Software Systems' TERM = 'xterm' PROCESSOR_IDENTIFIER = 'x86 Family 6 Model 15 Stepping 11, GenuineIntel' WINDIR = 'C:\WINDOWS' QNX_JAVAHOME = 'F:\QNX641\_jvm' OLDPWD = '/usr/bin' USERDOMAIN = 'DRAGONWAVE' OS = 'Windows_NT' ALLUSERSPROFILE = 'C:\Documents and Settings\All Users' !:: = '::\' TEMP = '/tmp' COMMONPROGRAMFILES = 'C:\Program Files\Common Files' LIB = 'C:\Program Files\Microsoft Visual Studio .NET 2003\SDK\v1.1\Lib\' SSH_AUTH_SOCK = '/tmp/ssh-IwBSPf3500/agent.3500' USERNAME = 'rcampbell' PROCESSOR_LEVEL = '6' PSModulePath = 'C:\WINDOWS\system32\WindowsPowerShell\v1.0\Modules\' FP_NO_HOST_CHECK = 'NO' SYSTEMDRIVE = 'C:' LANG = 'C.UTF-8' USERPROFILE = 'C:\Documents and Settings\rcampbell' PS1 = '\[\e]0;\w\a\]\n\[\e[32m\...@\h \[\e[33m\]\w\[\e[0m\]\n\$ ' LOGONSERVER = '\\CLAPTON' PROCESSOR_ARCHITECTURE = 'x86' VISUALSVN_SERVER = 'C:\Program Files\VisualSVN Server\' SHLVL = '1' QNX_TARGET = 'F:/QNX641/target/qnx6' USERDNSDOMAIN = 'DRAGONWAVEINC.COM' PATHEXT = '.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.PSC1' HOMEDRIVE = 'C:' QNX_HOST = 'F:/QNX641/host/win32/x86' COMSPEC = 'C:\WINDOWS\system32\cmd.exe' TMP = '/tmp' SYSTEMROOT = 'C:\WINDOWS' PRINTER = 'Fleury on kermit (from DWI-A2535)' CVS_RSH = '/bin/ssh' PROCESSOR_REVISION = '0f0b' HUDSON_HOME = 'F:/.hudson' INFOPATH = '/usr/local/info:/usr/share/info:/usr/info:' PROGRAMFILES = 'C:\Program Files' NUMBER_OF_PROCESSORS = '2' INCLUDE = 'C:\Program Files\Microsoft Visual Studio .NET 2003\SDK\v1.1\include\' COMPUTERNAME = 'RCAMPBELL' _ = '/usr/bin/cygcheck' HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2 HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2 c__altera_72sp1_quartus_bin_cygwin_bin_cygwin1_dll HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\Program Options HKEY_CURRENT_USER\Software\Cygwin HKEY_CURRENT_USER\Software\Cygwin\Program Options HKEY_CURRENT_USER\Software\Cygwin\setup HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MenuOrder\Start Menu2\Programs\Cygwin (default) = (unsupported type) HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MenuOrder\Start Menu2\Programs\Cygwin-X (default) = (unsupported type) HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2 (default) = '/cygdrive' cygdrive flags = 0x0022 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/ (default) = 'C:\cygwin' flags = 0x000a HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/c (default) = 'C:' flags = 0x000a HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/f (default) = 'F:' flags = 0x000a HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/mp3 (default) = 'F:\mp3' flags = 0x000a HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/share (default) = 'C:\cygwin\home\rcampbell\share' flags = 0x000a
Re: Path problems with libgmpxx.la, libppl.la, libppl_c.la and libcloog-ppl.la - a work around
David Billinghurst wrote: I won't release a fixed set of gmp packages at present as a new upstream release gmp-4.3.2 is imminent (late December 2009). For the moment, affected users will need to edit the installed libgmpxx.la file. The /usr/sbin/fix-libtool-scripts-for-latest-gcc-runtimes.sh script should do this for you. (Note that you'll need to chmod +x it first, owing to a packaging bug). cheers, DaveK -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Windows call SetFileValidData() fails on cygwin 1.5.25-15 usign gcc 3.4.4
On 01/15/2010 07:47 AM, cyg...@riemens.org wrote: Hi all, My aim is to allocate a (large) file on disk and write somewhere at the end without being hit by the performance penalty of zero-filling that NTFS executes by default. Therefore, I try to use SetFileValidData() but this consistently reports windows error 1314 A required privilege is not held by the client. (I am aware of the risks, thanks for your concern). The error occurs on an executable that is compiled under cygwin 1.5.25-15 using gcc version 3.4.4. No error on an exec that is built with MS visual studio .NET 2003. Function SetFileValidData() requires a special privilege SE_MANAGE_VOLUME_NAME that is set in the program. Program lists current priviledges to check that it is actually set; this confirms that the permission is granted. Works just fine with gcc-3 or gcc-4 with Cygwin 1.7. Perhaps you want to upgrade. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: 1.7.1: terminal not passing Ctrl-C to sub-sub cygwin processes
On Fri, Jan 15, 2010 at 05:00:37PM -0500, Rolf Campbell wrote: From within cygwin python, if I call os.system running a cygwin sub-process, and I hit Ctrl-C while that cygwin sub-process is running, the Ctrl-C does nothing (absolutely nothing -- nothing is printed, nothing terminates, no sound is made -- it's as if I didn't press the key at all). I've attached a simple script which easily reproduces the situation. When I run the script as ./ctrlc.py 0, Ctrl-C kill the process, but when I run it with an argument of 1 or more, hitting Ctrl-C has no effect. I have not testing this with anything other than python, but I have a feeling that it's not python related. It probably isn't. From the linux man page: NAME system - execute a shell command SYNOPSIS #include stdlib.h int system(const char *command); DESCRIPTION system() executes a command specified in command by calling /bin/sh -c command, and returns after the command has been completed. During execution of the command, SIGCHLD will be blocked, and SIGINT and SIGQUIT will be ignored. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
cygpath problem on last snapshot
Hi, on latest $ uname -v 20100114 15:57:50 $ cygpath -w / C:\cygwin2 Aborted (core dumped) no problems on the previous 20100101 Regards Marco -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: 1.7.1: terminal not passing Ctrl-C to sub-sub cygwin processes
On 2010-01-15 18:22, Christopher Faylor wrote: On Fri, Jan 15, 2010 at 05:00:37PM -0500, Rolf Campbell wrote: From within cygwin python, if I call os.system running a cygwin sub-process, and I hit Ctrl-C while that cygwin sub-process is running, the Ctrl-C does nothing (absolutely nothing -- nothing is printed, nothing terminates, no sound is made -- it's as if I didn't press the key at all). [snip] It probably isn't. From the linux man page: NAME system - execute a shell command SYNOPSIS #includestdlib.h int system(const char *command); DESCRIPTION system() executes a command specified in command by calling /bin/sh -c command, and returns after the command has been completed. During execution of the command, SIGCHLD will be blocked, and SIGINT and SIGQUIT will be ignored. cgf Thanks for setting me straight. When I change my script to use os.popen, ^C gets propagated to sub-processes. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Problem with gpc on 1.7.1
Yuri Gribov wrote: Here are the symptoms. I try to compile a simple Pascal program (see attach). When it's name is lowercase (say temp.pas) it compiles fine: $ gpc temp.pas temp.pas:0: warning: missing program header but when I change it to uppercase (TEMP.PAS) I get internal compiler error: $ mv temp.pas TEMP.PAS $ gpc TEMP.PAS gpc: Internal GPC problem: internal option `--amtmpfile' not given From info gpc: 5.2 The most commonly used options to GPC = Users familiar with BP, please note that you have to give the file name extension `.pas': GPC is a common interface for a Pascal compiler, a C, ObjC and C++ compiler, an assembler, a linker, and perhaps an Ada and a FORTRAN compiler. From the extension of your source file GPC figures out which compiler to run. GPC recognizes Pascal sources by the extension `.pas', `.p', `.pp' or `.dpr'. GPC also accepts source files in other languages (e.g., `.c' for C) and calls the appropriate compilers for them. Files with the extension `.o' or without any special recognized extension are considered to be object files or libraries to be linked. Note that it is case-sensitive about the extension. TEMP.pas works fine. If you want to use upper-case names, GPC won't recognize them automatically as pascal source files, but you can precede them on the command-line with the -x option in order to specify the language manually: $ gpc TEM.PAS gpc: Internal GPC problem: internal option `--amtmpfile' not given $ gpc -x Pascal TEM.PAS TEM.PAS:0: warning: missing program header This behaviour should be the same on Linux, although I haven't checked. cheers, DaveK -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
New: arj 3.10.22-1 -- archiver for .arj files
PACKAGE DESCRIPTION === Homepage: http://www.sourceforge.net/projects/arj License : GPL An open source version of the arj archiver. This version has been created with the intent to preserve maximum compatibility and retain the feature set of original ARJ archiver as provided by ARJ Software, Inc. CHANGES SINCE LAST RELEASE == See /usr/share/doc/arj-*/rev_hist.txt INSTALL OR UPGRADE NOTES Standard Cygwin install. CYGWIN INSTALLATION INFORMATION === To install this package, click on the Install Cygwin now link on the http://cygwin.com/ web page. This downloads setup.exe to your system. Then, run setup and answer all of the questions. You'll find the package listed in the All category. After installation, read the documentation at directories: /usr/share/doc/package-version/* /usr/share/doc/Cygwin/package-version.README If you have questions or comments, please send them to the Cygwin mailing list at cyg...@cygwin.com. CYGWIN-ANNOUNCE UNSUBSCRIBE INFO This message has been sent to cygwin-announce list. If you want to unsubscribe from the mailing list, look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com More information on unsubscribing can be found: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at the above URL.
