X11 server
I'm trying to install x11 for Windows but the site ask me for a Server Authorization Password Why. Do I have to register something somewhere?? thanks in advance Pietro F. Bianchi SUN Microsystem Italia SpA Project Manager cell.: 335-7683522 mail: pietro.bian...@sun.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/
broken checkx on mirrors
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, just now I tried an update of my CygWin. I realized that checkx-0.2.1-1.tar.bz is broken on all mirrors. Please, can the maintainer correct this? Thanks! - -- Kindest Regards Guenter Millahn -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.12 (MingW32) iQIcBAEBAgAGBQJKUynMAAoJEHJuTLcCOtoFDC8P/3um4TWBgqLBI2PtHcUrbCfa eyO2mahuLe4Ta6TLaPV7u8TW8fe8ULFArWC7vwuvVlnx1AYDH7LdPmTLWHaXpgix m6t08gipg772ZxuPIS7LPO/NOtGk4VG+gH9rYcyFhKi5V+9g1BPsaGjzxWg2SD4y eRG/l3aO8fnmOkmyjIRTjcKvjoIcybFH6qO8mdRbecEDoQH9/qnQbbETtyilfu8d IC9IFu8+u9s/XAJQALs6W2L2EKoYRE9Wb+7k7NAmhG7ajyxnKVvAtXm0ddiqWtuC mNyoLdmPMtLuM6yYzNMzVfg/JqBaOXbgaKGEghCuKoJNIPKH/iquIainaCHeSkdJ HKvSRoswONyQGtKm8dRU6DHvA5gc1hkg/uiXdFMG7KkvJkE3kLwCq+Hg1/bJrOwx 4AM6qgXc7xfo3hF31DZkxLoB09lFcgbWUl9R5+MuZUhhsv3Xd8avbDerZkiJZxBg JnN4TQgMy5wozBDuJ6bYuO+t5y6bVgfKbBxrOuo+h7y6npYwOFfZ4eW5GOZ17Bg5 NKATnzeXZTnTxtQi/p8J+WkCemv/0ownMn0Ky3j85B0lvMu0+Zh3j6/ou6scy7HY DF4hZ/mepBnEDoKKwGubAPqXzyLxqso9/STgu6tRVxz4tLm81lYyIo2MSxJool+Y NiqdR1Q9hBZbBLn5gkOG =gm+E -END PGP SIGNATURE- -- 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: broken checkx on mirrors
On Tue, Jul 07, 2009 at 12:56:12PM +0200, Guenter Millahn wrote: just now I tried an update of my CygWin. I realized that checkx-0.2.1-1.tar.bz is broken on all mirrors. You haven't explained why you think this package is broken. You really need to do that. cgf -- 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: X11 server
Pietro Federico Bianchi wrote: I'm trying to install x11 for Windows but the site ask me for a Server Authorization Password Why. Do I have to register something somewhere?? Cygwin-X requires no authorization password. Please read and follow the problem reporting guidelines found at the URL below. Problem reports: http://cygwin.com/problems.html -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 429-6305 - FAX Holliston, MA 01746 -- 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/
[1.7] XWin still fails with SunOS 10
Greetings. I updated from the old cygwin to the new 1.7 by installing the new 1.7 in c:\cygwinx directory. The reason why was because I wanted to see if a problem that I previously had was fixed with a SunOS 10 server. When I run this command, XWin -once -query IP the X windows opens and quickly disappear. The log is attached. I went to, http://x.cygwin.com/docs/faq/cygwin-x-faq.html and tried to find any hints, but, nothing... By the way, this is the same problem that the previous version of cygwin had. But, since Mr. Turney said to give it a try with the new version, I did. :-) Is this going to ever be fixed? thanks, josé -- 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/
[1.7] XWin still fails with SunOS 10
Greetings. I updated from the old cygwin to the new 1.7 by installing the new 1.7 in c:\cygwinx directory. The reason why was because I wanted to see if a problem that I previously had was fixed with a SunOS 10 server. When I run this command, XWin -once -query IP the X windows opens and quickly disappear. The log is attached. I went to, http://x.cygwin.com/docs/faq/cygwin-x-faq.html and tried to find any hints, but, nothing... By the way, this is the same problem that the previous version of cygwin had. But, since Mr. Turney said to give it a try with the new version, I did. :-) Is this going to ever be fixed? thanks, josé -- 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] XWin still fails with SunOS 10
jose isaias cabrera wrote: snip By the way, this is the same problem that the previous version of cygwin had. But, since Mr. Turney said to give it a try with the new version, I did. :-) Is this going to ever be fixed? Nah. It's been there so long that it feels like an old friend. Getting rid of an old friend would... well, that would just be wrong! And, of course, if you don't agree, you're stuck. After all, we have the source and you don't... wait a minute. Ah, never mind. ;-) -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 429-6305 - FAX Holliston, MA 01746 -- 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] XWin still fails with SunOS 10
Larry Hall (Cygwin X) trying to be funny, wrote... jose isaias cabrera wrote: snip By the way, this is the same problem that the previous version of cygwin had. But, since Mr. Turney said to give it a try with the new version, I did. :-) Is this going to ever be fixed? Nah. It's been there so long that it feels like an old friend. Getting rid of an old friend would... well, that would just be wrong! And, of course, if you don't agree, you're stuck. After all, we have the source and you don't... wait a minute. Ah, never mind. ;-) He he he he... I guess not... son-ovah! I wish I had the time... :-( Anyway, just wanted to try it. By the way, it was funny. :-) josé -- 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/
src/winsup Makefile.common ChangeLog cygwin/Ma ...
CVSROOT:/cvs/src Module name:src Changes by: da...@sourceware.org2009-07-07 20:12:44 Modified files: winsup : Makefile.common ChangeLog winsup/cygwin : Makefile.in cxx.cc cygwin.din globals.cc winsup.h ChangeLog winsup/cygwin/include/cygwin: version.h winsup/cygwin/include/sys: cygwin.h winsup/cygwin/lib: _cygwin_crt0_common.cc Added files: winsup/cygwin : cygwin-cxx.h libstdcxx_wrapper.cc Log message: winsup/ChangeLog: * Makefile.common (COMPILE_CXX): Add support for per-file overrides to exclude $(nostdinc) and $(nostdincxx) from compiler flags. (COMPILE_CC): Likewise for $(nostdinc). winsup/cygwin/ChangeLog: * Makefile.in (DLL_OFILES): Add libstdcxx_wrapper.o (libstdcxx_wrapper_CFLAGS): Add flags for new module. (_cygwin_crt0_common_STDINCFLAGS): Define per-file override. (libstdcxx_wrapper_STDINCFLAGS, cxx_STDINCFLAGS): Likewise. * cxx.cc: Include cygwin-cxx.h. (operator new): Tweak prototype for full standards compliance. (operator new[]): Likewise. (operator new (nothrow)): New fallback function. (operator new[] (nothrow), operator delete (nothrow), operator delete[] (nothrow)): Likewise. (default_cygwin_cxx_malloc): New struct of pointers to the above, for final last-resort fallback default. * cygwin-cxx.h: New file. (struct per_process_cxx_malloc): Define. (default_cygwin_cxx_malloc): Declare extern. * cygwin.din (__wrap__ZdaPv): Export new wrapper. (__wrap__ZdaPvRKSt9nothrow_t, __wrap__ZdlPv, __wrap__ZdlPvRKSt9nothrow_t, __wrap__Znaj, __wrap__ZnajRKSt9nothrow_t, __wrap__Znwj, __wrap__ZnwjRKSt9nothrow_t): Likewise. * globals.cc (__cygwin_user_data): Init newly-repurposed 'forkee' field (now 'cxx_malloc') to point to default_cygwin_cxx_malloc. * libstdcxx_wrapper.cc: New file. (__wrap__ZdaPv, __wrap__ZdaPvRKSt9nothrow_t, __wrap__ZdlPv, __wrap__ZdlPvRKSt9nothrow_t, __wrap__Znaj, __wrap__ZnajRKSt9nothrow_t, __wrap__Znwj, __wrap__ZnwjRKSt9nothrow_t): Define wrapper functions for libstdc++ malloc operators and their overrides. * winsup.h (default_cygwin_cxx_malloc): Declare extern. * include/cygwin/version.h (CYGWIN_VERSION_API_MINOR): Bump. * include/sys/cygwin.h (struct per_process_cxx_malloc): Forward declare here. (struct per_process::forkee): Rename and repurpose from this ... (struct per_process::cxx_malloc): ... to this. * lib/_cygwin_crt0_common.cc: Include cygwin-cxx.h. (WEAK): Define shorthand helper macro. (__cygwin_cxx_malloc): Define and populate with weak references to whatever libstdc++ malloc operators will be visible at final link time for Cygwin apps and dlls. (_cygwin_crt0_common): Always look up cygwin DLL's internal per_process data, and don't test for (impossible) failure. Inherit any members of __cygwin_cxx_malloc that we don't have overrides for from the DLL's default and store the resulting overall set of overrides back into the DLL's global per_process data. Patches: http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/Makefile.common.diff?cvsroot=srcr1=1.55r2=1.56 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/ChangeLog.diff?cvsroot=srcr1=1.105r2=1.106 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/cygwin-cxx.h.diff?cvsroot=srcr1=NONEr2=1.1 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/libstdcxx_wrapper.cc.diff?cvsroot=srcr1=NONEr2=1.1 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/Makefile.in.diff?cvsroot=srcr1=1.227r2=1.228 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/cxx.cc.diff?cvsroot=srcr1=1.4r2=1.5 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/cygwin.din.diff?cvsroot=srcr1=1.213r2=1.214 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/globals.cc.diff?cvsroot=srcr1=1.2r2=1.3 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/winsup.h.diff?cvsroot=srcr1=1.228r2=1.229 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/ChangeLog.diff?cvsroot=srcr1=1.4559r2=1.4560 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/include/cygwin/version.h.diff?cvsroot=srcr1=1.296r2=1.297 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/include/sys/cygwin.h.diff?cvsroot=srcr1=1.79r2=1.80 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/lib/_cygwin_crt0_common.cc.diff?cvsroot=srcr1=1.16r2=1.17
src/winsup/cygwin ChangeLog
CVSROOT:/cvs/src Module name:src Changes by: da...@sourceware.org2009-07-07 20:25:34 Modified files: winsup/cygwin : ChangeLog Log message: * ChangeLog: Assorted minor whitespace fixes in old entries. Patches: http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/ChangeLog.diff?cvsroot=srcr1=1.4560r2=1.4561
src/winsup/cygwin winbase.h ChangeLog
CVSROOT:/cvs/src Module name:src Changes by: da...@sourceware.org2009-07-07 21:41:43 Modified files: winsup/cygwin : winbase.h ChangeLog Log message: * winbase.h (ilockexch): Avoid making 'ret' volatile. (ilockcmpexch): Likewise. Patches: http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/winbase.h.diff?cvsroot=srcr1=1.15r2=1.16 http://sources.redhat.com/cgi-bin/cvsweb.cgi/src/winsup/cygwin/ChangeLog.diff?cvsroot=srcr1=1.4561r2=1.4562
[PATCH] Libstdc++ support changes.
Hi all, I just got done doing a C/C++/libstdc++-v3 test run against GCC HEAD using the Cygwin DLL built with these patches, and everything worked. In particular, it passed these tests: FAIL: g++.old-deja/g++.abi/cxa_vec.C execution test FAIL: g++.old-deja/g++.brendan/new3.C execution test ... which fail on current 4.3.2-2 using shared libstdc++ DLL precisely because they expect to be able to interpose libstdc++'s own internal calls to the allocation operators. I've also been using it in daily use (and before that, the previous spin of this patch) for a while now and nothing unusual has been showing up. I'm now busy packaging a version of gcc-4.3.3 that will incorporate the necessary support to make this work, and though that'll be another few days testing, it's not going to need anything different by way of support from the Cygwin DLL, so I reckon this is ready for primetime. Re: the last outstanding issues we discussed; I decided not to try and fold the malloc handling into this. The malloc wrappers work without needing compiler support, and we can do that because we are the libc and we own malloc. That isn't the same as for the C++ operators, and I don't think we should conflate parts of libstdc++ into the Cygwin DLL. For that reason, I figured we shouldn't export ONDEE directly, even weakly, and that leaves us just the option of ld wrappers. Given that C++ is big and complex and requires the whole toolchain to be aware anyway, I think that's an acceptable compromise, but malloc and friends are plain old C and someone might even want to call them from assembly, and I didn't see it was worth adding complexity and fragility. The second idea was representing the pointers as an array somehow to make extending it in future easier. I had a quick go, but it gets pretty ugly pretty quickly when you try and union them against an array of PVOIDs or whatever, because you can't statically initialise a union, so you end up only declaring the struct and then having to cast it to a union in other places. I don't suppose extending this mechanism in future is terribly likely; it exists to support the requirements of the C++ spec, and that's not likely to start specifying any new function replacements anytime foreseeable. winsup/ChangeLog: * Makefile.common (COMPILE_CXX): Add support for per-file overrides to exclude $(nostdinc) and $(nostdincxx) from compiler flags. (COMPILE_CC): Likewise for $(nostdinc). winsup/cygwin/ChangeLog: * Makefile.in (DLL_OFILES): Add libstdcxx_wrapper.o (libstdcxx_wrapper_CFLAGS): Add flags for new module. (_cygwin_crt0_common_STDINCFLAGS): Define per-file override. (libstdcxx_wrapper_STDINCFLAGS, cxx_STDINCFLAGS): Likewise. * cxx.cc: Include cygwin-cxx.h. (operator new): Tweak prototype for full standards compliance. (operator new[]): Likewise. (operator new (nothrow)): New fallback function. (operator new[] (nothrow), operator delete (nothrow), operator delete[] (nothrow)): Likewise. (default_cygwin_cxx_malloc): New struct of pointers to the above, for final last-resort fallback default. * cygwin-cxx.h: New file. (struct per_process_cxx_malloc): Define. (default_cygwin_cxx_malloc): Declare extern. * cygwin.din (__wrap__ZdaPv): Export new wrapper. (__wrap__ZdaPvRKSt9nothrow_t, __wrap__ZdlPv, __wrap__ZdlPvRKSt9nothrow_t, __wrap__Znaj, __wrap__ZnajRKSt9nothrow_t, __wrap__Znwj, __wrap__ZnwjRKSt9nothrow_t): Likewise. * globals.cc (__cygwin_user_data): Init newly-repurposed 'forkee' field (now 'cxx_malloc') to point to default_cygwin_cxx_malloc. * libstdcxx_wrapper.cc: New file. (__wrap__ZdaPv, __wrap__ZdaPvRKSt9nothrow_t, __wrap__ZdlPv, __wrap__ZdlPvRKSt9nothrow_t, __wrap__Znaj, __wrap__ZnajRKSt9nothrow_t, __wrap__Znwj, __wrap__ZnwjRKSt9nothrow_t): Define wrapper functions for libstdc++ malloc operators and their overrides. * winsup.h (default_cygwin_cxx_malloc): Declare extern. * include/cygwin/version.h (CYGWIN_VERSION_API_MINOR): Bump. * include/sys/cygwin.h (struct per_process_cxx_malloc): Forward declare here. (struct per_process::forkee): Rename and repurpose from this ... (struct per_process::cxx_malloc): ... to this. * lib/_cygwin_crt0_common.cc: Include cygwin-cxx.h. (WEAK): Define shorthand helper macro. (__cygwin_cxx_malloc): Define and populate with weak references to whatever libstdc++ malloc operators will be visible at final link time for Cygwin apps and dlls. (_cygwin_crt0_common): Always look up cygwin DLL's internal per_process data, and don't test for (impossible) failure. Inherit any members of __cygwin_cxx_malloc that we don't have overrides for from
Re: [PATCH] Libstdc++ support changes.
Hi Dave, Thanks for doing that stuff! On Jul 7 17:22, Dave Korn wrote: Hi all, I just got done doing a C/C++/libstdc++-v3 test run against GCC HEAD using the Cygwin DLL built with these patches, and everything worked. In particular, it passed these tests: FAIL: g++.old-deja/g++.abi/cxa_vec.C execution test FAIL: g++.old-deja/g++.brendan/new3.C execution test ... which fail on current 4.3.2-2 using shared libstdc++ DLL precisely because they expect to be able to interpose libstdc++'s own internal calls to the allocation operators. I've also been using it in daily use (and before that, the previous spin of this patch) for a while now and nothing unusual has been showing up. [...] This looks pretty good to me. I have just two formal nits. In the ChangeLogs, * Makefile.common (COMPILE_CXX): Add support for per-file overrides please use just one space after the colon. At some points you're using different comment types rather freely. Here's an example. Index: winsup/cygwin/libstdcxx_wrapper.cc === RCS file: winsup/cygwin/libstdcxx_wrapper.cc diff -N winsup/cygwin/libstdcxx_wrapper.cc --- /dev/null 1 Jan 1970 00:00:00 - +++ winsup/cygwin/libstdcxx_wrapper.cc7 Jul 2009 15:21:57 - @@ -0,0 +1,91 @@ +/* libstdcxx_wrapper.cc + + Copyright 2009 Red Hat, Inc. + +This file is part of Cygwin. + +This software is a copyrighted work licensed under the terms of the +Cygwin license. Please consult the file CYGWIN_LICENSE for +details. */ ^ That's ok. + + +/* We provide these stubs to call into a user's + provided ONDEE replacement if there is one - otherwise + it must fall back to the standard libstdc++ version. +*/ ^ The comment closing */ should be at the end of the last line of comment, rather than starting a new line. +#include winsup.h +#include cygwin-cxx.h +#include perprocess.h + +// We are declaring asm names for the functions we define here, as we want +// to define the wrappers in this file. GCC links everything with wrappers +// around the standard C++ memory management operators; these are the wrappers, +// but we want the compiler to know they are the malloc operators and not have +// it think they're just any old function matching 'extern C _wrap_*'. ^ While we have a couple of // comments in Cygwin, it would be nice to at least don't use them for multiline comments and comments on their own line. Use /* This is a comment. */ /* This is another comment. */ instead. Other than that it looks like you tested this a lot so it's fine with me. Maybe Chris has some additional comment. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: [PATCH] Libstdc++ support changes.
Corinna Vinschen wrote: In the ChangeLogs, please use just one space after the colon. Sure. At some points you're using different comment types rather freely. Other than that it looks like you tested this a lot so it's fine with me. Maybe Chris has some additional comment. I'll be tidying the comments up while we wait. (Ooh. Thunder. May have to go AFK for a while if it gets closer and zappy.) cheers, DaveK
Re: [PATCH] Libstdc++ support changes.
On Tue, Jul 07, 2009 at 07:18:58PM +0200, Corinna Vinschen wrote: Hi Dave, Thanks for doing that stuff! On Jul 7 17:22, Dave Korn wrote: Hi all, I just got done doing a C/C++/libstdc++-v3 test run against GCC HEAD using the Cygwin DLL built with these patches, and everything worked. In particular, it passed these tests: FAIL: g++.old-deja/g++.abi/cxa_vec.C execution test FAIL: g++.old-deja/g++.brendan/new3.C execution test ... which fail on current 4.3.2-2 using shared libstdc++ DLL precisely because they expect to be able to interpose libstdc++'s own internal calls to the allocation operators. I've also been using it in daily use (and before that, the previous spin of this patch) for a while now and nothing unusual has been showing up. [...] This looks pretty good to me. I have just two formal nits. In the ChangeLogs, * Makefile.common (COMPILE_CXX): Add support for per-file overrides please use just one space after the colon. At some points you're using different comment types rather freely. Here's an example. Index: winsup/cygwin/libstdcxx_wrapper.cc === RCS file: winsup/cygwin/libstdcxx_wrapper.cc diff -N winsup/cygwin/libstdcxx_wrapper.cc --- /dev/null1 Jan 1970 00:00:00 - +++ winsup/cygwin/libstdcxx_wrapper.cc 7 Jul 2009 15:21:57 - @@ -0,0 +1,91 @@ +/* libstdcxx_wrapper.cc + + Copyright 2009 Red Hat, Inc. + +This file is part of Cygwin. + +This software is a copyrighted work licensed under the terms of the +Cygwin license. Please consult the file CYGWIN_LICENSE for +details. */ ^ That's ok. + + +/* We provide these stubs to call into a user's + provided ONDEE replacement if there is one - otherwise + it must fall back to the standard libstdc++ version. +*/ ^ The comment closing */ should be at the end of the last line of comment, rather than starting a new line. +#include winsup.h +#include cygwin-cxx.h +#include perprocess.h + +// We are declaring asm names for the functions we define here, as we want +// to define the wrappers in this file. GCC links everything with wrappers +// around the standard C++ memory management operators; these are the wrappers, +// but we want the compiler to know they are the malloc operators and not have +// it think they're just any old function matching 'extern C _wrap_*'. ^ While we have a couple of // comments in Cygwin, it would be nice to at least don't use them for multiline comments and comments on their own line. Use /* This is a comment. */ /* This is another comment. */ instead. Other than that it looks like you tested this a lot so it's fine with me. Maybe Chris has some additional comment. Nope. I noticed the comment style too (and missed the two spaces after the colon). Obviously not a big deal but it would be nice to have them consistent. cgf
Re: [PATCH] Re: 1.7 winbase.h (ilockcmpexch) compile error
On Tue, Jul 07, 2009 at 10:21:33PM +0100, Dave Korn wrote: Brian Ford wrote: I'm trying to build Cygwin 1.7 from CVS to debug an ImageMagick problem on server 2008 that causes an access violation in cygwin1.dll. Doe anyone know the work around for this issue? g++ (GCC) 3.4.4 (cygming special, gdc 0.12, using dmd 0.125) winsup/cygwin/winbase.h: In member function `int pthread_mutex::_trylock(pthread*)': winsup/cygwin/winbase.h:59: warning: volatile register variables don't work as you might wish winsup/cygwin/winbase.h:63: error: can't find a register in class `AREG' while reloading `asm' The attached patch fixes the warning about volatile register variables, by explicitly specifying the type, instead of using typeof() the input parameter (which inherits the volatility), and which I also saw using gcc HEAD the other day. It doesn't do anything about the reload failure, which is a bug in GCC-3, since the usage is a standard usage supported by the documentation. It's possible that it may disappear as a side-effect, in which case all the better. (I experimented briefly with removing the register asm from the source and building it with gcc-4.3.2, and the results were disappointing; we actually got worse register allocation, resulting in some functions having larger stack frames and more registers saved/restored, so I guess the RA can still benefit from the extra hint.) Tested by building thread.o and shared.o with CFLAGS=-g -O2 --save-temps before and after and comparing the generated .s file; no differences except in debug info, where (naturally) a bunch of bits changed in the flag words encoding the datatypes of variables. winsup/cygwin/ChangeLog: * winbase.h (ilockexch): Avoid making 'ret' volatile. (ilockcmpexch): Likewise. Ok? Yes. Thanks. cgf
Re: [PATCH] Re: 1.7 winbase.h (ilockcmpexch) compile error
Christopher Faylor wrote: On Tue, Jul 07, 2009 at 10:21:33PM +0100, Dave Korn wrote: winsup/cygwin/ChangeLog: * winbase.h (ilockexch): Avoid making 'ret' volatile. (ilockcmpexch): Likewise. Ok? Yes. Thanks. Applied, and I even caught the changelog formatting in time! cheers, DaveK
Re: [PATCH] Re: 1.7 winbase.h (ilockcmpexch) compile error
On Tue, Jul 07, 2009 at 10:55:13PM +0100, Dave Korn wrote: Christopher Faylor wrote: On Tue, Jul 07, 2009 at 10:21:33PM +0100, Dave Korn wrote: winsup/cygwin/ChangeLog: * winbase.h (ilockexch): Avoid making 'ret' volatile. (ilockcmpexch): Likewise. Ok? Yes. Thanks. Applied, and I even caught the changelog formatting in time! I think I may have to turn in my Anal Whitespace Enforcer badge. cgf
Re: [PATCH] Re: 1.7 winbase.h (ilockcmpexch) compile error
Dave Korn wrote: It doesn't do anything about the reload failure, which is a bug in GCC-3, since the usage is a standard usage supported by the documentation. It's possible that it may disappear as a side-effect, in which case all the better. Nope, no such luck. Also, the libstdc++ patch has really done for compiling it with gcc-3, which doesn't support the weak attribute. It also has a bug that for some reason two of the wrapper functions in libstdcxx_malloc.cc are emitted under their real names, rather than the asm(__real__*) name specified. There's also the inline asm bug and there's a number of other warnings about type conversions. All of these could in theory be worked around. We could compile the files using the inline asm with -O0, and fix the type conversion warnings(*), and we would have to work around the lack of support for weaks in the compiler by providing the definition of the __cygwin_cxx_malloc struct in assembler source, and probably the same for the wrapper function names, but I'm not inclined to do so unless there's serious demand for it. cheers, DaveK -- (*) - actually, I'll send patches for those anyway.
Re: setrlimit(RLIMIT_CPU) isn't implemented in Cygwin., Corinna Vinschen
--- I asked: Will it be implemented in Cygwin someday? --- Dave Korn replied: Otherwise, http://cygwin.com/acronyms#SHTDI and http://cygwin.com/acronyms#PTC apply here. I imagine it should be possible to use a windows job object to implement it. --- Corinna Vinschen replied: There are no plans to implement it in the near future. Are contributors asked to sign any paper? If I contribute it, will my name appear in the .cc file? Must my e-mail appear with my name? -- 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: Successful build of ssh from openssh w. MIT kerberos
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 ht writes: There's been a lot of interest in this over the years, but I've found no reports of success. The following involves a number of hacks, but it works, which may be of use to some. 1) Download and install MIT Kerberos for Windows -- I used kfw-3-2-2.exe Oops, forgot one required patch to the MIT -- follows inline (attachment blocked???) ht - -clip here--- *** krb5/win-mac.h~ Fri Mar 30 01:54:58 2007 - --- krb5/win-mac.h Mon Jul 6 18:12:31 2009 *** *** 76,83 typedef unsigned int u_int; typedef unsigned short u_short; typedef unsigned char u_char; ! typedef unsigned int uint32_t; ! typedef int int32_t; #if _INTEGRAL_MAX_BITS = 64 typedef unsigned __int64 uint64_t; typedef __int64 int64_t; - --- 76,83 typedef unsigned int u_int; typedef unsigned short u_short; typedef unsigned char u_char; ! /*typedef unsigned int uint32_t; ! typedef int int32_t;*/ #if _INTEGRAL_MAX_BITS = 64 typedef unsigned __int64 uint64_t; typedef __int64 int64_t; *** *** 89,95 #ifdef _WIN64 typedef __int64ssize_t; #else ! typedef _W64 int ssize_t; #endif #define SSIZE_T_DEFINED #endif - --- 89,95 #ifdef _WIN64 typedef __int64ssize_t; #else ! /*typedef _W64 int ssize_t;*/ #endif #define SSIZE_T_DEFINED #endif - --clip here - -- Henry S. Thompson, School of Informatics, University of Edinburgh Half-time member of W3C Team 10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440 Fax: (44) 131 651-1426, e-mail: h...@inf.ed.ac.uk URL: http://www.ltg.ed.ac.uk/~ht/ [mail really from me _always_ has this .sig -- mail without it is forged spam] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFKUv/vkjnJixAXWBoRAgQ5AJ9UCVVtefuvfsnqUpiR+CbFy7lAfQCePfDS HVTTk5qNO+G0wa1XZNn2h4k= =xqxa -END PGP SIGNATURE- -- 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: setrlimit(RLIMIT_CPU) isn't implemented in Cygwin., Corinna Vinschen
On Jul 7 04:14, Pedro Izecksohn wrote: --- I asked: Will it be implemented in Cygwin someday? --- Dave Korn replied: Otherwise, http://cygwin.com/acronyms#SHTDI and http://cygwin.com/acronyms#PTC apply here. I imagine it should be possible to use a windows job object to implement it. --- Corinna Vinschen replied: There are no plans to implement it in the near future. Are contributors asked to sign any paper? Yes, see http://cygwin.com/contrib.html, especially the Before you get started section. For Cygwin and the Cygwin tools the copyright for your code changes has to be assigned to Red Hat. If I contribute it, will my name appear in the .cc file? Your choice. I, for one, don't put my name into the source files anymore. Must my e-mail appear with my name? Your name and your email address appear in the ChangeLog files. 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: ssh-host-config now involves cygwin-service-installation-helper.sh
On Jul 6 15:38, Christoph Herdeg wrote: Hello, we're deploying an unattended installation of Cygwin to some of our testmachines. On goal is to have SSH access to those machines, so we put a customizing script to /etc\profile.d which then runs at 1st start involving the command ssh-host-config -y -c tty ntsec -w $RANDOM_PASS. Every summer or so, we're used to update our package - again this year. But all at once on systems with Server 2003, Vista or Server 2008 ssh-host-config now stops and requests the name of a privileged user instead of as before simply creating a privileged user sshd_server with the given password. After doing some checks we found that latterly cygwin-service-installation-helper.sh is involved in the process. Why? My personal opinion: If I give ssh-host-config the parameter -y, the process shouldn't be like: The new ssh-host-config script used for OpenSSH 5.2p1-3 in the Cygwin 1.7 release area doesn't have that problem anymore. 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: Successful build of ssh from openssh w. MIT kerberos
On Jul 6 17:30, Henry S. Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 There's been a lot of interest in this over the years, but I've found no reports of success. The following involves a number of hacks, but it works, which may be of use to some. dream What would be *really* cool: Somebody volunteering as Cygwin package maintainer for a Kerberos 5 package. /dream 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: Really dumb setup question.
Mark J. Reed wrote: On Fri, Jul 3, 2009 at 6:31 PM, Dave Korn wrote: Yep; click on Keep first thing of all, that makes setup keep all your current choices, then manually choose the new version of the particular file you want. Should get a warning if there's any unsatisfied dependencies, otherwise everything should just work. Hm, I could swear I cycled around all the possible top-level choices and didn't see Keep. Maybe because I'd already selected something? It's not one of the view modes, it's one of the radio buttons next to the view mode! Here: |---+-+-+-+--++-| |Search | | |Clear| o Keep o Prev o Curr o Exp |View| Category| |---+-+-+-+--++-| Keep sets all the selections so that the currently-installed version is selected. After doing this, if you clicked Next straight away, nothing would need to be installed. Prev sets all packages to their one-step-back versions. I'm not sure how useful it would ever be to downgrade every package at once, rather than just a specific one you were having problems with, but there it is if you want it. Curr sets all packages to the current release versions available on the servers. This is the normal mode: any packages you're already up-to-date with will be left alone, any packages that newer versions are available on the server will get upgraded. Exp sets any packages that have experimental versions available to those versions. Everything else gets left alone, i.e. it's as if the default was Keep (not Curr) for everything without an experimental version. I'm not entirely sure why these are modal radio buttons, as they seem to me more like one-shot effects of the kind you'd expect a pushbutton to have, you click it and it sets a bunch of package versions, but I think it's because the mode you've selected affects how dependency interactions have to be handled if you go and start altering individual selections after choosing the mode. 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: setrlimit(RLIMIT_CPU) isn't implemented in Cygwin., Corinna Vinschen
On Tue, Jul 07, 2009 at 04:14:49AM -0300, Pedro Izecksohn wrote: --- I asked: Will it be implemented in Cygwin someday? --- Dave Korn replied: Otherwise, http://cygwin.com/acronyms#SHTDI and http://cygwin.com/acronyms#PTC apply here. I imagine it should be possible to use a windows job object to implement it. --- Corinna Vinschen replied: There are no plans to implement it in the near future. Are contributors asked to sign any paper? You might want to peruse: http://cygwin.com/contrib.html If I contribute it, will my name appear in the .cc file? Must my e-mail appear with my name? If you are making a change to an existing file then I don't think it is appropriate to add your name. With maybe a couple of exceptions we just haven't done that. Sometimes people add their names to new files but if the file is part of the Cygwin DLL and not a standalone app, I don't think it makes sense to personalize it. 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
Installed Cygwin 1.7 - no X?
Installed Cygwin 1.7 beta on a new clean machine - figured I may as well get with the 1.7 program. Let it install all defaults plus a few packages I knew I'd need. Added to default list, didn't remove anything. Installed on C:\cygwin under Windows XP SP2. How to start X? No XWin Server icon in menu. Just the cygwin shell server on desktop. No /usr/bin/startxwin.bat script. No /usr/bin/ Xwin.exe. And no xinit, which I thought was how X 7.4 got started. /usr/include/X11 has header files. /usr/lib/X11 is pretty much empty, bar the config/ dir. Looked in /usr/bin/X11R6. Nothing there bar run.exe. Which figures, since that should be history with the 7.4 install. But why is run.exe there as well as in /usr/bin? Went through new FAQ and userguide and changes/features. No help. Did the beta munge the X install? thanks, L. http://info.surrey.ac.uk/Personal/L.Wood/l.w...@surrey.ac.uk -- 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: Successful build of ssh from openssh w. MIT kerberos
Corinna Vinschen wrote: On Jul 6 17:30, Henry S. Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 There's been a lot of interest in this over the years, but I've found no reports of success. The following involves a number of hacks, but it works, which may be of use to some. dream What would be *really* cool: Somebody volunteering as Cygwin package maintainer for a Kerberos 5 package. /dream Corinna. Corinna! Wake up. You're having a dream. ;-) -- 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: Installed Cygwin 1.7 - no X?
Lloyd Wood wrote: Installed Cygwin 1.7 beta on a new clean machine - figured I may as well get with the 1.7 program. Let it install all defaults plus a few packages I knew I'd need. Added to default list, didn't remove anything. You don't get X by default, it's huge. Rerun setup and choose it manually. 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: Installed Cygwin 1.7 - no X?
Lloyd Wood wrote: Installed Cygwin 1.7 beta on a new clean machine - figured I may as well get with the 1.7 program. Let it install all defaults plus a few packages I knew I'd need. Added to default list, didn't remove anything. Installed on C:\cygwin under Windows XP SP2. How to start X? No XWin Server icon in menu. Just the cygwin shell server on desktop. No /usr/bin/startxwin.bat script. No /usr/bin/Xwin.exe. And no xinit, which I thought was how X 7.4 got started. My installation has a XWin Server menu item under Cygwin-X in the Programs menu. /usr/include/X11 has header files. /usr/lib/X11 is pretty much empty, bar the config/ dir. Looked in /usr/bin/X11R6. Nothing there bar run.exe. Which figures, since that should be history with the 7.4 install. But why is run.exe there as well as in /usr/bin? Went through new FAQ and userguide and changes/features. No help. Did the beta munge the X install? WFM. I'd first point you at the problem reporting guidelines at the URL below: Problem reports: http://cygwin.com/problems.html I wouldn't have to ask this next question otherwise - did you install X? It's probably best to answer that with the cygwcheck output mentioned at the URL above. Since your questions hinge on whether X is installed or not, it does fall into the category of something that's appropriate for the main list. However, Cygwin-X has its own list for all things X and Cygwin, for future reference. You can ask Cygwin-X questions there and/or search the archives. -- 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: Installed Cygwin 1.7 - no X?
Larry, On Tue, Jul 7, 2009 at 9:37 AM, Larry Hall (Cygwin)reply-to-list-only...@cygwin.com wrote: Lloyd Wood wrote: Installed Cygwin 1.7 beta on a new clean machine - figured I may as well get with the 1.7 program. Let it install all defaults plus a few packages I knew I'd need. Added to default list, didn't remove anything. Installed on C:\cygwin under Windows XP SP2. How to start X? No XWin Server icon in menu. Just the cygwin shell server on desktop. No /usr/bin/startxwin.bat script. No /usr/bin/Xwin.exe. And no xinit, which I thought was how X 7.4 got started. My installation has a XWin Server menu item under Cygwin-X in the Programs menu. I had a similar issue. If you do a from scratch install recently, you do not get the XWin Server under Cygwin-X. For my install I did install the x windows, and can start from startx in the shell or the startxwin.bat, just no menu item. -Bill -- 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: Installed Cygwin 1.7 - no X?
On Tue, Jul 07, 2009 at 10:51:26AM -0700, William Deegan wrote: Larry, On Tue, Jul 7, 2009 at 9:37 AM, Larry Hall (Cygwin)reply-to-list-only...@cygwin.com wrote: Lloyd Wood wrote: Installed Cygwin 1.7 beta on a new clean machine - figured I may as well get with the 1.7 program. Let it install all defaults plus a few packages I knew I'd need. Added to default list, didn't remove anything. Installed on C:\cygwin under Windows XP SP2. How to start X? No XWin Server icon in menu. Just the cygwin shell server on desktop. No /usr/bin/startxwin.bat script. No /usr/bin/Xwin.exe. And no xinit, which I thought was how X 7.4 got started. My installation has a XWin Server menu item under Cygwin-X in the Programs menu. I had a similar issue. If you do a from scratch install recently, you do not get the XWin Server under Cygwin-X. For my install I did install the x windows, and can start from startx in the shell or the startxwin.bat, just no menu item. ...and if you were reading the cygwin-xfree mailing list you might have caught the recent discussion about this. cgf (who wonders if he should make good on this threat to merge the cygwin-xfree and cygwin mailing lists) -- 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: Installed Cygwin 1.7 - no X?
2009/7/7 William Deegan: If you do a from scratch install recently, you do not get the XWin Server under Cygwin-X. For my install I did install the x windows, and can start from startx in the shell or the startxwin.bat, just no menu item. Known issue: http://article.gmane.org/gmane.os.cygwin.xfree/19682 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
Questions about setting the CYGWIN env. variable's 'error_start'
Mon, 6 Jul 2009 11:21:14 -0400 , Christopher Faylor wrote: For the curious, I debugged it by doing this: set CYWGIN=error_start:gdb When gdb popped up, the stack trace led me straight to the problem. Thanks for the reminder. Here is the documentation for the 'error_start' option: http://cygwin.com/cygwin-ug-net/using-cygwinenv.html or, http://cygwin.com/1.7/cygwin-ug-net/using-cygwinenv.html |error_start:Win32filepath| - if set, runs |Win32filepath| when cygwin encounters a fatal error, which is useful for debugging. |Win32filepath| is usually set to the path to *gdb* or *dumper*, for example |C:\cygwin\bin\gdb.exe|. There is no default set. Is there a canonical or recommended, robust method that should be used for setting 'error_start'? It appears that your method assumes the value of PATH is set appropriately. Is it recommended that users define the environment variable 'Win32filepath' to have the value of the Windows location of the desired debugger and, if so, can this be changed dynamically? (That is, if a user changes 'Win32filepath' at, say, a shell prompt, would this be picked up by 'error_start'?) And has the new 'insight' GUI included with 'gdb' been tested to work as a value for 'error_start'? -- 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] fifo regression
On Mon, Jul 06, 2009 at 10:18:39PM -0400, Christopher Faylor wrote: On Mon, Jul 06, 2009 at 07:03:11AM -0600, Eric Blake wrote: But on cygwin 1.7, when you attempt to create multiple writers to a single fifo, the second writer creates an fd just fine but then fails on any attempt to write to that fd: I see the problem but I don't know how to fix it yet. It may be a couple of days before I can come up with a solution. Just an update: I now have a headache. Thanks again Microsoft for making it all so complicated. This is YA example of a feature (Windows Named Pipes) which behave 98% of the way you'd expect it to work. The 2% is the killer. 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: Installed Cygwin 1.7 - no X?
CGF, On Tue, Jul 7, 2009 at 10:59 AM, Christopher Faylorcgf-use-the-mailinglist-ple...@cygwin.com wrote: On Tue, Jul 07, 2009 at 10:51:26AM -0700, William Deegan wrote: Larry, On Tue, Jul 7, 2009 at 9:37 AM, Larry Hall (Cygwin)reply-to-list-only...@cygwin.com wrote: Lloyd Wood wrote: Installed Cygwin 1.7 beta on a new clean machine - figured I may as well get with the 1.7 program. Let it install all defaults plus a few packages I knew I'd need. Added to default list, didn't remove anything. Installed on C:\cygwin under Windows XP SP2. How to start X? No XWin Server icon in menu. Just the cygwin shell server on desktop. No /usr/bin/startxwin.bat script. No /usr/bin/Xwin.exe. And no xinit, which I thought was how X 7.4 got started. My installation has a XWin Server menu item under Cygwin-X in the Programs menu. I had a similar issue. If you do a from scratch install recently, you do not get the XWin Server under Cygwin-X. For my install I did install the x windows, and can start from startx in the shell or the startxwin.bat, just no menu item. ...and if you were reading the cygwin-xfree mailing list you might have caught the recent discussion about this. My Bad. I filter cygwin-x and cygwin into same folder.. Somehow I missed the reply. cgf (who wonders if he should make good on this threat to merge the cygwin-xfree and cygwin mailing lists) Probably. -Bill -- 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: Questions about setting the CYGWIN env. variable's 'error_start'
Thanks for the reminder. Here is the documentation for the 'error_start' option: http://cygwin.com/cygwin-ug-net/using-cygwinenv.html or, http://cygwin.com/1.7/cygwin-ug-net/using-cygwinenv.html |error_start:Win32filepath| - if set, runs |Win32filepath| when cygwin encounters a fatal error, which is useful for debugging. |Win32filepath| is usually set to the path to *gdb* or *dumper*, for example |C:\cygwin\bin\gdb.exe|. There is no default set. Is there a canonical or recommended, robust method that should be used for setting 'error_start'? It appears that your method assumes the value of PATH is set appropriately. Is it recommended that users define the environment variable 'Win32filepath' to have the value of the Windows location of the desired debugger and, if so, can this be changed dynamically? (That is, if a user changes 'Win32filepath' at, say, a shell prompt, would this be picked up by 'error_start'?) And has the new 'insight' GUI included with 'gdb' been tested to work as a value for 'error_start'? To follow up, the behavior of Cygwin (bash?) is different depending on whether cygwin 1.5 or cygwin 1.7 is used. The environment variable 'Win32filepath' is null for some reason in Cygwin 1.5 (the value has been set via the Environment Variables applet in the Control Panel's System applet). 1. Cygwin 1.5: bash --norc --noprofile bash-3.2$ echo $CYGWIN tty error_start:Win32filepath bash-3.2$ echo $Win32filepath [no value printed] bash-3.2$ /bin/cygcheck -c bash cygwin Cygwin Package Information Package Version Status bash3.2.49-22OK cygwin1.5.25-15 OK 2. Cygwin 1.7: bash --norc --noprofile bash-3.2$ echo $CYGWIN tty error_start:Win32filepath bash-3.2$ echo $Win32filepath c:\cygwin-1.7\bin\gdb.exe bash-3.2$ /bin/cygcheck -c bash cygwin Cygwin Package Information Package Version Status bash3.2.49-23OK cygwin1.7.0-50 OK -- 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: Questions about setting the CYGWIN env. variable's 'error_start'
On Tue, Jul 07, 2009 at 02:33:38PM -0400, Mark Harig wrote: Thanks for the reminder. Here is the documentation for the 'error_start' option: http://cygwin.com/cygwin-ug-net/using-cygwinenv.html or, http://cygwin.com/1.7/cygwin-ug-net/using-cygwinenv.html |error_start:Win32filepath| - if set, runs |Win32filepath| when cygwin encounters a fatal error, which is useful for debugging. |Win32filepath| is usually set to the path to *gdb* or *dumper*, for example |C:\cygwin\bin\gdb.exe|. There is no default set. Is there a canonical or recommended, robust method that should be used for setting 'error_start'? It appears that your method assumes the value of PATH is set appropriately. Is it recommended that users define the environment variable 'Win32filepath' to have the value of the Windows location of the desired debugger and, if so, can this be changed dynamically? (That is, if a user changes 'Win32filepath' at, say, a shell prompt, would this be picked up by 'error_start'?) And has the new 'insight' GUI included with 'gdb' been tested to work as a value for 'error_start'? To follow up, the behavior of Cygwin (bash?) is different depending on whether cygwin 1.5 or cygwin 1.7 is used. The environment variable 'Win32filepath' is null for some reason in Cygwin 1.5 (the value has been set via the Environment Variables applet in the Control Panel's System applet). You're misreading the documentation. Cygwin doesn't do anything with an environment variable called Win32filepath. That's a placeholder like Your Name Here. I have the cygwin bin directory in my windows path so I really did do what I said in the original post: set CYGWIN=error_start:gdb If you want a more precise way of getting to gdb then: set CYGWIN=error_start:c:\cygwin\bin\gdb.exe 1. Cygwin 1.5: bash --norc --noprofile bash-3.2$ echo $CYGWIN tty error_start:Win32filepath bash-3.2$ echo $Win32filepath [no value printed] bash-3.2$ /bin/cygcheck -c bash cygwin Cygwin Package Information Package Version Status bash3.2.49-22OK cygwin1.5.25-15 OK 2. Cygwin 1.7: bash --norc --noprofile bash-3.2$ echo $CYGWIN tty error_start:Win32filepath bash-3.2$ echo $Win32filepath c:\cygwin-1.7\bin\gdb.exe bash-3.2$ /bin/cygcheck -c bash cygwin Cygwin Package Information Package Version Status bash3.2.49-23OK cygwin1.7.0-50 OK I don't know why you'd see a Win32filepath environment variable but no version of the Cygwin DLL does anything with this variable. 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: Installed Cygwin 1.7 - no X?
Christopher Faylor wrote: (who wonders if he should make good on this threat to merge the cygwin-xfree and cygwin mailing lists) I thought that was a done deal, just waiting on someone to get around to it. MHO: go, go! -- 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: Installed Cygwin 1.7 - no X?
Date: Tue, 7 Jul 2009 14:50:49 -0600 From: warren Subject: Re: Installed Cygwin 1.7 - no X? Christopher Faylor wrote: (who wonders if he should make good on this threat to merge the cygwin-xfree and cygwin mailing lists) I thought that was a done deal, just waiting on someone to get around to it. MHO: go, go! +1 ...Karl _ Hotmail® has ever-growing storage! Don’t worry about storage limits. http://windowslive.com/Tutorial/Hotmail/Storage?ocid=TXT_TAGLM_WL_HM_Tutorial_Storage_062009 -- 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
Subversion not caching password
Using the Cygwin version of subversion, I have been unable to
configure it to store my encrypted password in
~/.subversion/auth/svn.simple/.
Here are the steps I am taking (the first step to start with a clean config):
- rm -rf ~/.subversion; svn --version
- edit the ~/.subversion/servers file to include store-passwords =
yes and store-plaintext-passwords = no under the [global] section.\
After following these steps, running svn up from a subversion work
area, I am getting the first expected prompt to accept the certificate
and prompting me for my password. I select 'p' for permanently accept
certificate and enter my password which works as expected. Issuing
the command again prompts me for my password again.
Examining the ~/.subversion/auth/svn.simple/ folder, a file a
successfully been created with the information for the authentication
realm, but this file does not contain the encrypted password.
What am I missing?
EXTRA INFO
---
Another thing I've tried is editing the ~/.subversion/config file and
adding a password-stores = windows-cryptoapi under the [auth]
section. This seems to have no effect.
I would also note that I also have VisualSVN installed on my machine
and when using that version it does not prompt me for my password.
Looking at its config store, It has generated the exact same named
authentication realm file under ${HOMEPATH}/Application\
Data\Subversion\auth\svn.simple\, but contains the encrypted password
section. Copying the contexts of this file the corresponding file
within ~/.subversion/auth/svn.simple/ also has had no effect, as
issuing a svn up command prompts for my password which then
overwrites the ~/.subversion/auth/svn.simple file with the previous,
non-password containing contexts again.
For those tempted to answer with Just use the VisualSVN version (I'm
sure no one out there is thinking that), aside from this not being the
stated problem (not being able to get the Cygwin subversion to cache
passwords), there are also issues with using the VisualSVN version
from the bash shell (things like it not accepting commands after
prompting for merge operations).
Thanks for any help that can be provided. Hopefully there is some
simple you need to uncomment this other property and set it to X
answer to this.
--
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
ssh-host-config is confused between sshd user and cyg_server user
ssh-host-config is confused between 'sshd' user and 'cyg_server' user. Immediately after asking about priviledge separation, you are asked if a 'sshd' account should be created: *** Query: Should privilege separation be used? (yes/no) yes *** Info: Note that creating a new user requires that the current account have *** Info: Administrator privileges. Should this script attempt to create a *** Query: new local account 'sshd'? (yes/no) yes Later it wants to create a 'cyg_server' account: *** Info: No privileged account could be found. *** Info: This script plans to use 'cyg_server'. *** Info: 'cyg_server' will only be used by registered services. *** Query: Do you want to use a different name? (yes/no) This is on a fresh 1.7 install on a new machine. -- Tom Schutter First American - Proxix Solutions 303-440-7272 x6822 512-977-6822 $ ssh-host-config *** Info: Generating /etc/ssh_host_key *** Info: Generating /etc/ssh_host_rsa_key *** Info: Generating /etc/ssh_host_dsa_key *** Info: Creating default /etc/ssh_config file *** Info: Creating default /etc/sshd_config file *** Info: Privilege separation is set to yes by default since OpenSSH 3.3. *** Info: However, this requires a non-privileged account called 'sshd'. *** Info: For more info on privilege separation read /usr/share/doc/openssh/README.privsep. *** Query: Should privilege separation be used? (yes/no) yes *** Info: Note that creating a new user requires that the current account have *** Info: Administrator privileges. Should this script attempt to create a *** Query: new local account 'sshd'? (yes/no) yes *** Info: Updating /etc/sshd_config file *** Warning: The following functions require administrator privileges! *** Query: Do you want to install sshd as a service? *** Query: (Say no if it is already installed as a service) (yes/no) yes *** Query: Enter the value of CYGWIN for the daemon: [] *** Info: On Windows Server 2003, Windows Vista, and above, the *** Info: SYSTEM account cannot setuid to other users -- a capability *** Info: sshd requires. You need to have or to create a privileged *** Info: account. This script will help you do so. *** Info: You appear to be running Windows 2003 Server or later. On 2003 *** Info: and later systems, it's not possible to use the LocalSystem *** Info: account for services that can change the user id without an *** Info: explicit password (such as passwordless logins [e.g. public key *** Info: authentication] via sshd). *** Info: If you want to enable that functionality, it's required to create *** Info: a new account with special privileges (unless a similar account *** Info: already exists). This account is then used to run these special *** Info: servers. *** Info: Note that creating a new user requires that the current account *** Info: have Administrator privileges itself. *** Info: No privileged account could be found. *** Info: This script plans to use 'cyg_server'. *** Info: 'cyg_server' will only be used by registered services. *** Query: Do you want to use a different name? (yes/no) no *** Query: Create new privileged user account 'cyg_server'? (yes/no) yes *** Info: Please enter a password for new user cyg_server. Please be sure *** Info: that this password matches the password rules given on your system. *** Info: Entering no password will exit the configuration. *** Query: Please enter the password: *** Query: Reenter: *** Info: User 'cyg_server' has been created with password '*'. *** Info: If you change the password, please remember also to change the *** Info: password for the installed services which use (or will soon use) *** Info: the 'cyg_server' account. *** Info: Also keep in mind that the user 'cyg_server' needs read permissions *** Info: on all users' relevant files for the services running as 'cyg_server'. *** Info: In particular, for the sshd server all users' .ssh/authorized_keys *** Info: files must have appropriate permissions to allow public key *** Info: authentication. (Re-)running ssh-user-config for each user will set *** Info: these permissions corrently. [Similary restrictions apply, for *** Info: instance, for .rhosts files if the rshd server is running, etc]. *** Info: The sshd service has been installed under the 'cyg_server' *** Info: account. To start the service now, call `net start sshd' or *** Info: `cygrunsrv -S sshd'. Otherwise, it will start automatically *** Info: after the next reboot. *** Info: Host configuration finished. Have fun! Cygwin Configuration Diagnostics Current System Time: Tue Jul 07 16:43:31 2009 Windows 2003 Server R2 Ver 5.2 Build 3790 Service Pack 2 Running in Terminal Service session Path: C:\cygwin\usr\local\bin C:\cygwin\bin C:\cygwin\bin C:\cygwin\usr\X11R6\bin C:\WINDOWS\system32 C:\WINDOWS C:\WINDOWS\System32\Wbem C:\Program Files\Intel\DMIX Output from C:\cygwin\bin\id.exe (nontsec) UID: 18718(tschutter) GID: 10513(Domain
Re: Subversion not caching password
On 7/7/2009 3:04 PM, Derek Greer wrote: Using the Cygwin version of subversion, I have been unable to configure it to store my encrypted password in ~/.subversion/auth/svn.simple/. Here are the steps I am taking (the first step to start with a clean config): - rm -rf ~/.subversion; svn --version - edit the ~/.subversion/servers file to include store-passwords = yes and store-plaintext-passwords = no under the [global] section.\ I guess the Cygwin build of subversion can only cache plaintext passwords, and you've just turned that off, so it won't cache passwords. I will look into supporting the wincrypt API in the Cygwin build, but I wouldn't hold your breath if I were you. It might also be possible to turn on the GNOME keyring or KWallet support, although again I'm not sure. -- David Rothenberger daver...@acm.org Volunteer Cygwin subversion maintainer. -- 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: ssh-host-config is confused between sshd user and cyg_server user
Tom Schutter wrote: ssh-host-config is confused between 'sshd' user and 'cyg_server' user. You are confused between 'sshd' user and 'cyg_server' user; ssh-host-config knows what it's doing. Immediately after asking about priviledge separation, you are asked if a 'sshd' account should be created: Yes. Later it wants to create a 'cyg_server' account: Yes. And? 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: Subversion not caching password
Very cool. Thanks much! Derek -Original Message- From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On Behalf Of David Rothenberger Sent: Tuesday, July 07, 2009 10:11 PM To: cygwin@cygwin.com Subject: Re: Subversion not caching password On 7/7/2009 4:39 PM, David Rothenberger wrote: On 7/7/2009 3:04 PM, Derek Greer wrote: Using the Cygwin version of subversion, I have been unable to configure it to store my encrypted password in ~/.subversion/auth/svn.simple/. I will look into supporting the wincrypt API in the Cygwin build, but I wouldn't hold your breath if I were you. Turns out this wasn't too hard. I'm working on packaging 1.6.3, so I'll include this fix in those packages. They should be available early next week if not before. -- David Rothenberger daver...@acm.org Volunteer Cygwin subversion maintainer. -- 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 -- 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: Subversion not caching password
On 7/7/2009 4:39 PM, David Rothenberger wrote: On 7/7/2009 3:04 PM, Derek Greer wrote: Using the Cygwin version of subversion, I have been unable to configure it to store my encrypted password in ~/.subversion/auth/svn.simple/. I will look into supporting the wincrypt API in the Cygwin build, but I wouldn't hold your breath if I were you. Turns out this wasn't too hard. I'm working on packaging 1.6.3, so I'll include this fix in those packages. They should be available early next week if not before. -- David Rothenberger daver...@acm.org Volunteer Cygwin subversion maintainer. -- 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
gfortran and gcc 4.5 (experimental) binary for Cygwin-1.7
I have posted a link to gfortran and gcc binaries for the latest gcc experimental 4.5 trunk at the gfortran wiki. This was built under Cygwin-1.7. I do not know if they will run on under Cygwin-1.5. These binaries are pre-release provided for testing purposes. The executables are stripped. The wiki is here: http://gcc.gnu.org/wiki/GFortranBinaries There are instructions for installing provided in the wiki. Please let me know if it works. Regards, Jerry -- 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: Successful build of ssh from openssh w. MIT kerberos
On 07/07/2009 04:52, Corinna Vinschen wrote: dream What would be *really* cool: Somebody volunteering as Cygwin package maintainer for a Kerberos 5 package. /dream Ports has provided heimdal for some time (heimdal is fully autotooled, so it's a lot easier to build correctly than MIT-KRB5), but I don't know how to test it in the field (make check looks good, though). I just updated the build for 1.2.1, if someone wants to give it a spin: http://cygwin-ports.svn.sourceforge.net/viewvc/cygwin-ports/ports/trunk/net/heimdal/ Yaakov -- 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
