[ITP] win-ssh-agent 1.07
I'd like to package and maintain win-ssh-agent for Cygwin. With the win-ssh-agent, we can use the ssh-agent (available inthe cygwin openssh) in the more smart way. Normally, we need to start all relevant programs, which mightneed to use the ssh, as child processes of the shell(e.g. bash) in which you eval'ed the ssh-agent. Because, theprograms must be able to refer to environment variables thatset by the ssh-agent. The win-ssh-agent enables all programs to refer to theenvironment variables of the ssh-agent, i.e. theSSH_AUTH_SOCK. Now, we no longer need to start programs aschild processes of the shell. win-ssh-agent been written only for Cygwin, so it's not available in any Linux distros and needs to be voted on. License: BSDHome page: https://github.com/ganaware/win-ssh-agentAuthor: Nayuta Taga ganaw...@gmail.com setup.hint category: Utilsrequires: openssh cygwinsdesc: A ssh-agent wrapper with simple GUIldesc: With the win-ssh-agent, we can use the ssh-agent (available inthe cygwin openssh) in the more smart way. Normally, we need to start all relevant programs, which mightneed to use the ssh, as child processes of the shell(e.g. bash) in which you eval'ed the ssh-agent. Because, theprograms must be able to refer to environment variables thatset by the ssh-agent. The win-ssh-agent enables all programs to refer to theenvironment variables of the ssh-agent, i.e. theSSH_AUTH_SOCK. Now, we no longer need to start programs aschild processes of the shell./setup.hint wget \ https://github.com/downloads/ganaware/win-ssh-agent-cygport/setup.hint \ https://github.com/downloads/ganaware/win-ssh-agent-cygport/win-ssh-agent-1.07-1-src.tar.bz2 \ https://github.com/downloads/ganaware/win-ssh-agent-cygport/win-ssh-agent-1.07-1.tar.bz2
Re: [ITP] libid3tag
On Oct 30 19:55, Yaakov (Cygwin/X) wrote: libid3tag is a library for handling embedded ID3 tags in multimedia. ftp://ftp.cygwinports.org/pub/cygwinports/release-2/libid3tag/ Even though ID3 tags are most commonly associated with MP3 files, they are not impacted by MP3 patent claims and therefore libid3tag is available even in Fedora. libid3tag is a(n optional) prerequisite for imlib2, which is needed for updating openbox. Please go ahead. Same for source-highlight. Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: [ITP] astrometry.net-0.38-1
On Oct 30 23:10, Jussi Kantola wrote: Bump. The package has the 5 votes required for inclusion of a new package, still missing the GTG. If someone knows the package is not GTG, can I please get directions about what's wrong. The project that sort of needs astrometry.net in the Cygwin repos is close to its first publicized release (in fact, we're just waiting for the package approval); check it out at http://sourceforge.net/p/astrotortilla/ Meanwhile, wget \ http://rubor.org/astrometrytortilla/astrometry.net/astrometry.net-0.38-1.tar.bz2 \ http://rubor.org/astrometrytortilla/astrometry.net/astrometry.net-0.38-1-src.tar.bz2 \ http://rubor.org/astrometrytortilla/astrometry.net/setup.hint I hoped that somebody who voted on the package would do the final GTG, but in vain it seems. Anyway, I just had a look. The packaging now looks basically good. One issue I still have with the package is the big number of non-standard binaries in /usr/bin. Is it really necessary to have all the binaries as user-accessible binaries in /usr/bin? Or are many of the binaries just called from another (or other) binaries which serve as the primary UI? What also bugs me are the generic names of the binaries. Plotstuff, merge-index, tablist, tabsort, checktree, ... This all sounds not much like astronomer stuff. So, I would prefer to split the binaries into two groups: - UI binary (or binaries) into /usr/bin - Helper binaries into /usr/share/astrometry/bin There's also still the issue with usr/lib/astrometry/libbackend.so. If that's really a shared lib, it should be called cygbackend.dll and should reside in /usr/bin. If the binaries are using it, they should also be linked against it, rather than being linked statically. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: [ITP] astrometry.net-0.38-1
On 11/3/2011 8:02 AM, Corinna Vinschen wrote: I hoped that somebody who voted on the package would do the final GTG, but in vain it seems. Sorry...I had intended to, but got swamped with other stuff. :-( Anyway, I just had a look. The packaging now looks basically good. One issue I still have with the package is the big number of non-standard binaries in /usr/bin. Is it really necessary to have all the binaries as user-accessible binaries in /usr/bin? Or are many of the binaries just called from another (or other) binaries which serve as the primary UI? What also bugs me are the generic names of the binaries. Plotstuff, merge-index, tablist, tabsort, checktree, ... This all sounds not much like astronomer stuff. So, I would prefer to split the binaries into two groups: - UI binary (or binaries) into /usr/bin - Helper binaries into /usr/share/astrometry/bin FHS says that architecture-dependent files should go under /usr/lib/ not /usr/share...so /usr/lib/astrometry/bin -- Chuck
Re: [ITP] astrometry.net-0.38-1
On Nov 3 08:55, Charles Wilson wrote: On 11/3/2011 8:02 AM, Corinna Vinschen wrote: I hoped that somebody who voted on the package would do the final GTG, but in vain it seems. Sorry...I had intended to, but got swamped with other stuff. :-( Anyway, I just had a look. The packaging now looks basically good. One issue I still have with the package is the big number of non-standard binaries in /usr/bin. Is it really necessary to have all the binaries as user-accessible binaries in /usr/bin? Or are many of the binaries just called from another (or other) binaries which serve as the primary UI? What also bugs me are the generic names of the binaries. Plotstuff, merge-index, tablist, tabsort, checktree, ... This all sounds not much like astronomer stuff. So, I would prefer to split the binaries into two groups: - UI binary (or binaries) into /usr/bin - Helper binaries into /usr/share/astrometry/bin FHS says that architecture-dependent files should go under /usr/lib/ not /usr/share...so /usr/lib/astrometry/bin Uh, yes, indeed. Thanks for spotting that. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: [ITP] win-ssh-agent 1.07
I'd like to package and maintain win-ssh-agent for Cygwin. With the win-ssh-agent, we can use the ssh-agent (available inthe cygwin openssh) in the more smart way. Normally, we need to start all relevant programs, which mightneed to use the ssh, as child processes of the shell(e.g. bash) in which you eval'ed the ssh-agent. Because, theprograms must be able to refer to environment variables thatset by the ssh-agent. The win-ssh-agent enables all programs to refer to theenvironment variables of the ssh-agent, i.e. theSSH_AUTH_SOCK. Now, we no longer need to start programs aschild processes of the shell. +1 Sounds useful.
[ITP] imlib2
imlib2 is an image loading library from the Enlightenment project. ftp://ftp.cygwinports.org/pub/cygwinports/release-2/Enlightenment/imlib2/ imlib2 is already in the major distros, and is required for an upcoming update to openbox. Yaakov
Re: [ITP] astrometry.net-0.38-1
On Thu, Nov 3, 2011 at 2:02 PM, Corinna Vinschen wrote: Is it really necessary to have all the binaries as user-accessible binaries in /usr/bin? Or are many of the binaries just called from another (or other) binaries which serve as the primary UI? The latter was true. I updated the packages as per your instructions: the actual binaries are now in /usr/lib/astrometry/bin, whereas two user interface commands are PATH-setting shell scripts, /usr/bin/solve-field and /usr/bin/wcsinfo. Solve-field is the actual astrometry.net solver, whereas wcsinfo is used to extract World Coordinate System data from the output generated by solve-field. There may be more commands that should be available in the default PATH; I'm sure the astrometry.net community will notify me if this is the case. There's also still the issue with usr/lib/astrometry/libbackend.so. If that's really a shared lib, it should be called cygbackend.dll and should reside in /usr/bin. If the binaries are using it, they should also be linked against it, rather than being linked statically. I dug a little deeper into it, and to my best knowledge the .so was being used only by two Python-scripts, which weren't even installed by the Makefile. So I'm assuming it's either a WIP or obsolete code. I modified the package source (and Makefile) to reflect Cygwin's naming scheme, however, the shared lib is _not_ installed anymore (neither in the binary package, nor by the Makefile in the source package). I haven't noticed anything breaking up due to this. Package filenames are the same, but the contents have been updated. wget \ http://rubor.org/astrometrytortilla/astrometry.net/astrometry.net-0.38-1.tar.bz2 \ http://rubor.org/astrometrytortilla/astrometry.net/astrometry.net-0.38-1-src.tar.bz2 \ http://rubor.org/astrometrytortilla/astrometry.net/setup.hint -- jussi
Re: [ITP] win-ssh-agent 1.07
On Thu, Nov 03, 2011 at 09:52:20AM -0400, Andrew Schulman wrote: I'd like to package and maintain win-ssh-agent for Cygwin. With the win-ssh-agent, we can use the ssh-agent (available inthe cygwin openssh) in the more smart way. Normally, we need to start all relevant programs, which mightneed to use the ssh, as child processes of the shell(e.g. bash) in which you eval'ed the ssh-agent. ?Because, theprograms must be able to refer to environment variables thatset by the ssh-agent. The win-ssh-agent enables all programs to refer to theenvironment variables of the ssh-agent, i.e. theSSH_AUTH_SOCK. ?Now, we no longer need to start programs aschild processes of the shell. +1 Sounds useful. I don't agree. I don't see why this couldn't be accomplished using standard UNIX tools and it seems like it might even be a potential security hole. I don't see the need to have this package in the distribution. cgf
Re: Title bar of X apps, no host name?
On 24.10.2010 04:59, Jerry Cloe wrote: When I start individual windows between two linux boxes I always get the host name in the title bar of the window. For example from my desktop linux box: ssh -X jerry@prodserver then gedit The title bar of the resulting gedit window will be along the lines of: gedit (on prodserver.host.com) But, when I do this from my windows/cygwin desktop, the title bar is simply gedit without the host name. On the linux side, I've never done anything to set this up or make it work, it just always worked, so I'm not even sure where to begin looking. Any ideas? Does anyone know how to change the window title to include the hostname please ? Connecting to 4 machines (with *ssh -Y*) and starting the *gvim* on all of them can be really frustrating when you have no indication what machine each instance is running on. Thank you, Timothy Madden -- 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/cygwin ChangeLog fhandler.cc global ...
CVSROOT:/cvs/src Module name:src Changes by: cori...@sourceware.org 2011-11-03 17:47:34 Modified files: winsup/cygwin : ChangeLog fhandler.cc globals.cc winsup.h Log message: * fhandler.cc (off_current): Define local in fhandler_base::raw_write. Drop erroneous NO_COPY, add _RDATA to make R/O. (off_append): Ditto. * globals.cc (_RDATA): Move definition from here... * winsup.h: ...to here. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/ChangeLog.diff?cvsroot=srcr1=1.5541r2=1.5542 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/fhandler.cc.diff?cvsroot=srcr1=1.405r2=1.406 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/globals.cc.diff?cvsroot=srcr1=1.31r2=1.32 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/winsup.h.diff?cvsroot=srcr1=1.238r2=1.239
winsup/cygwin ChangeLog sigproc.cc
CVSROOT:/cvs/uberbaum Module name:winsup Changes by: c...@sourceware.org 2011-11-03 18:48:27 Modified files: cygwin : ChangeLog sigproc.cc Log message: * sigproc.cc (child_info_spawn::reattach_children): Avoid issuing an error when we can't duplicate from parent since it is probably ok if children of the previous owner of the pid disappear. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/winsup/cygwin/ChangeLog.diff?cvsroot=uberbaumr1=1.5542r2=1.5543 http://sourceware.org/cgi-bin/cvsweb.cgi/winsup/cygwin/sigproc.cc.diff?cvsroot=uberbaumr1=1.347r2=1.348
winsup/cygwin ChangeLog sigproc.cc
CVSROOT:/cvs/uberbaum Module name:winsup Changes by: c...@sourceware.org 2011-11-03 21:44:05 Modified files: cygwin : ChangeLog sigproc.cc Log message: * sigproc.cc (child_info::sync): Report on exit code in strace output. (child_info::proc_retry): Don't consider STATUS_ACCESS_VIOLATION as a restartable event. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/winsup/cygwin/ChangeLog.diff?cvsroot=uberbaumr1=1.5543r2=1.5544 http://sourceware.org/cgi-bin/cvsweb.cgi/winsup/cygwin/sigproc.cc.diff?cvsroot=uberbaumr1=1.348r2=1.349
Re: [PATCH] Prevent restart of crashing non-Cygwin exe
On Nov 2 20:53, Christian Franke wrote: On Jun 24, Corinna Vinschen wrote: Hi Christian, On Jun 23 19:52, Christian Franke wrote: If a non-Cygwin .exe started from a Cygwin shell window segfaults, Cygwin restarts the .exe 5 times. [...l] * sigproc.cc (child_info::sync): Add exit_code to debug message. (child_info::proc_retry): Don't retry on unknown exit_code from non-cygwin programs. This looks ok to me, but cgf should have a say here. He's on vacation for another week, though. Problem can still be reproduced with current CVS. Patch is still valid. Sorry, I forgot about this patch entirely. Chris, is that patch ok with you as well? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: Extend faq.using to discuss fork failures
On 30/08/2011 14:41, Ryan Johnson wrote: That sounds reasonable, though I suspect we'd want want to keep the concluding bits in the FAQ as well. Unfortunately, summertime free time has come to an end so I don't know when I'll get to this next. Perhaps a good compromise for now would be for you to post only the first FAQ question? That would at least cut traffic to the cygwin ML a bit. I've updated Ryan's patch to hopefully address the comments made, polished the language a bit in places, and split it into a patch for the FAQ which just says how to fix problems and a patch for the UG which contains the technical details. Index: doc/faq-using.xml === RCS file: /cvs/src/src/winsup/doc/faq-using.xml,v retrieving revision 1.35 diff -u -p -r1.35 faq-using.xml --- doc/faq-using.xml 4 Aug 2011 18:25:41 - 1.35 +++ doc/faq-using.xml 3 Nov 2011 16:26:56 - @@ -1099,7 +1099,7 @@ it./para IPv6 stack, see the ulink url=http://www.microsoft.com/technet/network/ipv6/ipv6faq.mspx;Microsoft TechNet IPv6 FAQ article/ulink /para/answer/qandaentry -qandaentry id=faq.using.bloda +qandaentry id=faq.using.bloda xreflabel=BLODA questionparaWhat applications have been found to interfere with Cygwin?/para/question answer @@ -1199,3 +1199,38 @@ such as virtual memory paging and file c /listitem /itemizedlist/para /answer/qandaentry + +qandaentry id='faq.using.fixing-fork-failures' + questionparaHow do I fix literalfork()/literal failures?/para/question + answer + paraUnfortunately, Windows can be quite hostile to a + reliable fork() implementation, leading to error messages such as:/para + paraitemizedlist +listitemunable to remap emphasissomedll/emphasis to same address as parent/listitem +listitemcouldn't allocate heap/listitem +listitemdied waiting for dll loading/listitem +listitemchild -1 - died waiting for longjmp before initialization/listitem +listitemSTATUS_ACCESS_VIOLATION/listitem +listitemresource temporarily unavailable/listitem + /itemizedlist/para + paraPotential solutions for the above errors:/para + paraitemizedlist +listitemRestart whatever process is trying (and failing) to use +literalfork()/literal. Sometimes Windows sets up a process +environment that is even more hostile to fork() than usual./listitem +listitemEnsure that you have eliminated (not just disabled) all +software on the xref linkend=faq.using.bloda/. +/listitem +listitemRead the 'rebase' package README in +literal/usr/share/doc/rebase//literal, and follow the +instructions there to run 'rebaseall'./listitem +/itemizedlist/para + paraPlease note that installing new packages or updating existing + ones undoes the effects of rebaseall and often causes fork() failures + to reappear. If so, just run rebaseall again. + /para + paraSee the ulink url=http://cygwin.com/cygwin-ug-net/highlights.html#ov-hi-process; + process creation/ulink section of the User's Guide for the technical reasons it is so + difficult to make literalfork()/literal work reliably./para +/answer +/qandaentry Index: doc/overview2.sgml === RCS file: /cvs/src/src/winsup/doc/overview2.sgml,v retrieving revision 1.20 diff -u -p -r1.20 overview2.sgml --- doc/overview2.sgml 18 Sep 2010 15:58:46 - 1.20 +++ doc/overview2.sgml 3 Nov 2011 16:27:36 - @@ -346,6 +346,60 @@ cases, stubs of each of these Win32 proc their exec'd Cygwin process to exit./para /sect2 +sect3 id='ov-hi-process-problems' +titleProblems with process creation/title + +paraThe semantics of literalfork/literal require that a forked +child process have emphasisexactly/emphasis the same address +space layout as its parent. However, Windows provides no native +support for cloning address space between processes and several +features actively undermine a reliable literalfork/literal +implementation. Three issues are especially prevalent:/para + +paraitemizedlist +listitemDLL base address collisions. Unlike *nix shared +libraries, which use position-independent code, Windows shared +libraries assume a fixed base address. Whenever the hard-wired +address ranges of two DLLs collide (which occurs quite often), the +Windows loader must rebase one of them to a different +address. However, it may not resolve collisions consistently, and +may rebase a different dll and/or move it to a different address +every time. Cygwin can usually compensate for this effect when it +involves libraries opened dynamically, but collisions among +statically-linked dlls (dependencies known at compile time) are +resolved before literalcygwin1.dll/literal initializes and +cannot be fixed afterward. This problem can only be solved by +removing the base address conflicts which cause the problem, +usually using the literalrebaseall/literal tool./listitem + +listitemAddress space layout
Re: Extend faq.using to discuss fork failures
Hi Jon, On Nov 3 16:35, Jon TURNEY wrote: On 30/08/2011 14:41, Ryan Johnson wrote: That sounds reasonable, though I suspect we'd want want to keep the concluding bits in the FAQ as well. Unfortunately, summertime free time has come to an end so I don't know when I'll get to this next. Perhaps a good compromise for now would be for you to post only the first FAQ question? That would at least cut traffic to the cygwin ML a bit. I've updated Ryan's patch to hopefully address the comments made, polished the language a bit in places, and split it into a patch for the FAQ which just says how to fix problems and a patch for the UG which contains the technical details. Thanks for doing that. I looks good to me, with just one exception. +listitemAddress space layout randomization (ASLR). Starting with +Vista, Windows implements ASLR, which means that thread stacks, +heap, memory-mapped files, and statically-linked dlls are placed +at different (random) locations in each process. This behaviour +interferes with a proper literalfork/literal, and if an +unmovable object (process heap or system dll) ends up at the wrong +location, Cygwin can do nothing to compensate (though it will +retry a few times automatically). In a 64-bit system, marking +executables as large address-ware and rebasing dlls to high +addresses has been reported to help, as ASLR affects only the +lower 2GB of address space./listitem Starting with In a 64-bit system it's getting a bit weird: - Starting with 4.5.3, gcc marks executables as large address aware automatically, so this is going to be a lesser problem over time. Is it worth to mention this at all? I suppose so, but the user should be pointed to peflags to tests for this property first for the given reason. - Starting with Cygwin 1.7.10, the high address area will be used for the application heap on 64 bit systems and large address aware executables. Mmaps are located there, too. This in turn leaves more room for DLLs in the normal 2 Gigs memory area. Therefore I would not like to suggest rebasing DLLs into the high address area at all. This should only be done by people who know what they are doing. Usually there should be enough space in the lower 2 Gigs, especially when heap and mmaps are out of the way, and given that the more recent rebaseall will not create an arbitrary 64K hole between DLLs anymore when rebasing. With these changes, feel free to check in the patch. Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: Extend faq.using to discuss fork failures
On Thu, Nov 03, 2011 at 04:35:25PM +, Jon TURNEY wrote: On 30/08/2011 14:41, Ryan Johnson wrote: That sounds reasonable, though I suspect we'd want want to keep the concluding bits in the FAQ as well. Unfortunately, summertime free time has come to an end so I don't know when I'll get to this next. Perhaps a good compromise for now would be for you to post only the first FAQ question? That would at least cut traffic to the cygwin ML a bit. I've updated Ryan's patch to hopefully address the comments made, polished the language a bit in places, and split it into a patch for the FAQ which just says how to fix problems and a patch for the UG which contains the technical details. Index: doc/faq-using.xml === RCS file: /cvs/src/src/winsup/doc/faq-using.xml,v retrieving revision 1.35 diff -u -p -r1.35 faq-using.xml --- doc/faq-using.xml 4 Aug 2011 18:25:41 - 1.35 +++ doc/faq-using.xml 3 Nov 2011 16:26:56 - @@ -1099,7 +1099,7 @@ it./para IPv6 stack, see the ulink url=http://www.microsoft.com/technet/network/ipv6/ipv6faq.mspx;Microsoft TechNet IPv6 FAQ article/ulink /para/answer/qandaentry -qandaentry id=faq.using.bloda +qandaentry id=faq.using.bloda xreflabel=BLODA questionparaWhat applications have been found to interfere with Cygwin?/para/question answer @@ -1199,3 +1199,38 @@ such as virtual memory paging and file c /listitem /itemizedlist/para /answer/qandaentry + +qandaentry id='faq.using.fixing-fork-failures' + questionparaHow do I fix literalfork()/literal failures?/para/question + answer + paraUnfortunately, Windows can be quite hostile to a I would still prefer eschewing actively negative words like hostile and just neutrally stating that Windows does not use a fork/exec model and does not offer any easy way to implement fork. I'd also like to see specific errors mentioned so that when people are searching for a solution to the problem they will be able to find it in the FAQ. cgf
Re: [PATCH] Prevent restart of crashing non-Cygwin exe
On Thu, Nov 03, 2011 at 01:07:20PM +0100, Corinna Vinschen wrote: On Nov 2 20:53, Christian Franke wrote: On Jun 24, Corinna Vinschen wrote: Hi Christian, On Jun 23 19:52, Christian Franke wrote: If a non-Cygwin .exe started from a Cygwin shell window segfaults, Cygwin restarts the .exe 5 times. [...l] * sigproc.cc (child_info::sync): Add exit_code to debug message. (child_info::proc_retry): Don't retry on unknown exit_code from non-cygwin programs. This looks ok to me, but cgf should have a say here. He's on vacation for another week, though. Problem can still be reproduced with current CVS. Patch is still valid. Sorry, I forgot about this patch entirely. Chris, is that patch ok with you as well? No, it isn't. Sorry for not stating this earlier. The problem that this code was intended to solve was actually a transient exit codes from a non-Cygwin process which began with 0xc... I don't believe that I ever saw STATUS_ACCESS_VIOLATION in any of my testing though so adding that earlier in the switch would fix this particular problem. I'll do that. cgf
[ANNOUNCEMENT] Updated: mercurial-1.9.3-1 -- Python based distributed version control (DVCS)
PACKAGE DESCRIPTION === Homepage: http://mercurial.selenic.com License : GPL Distributed, efficient Python based source control system. Mercurial is designed for efficient handling of very large distributed projects. CHANGES SINCE LAST RELEASE == See http://mercurial.selenic.com/wiki/WhatsNew INSTALL OR UPGRADE NOTES Standard Cygwin install. For more information, see http://mercurial.selenic.com/wiki/UpgradeNotes 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(at)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.com(at)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
[ANNOUNCEMENT] Updated: bzr 2.4.2-1 -- Python based distributed version control (DVCS)
PACKAGE DESCRIPTION === Home page: http://bazaar.canonical.com License : GPL (Bzr is part of GNU project) Distributed version control that is used in projects like managing Ubuntu packages http://ubuntulinux.org and it is one of the funded projects of Canonical. - Uses one .bzr directory at the top of the tree - The user interface is simple and familiar to people with experience from CVS or Subversion. - Offers a choice between centralized and decentralized/diconnected work. - Strong security. History can be GPG-signed to protect against man-in-the-middle attacks, bad mirrors, server intrusion or data corruption. CHANGES SINCE LAST RELEASE == https://launchpad.net/bzr/+announcements http://doc.bazaar.canonical.com/bzr.dev/en/release-notes/index.html http://doc.bazaar.canonical.com/en/ INSTALL OR UPGRADE NOTES Upgrade existing branches to new format with commands: bzr infoTo see current repository format bzr reconcile To correct metadata prior upgrade bzr upgrade To convert repository to latest format bzr packTo make repository faster Following additional Cygwin modules can be also installed: python-paramiko - for ssh/sftp support python-crypto - required by paramiko 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(at)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.com(at)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: Problem with execution of binary file
On Nov 3 12:20, Edvardsen Kåre wrote: I keep getting the cannot execute binary file and don't understand why. I have compiled same software on two different machines, but only one of the binaries work (it works on both machines). The successful machine is a HP laptop with W7 Pro, the other unsuccessful is a HP desktop in a AD network domain with W7 Enterpr and cygwin is installed with lokal admin rights only, so I keep getting the Your group is currently mkpasswd... message. What about running $ mkpasswd -l -d /etc/passwd $ mkgroup -l -d /etc/group so you don't get this message? I don't know if this may affect the result, but should not, as I can run the other successful binary. I was guided to run strace along with the call to the erroneous binary and the output is pasted below. The problem binary is called FLEXPART_GFORTRAN Can anyone see what's wrong in the strace log? No. What the strace shows is that bash does not even try to fork and then exec FLEXPART_GFORTRAN. Rather, it just opens the file, reads the first few bytes and then prints the error message: 4514 125618 [main] bash 536 open: open (./FLEXPART_GFORTRAN, 0x0) [...] 25 126365 [main] bash 536 open: 3 = open (./FLEXPART_GFORTRAN, 0x0) 209 126574 [main] bash 536 isatty: 0 = isatty (3) [...] 25 126623 [main] bash 536 lseek64: 0 = lseek (3, 0, 1) [...] 24 126710 [main] bash 536 readv: 80 = readv (3, 0x28CA34, 1), errno 0 458 127168 [main] bash 536 open: open (/usr/share/locale/locale.alias, 0x0) [...etc...] For some reason which isn't visible in the strace, bash doesn't even close the file anymore. What does `file FLEXPART_GFORTRAN.exe' print? 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
recompiling gcc, make, and binutils for my cpu architecture?
Hi all, I hope I am posting in the right location. I would like to setup/optimize gcc, binutils, and make for my CPU architecture, AMD K8, and rebuild. I have installed the cygwin sources. When I build, I get i686-pc-cygwin. How can I make the build K8-pc-cygwin with the proper optimizations. My CPU's information can be obtained from http://www.cpu-world.com/CPUs/K8/AMD-Sempron%203100+%20-%20SDA3100AIP3AX%20%28SDA3100AXBOX%29.html if it is needed. I would also like to know which order I should build in if it matters... and also if I should get the sources from the respective tools svn site instead of using the cygwin sources. My OS is Windows XP SP3 Thanks in advance for your replies. Jorge PS, when/if I have some success with this, I am willing to rebuild and package the entire cygwin distribution with some guidance from some experienced builders if it will help in any way. -- 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 execution of binary file
On to., 2011-11-03 at 14:01 +0100, Edvardsen Kåre wrote: On Nov 3 12:20, Edvardsen KÃre wrote: I keep getting the cannot execute binary file and don't understand why. I have compiled same software on two different machines, but only one of the binaries work (it works on both machines). The successful machine is a HP laptop with W7 Pro, the other unsuccessful is a HP desktop in a AD network domain with W7 Enterpr and cygwin is installed with lokal admin rights only, so I keep getting the Your group is currently mkpasswd... message. What about running $ mkpasswd -l -d /etc/passwd $ mkgroup -l -d /etc/group so you don't get this message? I don't know if this may affect the result, but should not, as I can run the other successful binary. I was guided to run strace along with the call to the erroneous binary and the output is pasted below. The problem binary is called FLEXPART_GFORTRAN Can anyone see what's wrong in the strace log? No. What the strace shows is that bash does not even try to fork and then exec FLEXPART_GFORTRAN. Rather, it just opens the file, reads the first few bytes and then prints the error message: 4514 125618 [main] bash 536 open: open (./FLEXPART_GFORTRAN, 0x0) [...] 25 126365 [main] bash 536 open: 3 = open (./FLEXPART_GFORTRAN, 0x0) 209 126574 [main] bash 536 isatty: 0 = isatty (3) [...] 25 126623 [main] bash 536 lseek64: 0 = lseek (3, 0, 1) [...] 24 126710 [main] bash 536 readv: 80 = readv (3, 0x28CA34, 1), errno 0 458 127168 [main] bash 536 open: open (/usr/share/locale/locale.alias, 0x0) [...etc...] For some reason which isn't visible in the strace, bash doesn't even close the file anymore. What does `file FLEXPART_GFORTRAN.exe' print? Corinna First, The university won't let me run the $ mkpasswd -l -d /etc/passwd $ mkgroup -l -d /etc/group with AD rights, so I just have to live with that. Then, file FLEXPART_GFORTRAN.exe prints: PE32 executable (console) Intel 80386, for MS Windows. I'm not even close being an expert on this, but usually I manage to figure out something, but this time I'm totally lost... It's about a month since I built the well working binary on the different machine, and wonder if any upgrades of cygwin software (compilers or anything) since then may have contain some bug. The bad binary is built on a quite fresh cygwin install. Maybe I will try to reinstall cygwin on the successful machine and see if a rebuilt version of the binary fails. Any thoughts on that? Cheers, Kåre
Re: Problem with execution of binary file
Someone more expert than I am may be able to say more (or correct me if I'm wrong), but it appears that bash opened the file, read 80 bytes, and didn't like what it saw. So: What does file FLEXPART_GFORTRAN.exe say about the file? Or maybe you could give us the first few lines from od -b FLEXPART_GFORTRAN.exe. It's starting to look as if it is not properly built. Or, maybe it got messed with in the process of transfer from the other system. Regards -- Eliot Moss -- 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: recompiling gcc, make, and binutils for my cpu architecture?
On 03/11/2011 8:54 AM, Jorge wrote: Hi all, I hope I am posting in the right location. This has nothing whatsoever to do with cygwin. I would like to setup/optimize gcc, binutils, and make for my CPU architecture, AMD K8, and rebuild. I have installed the cygwin sources. Invoking gcc with -march=native should do exactly what you want with far less effort than rebuilding the toolchain from scratch (a task not for the faint of heart nor for the impatient). Make cares very little what architecture it runs on; binutils cares deeply but almost certainly does the right thing already. If you need more information, try 'man gcc' and 'http://gcc.gnu.org' (in that order). Ryan -- 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 execution of binary file
On to., 2011-11-03 at 08:21 -0500, Eliot Moss wrote: Someone more expert than I am may be able to say more (or correct me if I'm wrong), but it appears that bash opened the file, read 80 bytes, and didn't like what it saw. So: What does file FLEXPART_GFORTRAN.exe say about the file? Or maybe you could give us the first few lines from od -b FLEXPART_GFORTRAN.exe. It's starting to look as if it is not properly built. Or, maybe it got messed with in the process of transfer from the other system. Regards -- Eliot Moss As corinna pointed out, the file is barely red before it's closed. The file command gives PE32 executable (console) Intel 80386, for MS Windows Here is a few lines of od -b output from both the working and bad binary, respectively. Good binary 000 115 132 220 000 003 000 000 000 004 000 000 000 377 377 000 000 020 270 000 000 000 000 000 000 000 100 000 000 000 000 000 000 000 040 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 060 000 000 000 000 000 000 000 000 000 000 000 000 200 000 000 000 100 016 037 272 016 000 264 011 315 041 270 001 114 315 041 124 150 120 151 163 040 160 162 157 147 162 141 155 040 143 141 156 156 157 140 164 040 142 145 040 162 165 156 040 151 156 040 104 117 123 040 160 155 157 144 145 056 015 015 012 044 000 000 000 000 000 000 000 200 120 105 000 000 114 001 017 000 032 067 261 116 000 154 165 000 220 252 072 000 000 340 000 047 001 013 001 002 026 000 354 015 000 240 000 220 022 000 000 322 127 073 000 020 000 000 000 020 000 000 260 000 000 016 000 000 000 100 000 000 020 000 000 000 002 000 000 300 004 000 000 000 001 000 000 000 004 000 000 000 000 000 000 000 320 000 300 315 073 000 004 000 000 041 217 173 000 003 000 000 200 340 000 000 040 000 000 020 000 000 000 000 020 000 000 020 000 000 360 000 000 000 000 020 000 000 000 000 000 000 000 000 000 000 000 400 000 220 152 073 014 016 000 000 000 000 000 000 000 000 000 000 420 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 * 520 000 000 000 000 000 000 000 000 174 222 152 073 030 002 000 000 540 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 560 000 000 000 000 000 000 000 000 056 164 145 170 164 000 000 000 600 010 352 015 000 000 020 000 000 000 354 015 000 000 004 000 000 620 000 000 000 000 000 000 000 000 000 000 000 000 140 000 120 140 Bad binary 000 115 132 220 000 003 000 000 000 004 000 000 000 377 377 000 000 020 270 000 000 000 000 000 000 000 100 000 000 000 000 000 000 000 040 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 060 000 000 000 000 000 000 000 000 000 000 000 000 200 000 000 000 100 016 037 272 016 000 264 011 315 041 270 001 114 315 041 124 150 120 151 163 040 160 162 157 147 162 141 155 040 143 141 156 156 157 140 164 040 142 145 040 162 165 156 040 151 156 040 104 117 123 040 160 155 157 144 145 056 015 015 012 044 000 000 000 000 000 000 000 200 120 105 000 000 114 001 017 000 144 115 261 116 000 130 165 000 220 252 072 000 000 340 000 047 001 013 001 002 026 000 322 015 000 240 000 166 022 000 000 354 273 311 000 020 000 000 000 020 000 000 260 000 360 015 000 000 000 100 000 000 020 000 000 000 002 000 000 300 004 000 000 000 001 000 000 000 004 000 000 000 000 000 000 000 320 000 320 061 312 000 004 000 000 126 346 172 000 003 000 000 200 340 000 000 040 000 000 020 000 000 000 000 020 000 000 020 000 000 360 000 000 000 000 020 000 000 000 000 000 000 000 000 000 000 000 400 000 220 316 311 014 016 000 000 000 000 000 000 000 000 000 000 420 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 * 520 000 000 000 000 000 000 000 000 174 222 316 311 030 002 000 000 540 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 560 000 000 000 000 000 000 000 000 056 164 145 170 164 000 000 000 600 270 320 015 000 000 020 000 000 000 322 015 000 000 004 000 000 620 000 000 000 000 000 000 000 000 000 000 000 000 140 000 120 140 640 056 144 141 164 141 000 000 000 224 220 004 000 000 360 015 000
invisible / hidden prompt text after exiting process
After exiting a process that returns me back to the shell, my prompt text is hidden. (Example - emacs file.txt; or ssh myserver.com; then exit. From then on, prompt text is hidden.) The characters are passed: when I type blindly and hit enter the command goes through, but I cannot see what I am typing. My fix has been to simply close and re-open a new cygwin window. I experienced this many years ago and found a fix. I recently got a new computer but quite unfortunately I do not remember the solution, and searching both my personal archives and the internet at large turned up nothing. Cygwin Configuration Diagnostics Current System Time: Thu Nov 03 11:19:22 2011 Windows 7 Home Premium Ver 6.1 Build 7601 Service Pack 1 Running under WOW64 on AMD64 Path: E:\Cygwin\usr\local\bin E:\Cygwin\bin C:\Program Files\Common Files\Microsoft Shared\Windows Live C:\windows\system32 C:\windows C:\windows\System32\Wbem C:\windows\System32\WindowsPowerShell\v1.0 C:\Program Files (x86)\Toshiba\Bluetooth Toshiba Stack\sys C:\Program Files (x86)\Toshiba\Bluetooth Toshiba Stack\sys\x64 C:\Program Files (x86)\QuickTime\QTSystem C:\Program Files (x86)\Common Files\HP\Digital Imaging\bin C:\Program Files (x86)\HP\Digital Imaging\bin C:\Program Files (x86)\HP\Digital Imaging\bin\Qt\Qt 4.3.3 C:\Program Files\Microsoft Network Monitor 3 C:\Program Files\Common Files\Microsoft Shared\Windows Live Output from E:\Cygwin\bin\id.exe UID: 1000(evlach) GID: 513(None) 513(None) 545(Users)1001(HomeUsers) SysDir: C:\windows\system32 WinDir: C:\windows USER = 'evlach' PWD = '/home/evlach' CYGWIN = 'tty' HOME = '/home/evlach' HOMEPATH = '\Users\evlach' MANPATH = '/usr/local/man:/usr/share/man:/usr/man::/usr/ssl/man' APPDATA = 'C:\Users\evlach\AppData\Roaming' ProgramW6432 = 'C:\Program Files' HOSTNAME = 'Psychotic' TERM = 'cygwin' PROCESSOR_IDENTIFIER = 'Intel64 Family 6 Model 30 Stepping 5, GenuineIntel' WINDIR = 'C:\windows' PUBLIC = 'C:\Users\Public' OLDPWD = '/usr/bin' USERDOMAIN = 'Psychotic' CommonProgramFiles(x86) = 'C:\Program Files (x86)\Common Files' OS = 'Windows_NT' ALLUSERSPROFILE = 'C:\ProgramData' !:: = '::\' COMMONPROGRAMFILES = 'C:\Program Files (x86)\Common Files' QTJAVA = 'E:\Program Files (x86)\Java\jre6\lib\ext\QTJava.zip' USERNAME = 'evlach' PROCESSOR_LEVEL = '6' ProgramFiles(x86) = 'C:\Program Files (x86)' PSModulePath = 'C:\windows\system32\WindowsPowerShell\v1.0\Modules\' FP_NO_HOST_CHECK = 'NO' SYSTEMDRIVE = 'C:' PROCESSOR_ARCHITEW6432 = 'AMD64' EDITOR = 'emacs' LANG = 'C.UTF-8' USERPROFILE = 'C:\Users\evlach' PS1 = '\[\e]0;\w\a\]\n\[\e[32m\]\u@\h \[\e[33m\]\w\[\e[0m\]\n\$ ' LOGONSERVER = '\\PSYCHOTIC' CommonProgramW6432 = 'C:\Program Files\Common Files' PROCESSOR_ARCHITECTURE = 'x86' LOCALAPPDATA = 'C:\Users\evlach\AppData\Local' !C: = 'C:\Windows\System32' ProgramData = 'C:\ProgramData' SHLVL = '1' PATHEXT = '.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC' HOMEDRIVE = 'C:' PROMPT = '$P$G' COMSPEC = 'C:\windows\system32\cmd.exe' SYSTEMROOT = 'C:\windows' PRINTER = 'HP Photosmart 2570 series' PROCESSOR_REVISION = '1e05' CLASSPATH = '.;E:\Program Files (x86)\Java\jre6\lib\ext\QTJava.zip' !E: = 'E:\Cygwin\bin' INFOPATH = '/usr/local/info:/usr/share/info:/usr/info:' PROGRAMFILES = 'C:\Program Files (x86)' NUMBER_OF_PROCESSORS = '8' asl.log = 'Destination=file' SESSIONNAME = 'Console' COMPUTERNAME = 'PSYCHOTIC' _ = '/usr/bin/cygcheck' HKEY_CURRENT_USER\Console\Cygwin (default) = 0x00f0 PopupColors = 0x00f5 ColorTable00 = 0x ColorTable01 = 0x0080 ColorTable02 = 0x8000 ColorTable03 = 0x00808000 ColorTable04 = 0x0080 ColorTable05 = 0x00800080 ColorTable06 = 0x8080 ColorTable07 = 0x00c0c0c0 ColorTable08 = 0x00808080 ColorTable09 = 0x00ff ColorTable10 = 0xff00 ColorTable11 = 0x0000 ColorTable12 = 0x00ff ColorTable13 = 0x00ff00ff ColorTable14 = 0x ColorTable15 = 0x00ff InsertMode = 0x0001 QuickEdit = 0x0001 ScreenBufferSize = 0x012c0050 WindowSize = 0x002d0050 FontSize = 0x0014000a FontFamily = 0x0030 FontWeight = 0x0190 FaceName = '8514oem' CursorSize = 0x0019 HistoryBufferSize = 0x0032 NumberOfHistoryBuffers = 0x0004 HistoryNoDup = 0x HKEY_CURRENT_USER\Software\Cygwin HKEY_CURRENT_USER\Software\Cygwin\Program Options HKEY_CURRENT_USER\Software\Cygwin\setup HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\Installations (default) = '\??\E:\Cygwin' HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\Program Options HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\setup (default) = 'E:\Cygwin' obcaseinsensitive set to 1 Cygwin installations found in the registry: System: Key: 685dc4bb75d52efd Path: E:\Cygwin c: hd NTFS 48804Mb 90% CP CS UN PA FC TI105861W0F d: cd N/AN/A e: hd
Re: invisible / hidden prompt text after exiting process
On 03/11/2011 11:54 AM, Eric Vlach wrote: After exiting a process that returns me back to the shell, my prompt text is hidden. (Example - emacs file.txt; or ssh myserver.com; then exit. From then on, prompt text is hidden.) The characters are passed: when I type blindly and hit enter the command goes through, but I cannot see what I am typing. My fix has been to simply close and re-open a new cygwin window. I experienced this many years ago and found a fix. I recently got a new computer but quite unfortunately I do not remember the solution, and searching both my personal archives and the internet at large turned up nothing. I usually just reset the terminal (type 'reset' and hit [enter]) That said, I've only had the problem when a terminal-handling app (= emacs) gets killed unexpectedly, such as when an ssh connection drops. Ryan -- 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 public key authentication problem using curl
Greetings, carolus! After setup with ssh-host-config, ssh-user-config, and ssh-copy-id, public key authentication works with ssh but fails with curl. (Password authentication works with curl -u, but is less convenient.) curl -v shows: SSH authentication methods available: publickey,password,keyboard-interactive Using ssh public key file /home/cdr/.ssh/id_dsa.pub Using ssh private key file /home/cdr/.ssh/id_dsa SSH public key authentication failed: Username/PublicKey combination invalid Authentication failure What was exact command? However, ssh authenticates OK using RSA. ssh -v shows: Next authentication method: publickey Offering public key: /home/cdr/.ssh/id_rsa Server accepts key: pkalg ssh-rsa blen 279 read PEM private key done: type RSA Authentication succeeded (publickey). Again: What was exact command? -- WBR, Andrey Repin (anrdae...@freemail.ru) 03.11.2011, 19:51 Sorry for my terrible english... -- 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 execution of binary file
Edvardsen Kåre writes: Here is a few lines of od -b output from both the working and bad binary, respectively. [...] Maybe more fruitful would be 'objdump -fp' run on both good and bad versions? ..mark -- 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
Possible Bug (clarification) in Cygwin 1.7.5 -- findfirstfile (and findnextfile) yeild bad cfilename when file names have special characters. Works in cygwin 1.5, fails in 1.7
Greetings,
This issue is making my head flat from pounding it against the wall. It
appears to be a bug in Cygwin 1.7, but I can't say with any certainty. I've
been down too many dead end trails already...
With cygwin 1.7.5, cFileName with a special characters such as ñ (n with tidle
above it) fail be properly extracted from a WIN32_FIND_DATA structure with
findFirstFile (or findNextFile).
To set up a simple test scenario, I created a file in C:\Testing named
Mañana.docx. I compiled the code at the end of this message on Cygwin 1.7.9
with GCC version 3.4.4 on Server 2008 32 bit system. On this system (and on a
Windows 7 32 bit machine), it returns:
$ ./winfilestat3.exe
hFind filename is ***Ma▒ana.docx***
hFind file name stat return code is: -1
character 0 is M
character 0 is signed int 77, hex 4d
character 1 is a
character 1 is signed int 97, hex 61
character 2 is ▒
character 2 is signed int -15, hex fff1
character 3 is a
character 3 is signed int 97, hex 61
character 4 is n
character 4 is signed int 110, hex 6e
character 5 is a
character 5 is signed int 97, hex 61
character 6 is .
character 6 is signed int 46, hex 2e
character 7 is d
character 7 is signed int 100, hex 64
character 8 is o
character 8 is signed int 111, hex 6f
character 9 is c
character 9 is signed int 99, hex 63
NOTE that the ñ is interpreted as ▒, and the stat fails.
I moved the compiled program to an old Server 2003 running Cygwin 1.5.25. It
CORRECTLY returns:
bash-3.2$ ./winfilestat3.exe
hFind filename is ***Mañana.docx***
hFind file name stat return code is: 0
character 0 is M
character 0 is signed int 77, hex 4d
character 1 is a
character 1 is signed int 97, hex 61
character 2 is ñ
character 2 is signed int -15, hex fff1
character 3 is a
character 3 is signed int 97, hex 61
character 4 is n
character 4 is signed int 110, hex 6e
character 5 is a
character 5 is signed int 97, hex 61
character 6 is .
character 6 is signed int 46, hex 2e
bash-3.2$
bash-3.2$
Note the ñ is correct, and the stat succeeds.
Is this a bug, or do I need to set something up special on Cygwin 1.7 to get it
to work the way it used to?
Thanks in advance,
Leon
**start of code #include string.h #include
unistd.h #include stdio.h #include sys/stat.h #include stdlib.h
#include string.h
#include unistd.h
#include stdio.h
#include sys/stat.h
#include stdlib.h
#include time.h
#include windows.h
#include winbase.h
#include sys/types.h
#include fcntl.h
#include dirent.h
#include curl/curl.h
#include pthread.h
#include wctype.h
#include sys/wait.h
#include cygwin/wait.h
struct stat fileStat;
WIN32_FIND_DATA FindFileData;
HANDLE hFind;
int main(int argc, char **argv)
{
char filename[100];
int rtn, i;
char chr;
//find file
char pathSearch[300];
sprintf(pathSearch, C:\\Testing\\*.docx);
hFind = FindFirstFile(pathSearch, FindFileData);
if (hFind == INVALID_HANDLE_VALUE)
{
printf(Warning: No .docx file found in the directory.
Exiting.\n);
return(1);
}
strcpy(filename, FindFileData.cFileName);
printf(hFind filename is ***%s***\n,filename);
rtn = stat(filename,fileStat);
printf(hFind file name stat return code is: %d\n, rtn);
for ( i = 0 ; i wcslen(filename) ; i++ )
{
printf(character %d is %c\n, i, filename[i] );
printf(character %d is signed int %d, hex %x \n, i,
filename[i], filename[i] );
}
return(0);
}
**end of code
Leon Vanderploeg
Cell 303-877-9654
--
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 package: libid3tag-0.15.1b-10
The following packages have been added to the Cygwin distribution: *** libid3tag0-0.15.1b-10 *** libid3tag-devel-0.15.1b-10 libid3tag is a library for reading ID3 tags in audio files, both ID3v1 and the various versions of ID3v2. -- Yaakov Cygwin/X CYGWIN-ANNOUNCE UNSUBSCRIBE INFO If you want to unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then 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 If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this 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
[ANNOUNCEMENT] New package: source-highlight-3.1.5-1
The following package has been added to the Cygwin distribution: *** source-highlight-3.1.5-1 *** libsource-highlight4-3.1.5-1 *** libsource-highlight-common-3.1.5-1 *** libsource-highlight-devel-3.1.5-1 GNU Source-highlight is a utility which creates documents with syntax-highlighting from source files. -- Yaakov Cygwin/X CYGWIN-ANNOUNCE UNSUBSCRIBE INFO If you want to unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then 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 If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this 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: Possible Bug (clarification) in Cygwin 1.7.5 -- findfirstfile (and findnextfile) yeild bad cfilename when file names have special characters. Works in cygwin 1.5, fails in 1.7
On 11/3/2011 4:48 PM, Leon Vanderploeg wrote: With cygwin 1.7.5, cFileName with a special characters such as ñ (n with tidle above it) fail be properly extracted from a WIN32_FIND_DATA structure with findFirstFile (or findNextFile). To set up a simple test scenario, I created a file in C:\Testing named Mañana.docx. I compiled the code at the end of this message on Cygwin 1.7.9 with GCC version 3.4.4 on Server 2008 32 bit system. On this system (and on a Windows 7 32 bit machine), it returns: a) Why are you using native Win32 APIs in a cygwin program? You should be using the POSIX interfaces instead -- see /usr/include/dirent.h. DIR *opendir (const char *); DIR *fdopendir (int); struct dirent *readdir (DIR *); int readdir_r (DIR *, struct dirent *, struct dirent **); void rewinddir (DIR *); int closedir (DIR *); b) What you observe is an artifact of cygwin-1.7's new *support* for i18n. In cygwin-1.5, it just didn't care and passed all the bytes back exactly as found without transliteration. In 1.7, it (correctly) transcodes strings into the current locale -- and your current locale does not appear to support ñ -- or, at least, you haven't told cygwin to use the correct one. (I'm probably thoroughly botching this explanation, but the point is, you need to check your LC_* and LANG env vars, and maybe call setlocale(LC_ALL, ) in your application.) -- Chuck -- 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 execution of binary file
Ok, so here's one thing about bash: to get it to run an *executable* (as opposed to a *script*), you need to say bash -c FLEXPART_GFORTRAN. You might try strace on that. In addition to the objdump suggestion. Regards -- EM -- 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 public key authentication problem using curl
On Tue, 2011-11-01 at 15:24 -0500, carolus wrote: After setup with ssh-host-config, ssh-user-config, and ssh-copy-id, public key authentication works with ssh but fails with curl. (Password authentication works with curl -u, but is less convenient.) curl -v shows: SSH authentication methods available: publickey,password,keyboard-interactive Using ssh public key file /home/cdr/.ssh/id_dsa.pub Using ssh private key file /home/cdr/.ssh/id_dsa SSH public key authentication failed: Username/PublicKey combination invalid Authentication failure However, ssh authenticates OK using RSA. ssh -v shows: Next authentication method: publickey Offering public key: /home/cdr/.ssh/id_rsa Server accepts key: pkalg ssh-rsa blen 279 read PEM private key done: type RSA Authentication succeeded (publickey). Look at the output: You're using the wrong keys with the curl command. 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
Re: ssh public key authentication problem using curl
On 11/3/2011 10:51 AM, Andrey Repin wrote: What was exact command? curl -v -O sftp://dell03/cygdrive/f/transit_ext/this_is_external_drive.txt (without the newline. I can't get rid of it using the Thunderbird newsreader to write this reply.) -- 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 public key authentication problem using curl
On 11/3/2011 6:08 PM, Yaakov (Cygwin/X) wrote: Look at the output: You're using the wrong keys with the curl command. How do I get them right? Why does curl insist on using the DSA key, when ssh is quite happy with the RSA key? I tried appending the public DSA key from the client to known_hosts on the server, but that didn't change anything. -- 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 public key authentication problem using curl
On 11/3/2011 6:57 PM, carolus wrote: I tried appending the public DSA key from the client to known_hosts on the server, but that didn't change anything. Correction: What I did was to append id_dsa.pub from the client to authorized_keys on the server, and to delete known_hosts on the server in case there was a conflict with prior data. There was no change in the behavior of either ssh -v host or curl -v -O sftp://host/path;. -- 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 execution of binary file
On 11/3/2011 4:56 PM, Eliot Moss wrote: Ok, so here's one thing about bash: to get it to run an *executable* (as opposed to a *script*), you need to say bash -c FLEXPART_GFORTRAN. You might try strace on that. In addition to the objdump suggestion. I have a moment to expand on this a little. The 80-byte read we saw was bash looking at the beginning of what it that was supposed to be a script (not a binary) and seeing if it really appeared to be a script. I did not look like a script, so bash gave up. (It checks whether the first line is all printable characters or white space.) Best -- Eliot Moss -- 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: Why 'script' utility require SHELL (and work fine under Linux)?
Le 14/10/2011 11:43, Oleksandr Gavenko a écrit : Look to my session: well, you session isn't very clear, however... As you can see first time script does not use SHELL, second time use it and third tie use it. So SHELL env var does not exported by bash... well, shells doesn't export anything except variables already exported at shell invocation or using the export builtin. Why? so, under unix like, $SHELL is positionned by login or whatever process (sshd, telnetd, X gui, etc.) which launch the interactive shell. under cygwqin, $SHELL is well positionned when connected through the network (sshd) but not when launched by cygwin.bat. Is this right add export SHELL to '~/.bashrc'? .bash_profile is more appropriate. the base-file maintainer has been BCC'ed to add the export SHELL to the /etc/profile. Regards, Cyrille Lefevre -- mailto:cyrille.lefevre-li...@laposte.net -- 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
Updated: bzr 2.4.2-1 -- Python based distributed version control (DVCS)
PACKAGE DESCRIPTION === Home page: http://bazaar.canonical.com License : GPL (Bzr is part of GNU project) Distributed version control that is used in projects like managing Ubuntu packages http://ubuntulinux.org and it is one of the funded projects of Canonical. - Uses one .bzr directory at the top of the tree - The user interface is simple and familiar to people with experience from CVS or Subversion. - Offers a choice between centralized and decentralized/diconnected work. - Strong security. History can be GPG-signed to protect against man-in-the-middle attacks, bad mirrors, server intrusion or data corruption. CHANGES SINCE LAST RELEASE == https://launchpad.net/bzr/+announcements http://doc.bazaar.canonical.com/bzr.dev/en/release-notes/index.html http://doc.bazaar.canonical.com/en/ INSTALL OR UPGRADE NOTES Upgrade existing branches to new format with commands: bzr infoTo see current repository format bzr reconcile To correct metadata prior upgrade bzr upgrade To convert repository to latest format bzr packTo make repository faster Following additional Cygwin modules can be also installed: python-paramiko - for ssh/sftp support python-crypto - required by paramiko 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(at)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.com(at)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.
Updated: mercurial-1.9.3-1 -- Python based distributed version control (DVCS)
PACKAGE DESCRIPTION === Homepage: http://mercurial.selenic.com License : GPL Distributed, efficient Python based source control system. Mercurial is designed for efficient handling of very large distributed projects. CHANGES SINCE LAST RELEASE == See http://mercurial.selenic.com/wiki/WhatsNew INSTALL OR UPGRADE NOTES Standard Cygwin install. For more information, see http://mercurial.selenic.com/wiki/UpgradeNotes 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(at)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.com(at)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.
New package: libid3tag-0.15.1b-10
The following packages have been added to the Cygwin distribution: *** libid3tag0-0.15.1b-10 *** libid3tag-devel-0.15.1b-10 libid3tag is a library for reading ID3 tags in audio files, both ID3v1 and the various versions of ID3v2. -- Yaakov Cygwin/X CYGWIN-ANNOUNCE UNSUBSCRIBE INFO If you want to unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then 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 If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL.
New package: source-highlight-3.1.5-1
The following package has been added to the Cygwin distribution: *** source-highlight-3.1.5-1 *** libsource-highlight4-3.1.5-1 *** libsource-highlight-common-3.1.5-1 *** libsource-highlight-devel-3.1.5-1 GNU Source-highlight is a utility which creates documents with syntax-highlighting from source files. -- Yaakov Cygwin/X CYGWIN-ANNOUNCE UNSUBSCRIBE INFO If you want to unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then 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 If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL.
