Re: Illegal character ^M
frenco schreef, Op 29-11-2011 19:57: I have a problem with a character. I think it's a conversion problem between dos and unix. I have a variable that is a float value. When I print it with the echo command i get: 0.495959 But when I try to make an operation on that value with the bc command (I am not sure how to write the bc command). echo $mean *1000 |bc I get: (standard_in) 1 : illegal character: ^M I already use the dos2unix command on my .sh file. I think it's because my variable have the ^M character (not printed with the echo command) How can i eliminate this error? Hi, Dos2unix will convert only DOS line breaks to Unix line breaks. Meaning \r\n to \n. When you see a single \r (^M), without a following \n, this is a Mac line break. Dos2unix will leave Mac line breaks alone. So you need to run mac2unix instead of dos2unix on the file. regards, -- Erwin Waterlander http://waterlan.home.xs4all.nl/ -- 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
libneon27 requires libproxy1 which requires libglib2.0_0
After running setup.exe to add a package I noticed something had decided to pull in some gnome libraries. As best I can tell its due to libneon27 requiring libproxy1 though I may be missing something else. I did manage to find this regarding libproxy. >From http://cygwin.com/ml/cygwin/2010-05/msg00605.html >libproxy pulls in these packages as dependencies for its GNOME and KDE >integration modules. libproxy was added as a libsoup-gnome dependency, >for which these deps are anyways required. But if neon is going to use >libproxy as well, these modules are not strictly required, so I removed >their deps from libproxy0/setup.hint (and from the upcoming libproxy1 >as well). So hopefully nothing else has changed and it's easy to fix. -- 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: Nuances of updating cygwin DLL
On Sat, Dec 03, 2011 at 04:00:26AM +, Andrew Hancock wrote: >I notice a thread on cygwin's inability to create folders/files on a network >drive (http://cygwin.com/ml/cygwin/2011-08/msg00136.html). Corinna's advice to >use to snapshot worked for me. However, I found that when I upgraded cygwin >some time afterward, the problem recurred. I had to re-do the advice that she >posted. You didn't "upgrade" Cygwin. You apparently downgraded from the newer 1.7.10S snapshot to the older 1.7.9 DLL. We haven't released Cygwin in a while but we are working on 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
Understanding versions of apps in cygwin suite
According to http://savannah.gnu.org/bugs/?func=detailitem&item_id=30309 , a bug with octave's wavread function was fixed in octave 3.2.3. My "cygcheck -cvs" shows an octave of 3.4.2, but I still get the bug. I was wondering if it is wise to assume that the app version number from cygcheck is the same as the version number from the gnu site? -- 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
Nuances of updating cygwin DLL
I notice a thread on cygwin's inability to create folders/files on a network drive (http://cygwin.com/ml/cygwin/2011-08/msg00136.html). Corinna's advice to use to snapshot worked for me. However, I found that when I upgraded cygwin some time afterward, the problem recurred. I had to re-do the advice that she posted. That thread was posted well in the past, and I wanted to check if the snapshot from that time has made it into the cygwin update. The most straightforward way seemed to be comparing dll file dates. To find what file was relevant, I did "cygcheck -cvs" and used vim to search for the pattern "cygwin\f*\.dll" (without quotes), which showed cygwin1.dll. The page http://cygwin.com/packages/cygwin/cygwin-1.7.9-1 showed that cygwin1.dll is still dated 29 Mar 2011, which means it's from well before the above thread. Approximately how often do the solutions in the snapshots get incorporated into the packages that are installed/updated with Setup.exe? The reason why I wanted to update cygwin was to update octave. It's wavread function has a bug, and I wanted to see if it was solved. Since I suspect that the cygwin.dll is pretty central to the unix environment offered to applications, would it be wise to update octave without udpating cygwin? (My next step is to search for octave release notes to determine whether the bug is fixed in the version that comes with cygwin). -- 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
[SOLVED:] Re: best way to prevent a cygwin build?
On 12/2/2011 10:49 AM, Dave Korn wrote: Well, in this particular case: ifeq (Cygwin, $(shell uname -o)) $(error This project does not build in Cygwin) endif Can be placed anywhere in the makefile, no need to modify the build rules. cheers, DaveK Csaba, Warren, and Dave: Thanks for all of your replies. The syntax/line: +++ $(error This project does not build in Cygwin) +++ is exactly what I was looking for as I didn't know how to force an exit. I just tried it out and it works like a champ. I also looked it up in GNU make man pages and it is there ... I don't know how I missed it last night as I "thought" I checked for error. My oversight on missing it, it was probably too late in the evening. Paul -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Redirecting output from running proc doesn't modify the "last modified time" field for target file
In my experience such metadata tends to be updated when the file is closed, but not necessarily before that time. This may be different from Unix, but (as mentioned) is probably not something cygwin can "fix". Best wishes -- 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: Redirecting output from running proc doesn't modify the "last modified time" field for target file
On 12/02/2011 11:50 AM, Jon Clugston wrote: > While this loop is running, the timestamp on "x.log" doesn't change > (whereas on Linux it changes every 10 seconds). It sure looks to me > that Windows just doesn't bother updating the file timestamp while it > is open. I don't know if this update is required by POSIX - I would > doubt that it is. POSIX requires that any write() to an open file mark it for update; the update doesn't have to occur right away (so you can batch up several writes, but only change the mtime metadata once at the end of the batch), but it DOES require that stat() and several similar functions flush all marked updates prior to exposing timestamps to the user. So yes, Windows is violating POSIX, and I have no idea whether cygwin can work around it. -- Eric Blake ebl...@redhat.com+1-919-301-3266 Libvirt virtualization library http://libvirt.org signature.asc Description: OpenPGP digital signature
[ANNOUNCEMENT] Updated: make-3.82.90-1
I've made a new version of make available for installation. This is a refresh against current CVS. The appropriate contents of the NEWS file for this snapshot are below. Note that this version of make continues to eschew support for MS-DOS paths as mentioned here: http://cygwin.com/ml/cygwin/2010-08/threads.html#00223 If you need a version of make which understands MS-DOS path please check out the MinGW project at http://mingw.org/ *** 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 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 web address. Changes from make NEWS file: Version 3.82.90 A complete list of bugs fixed in this version is available here: http://sv.gnu.org/bugs/index.php?group=make&report_id=111&fix_release_id=101&set=custom * WARNING: Backward-incompatibility! This version of make adheres to the POSIX backslash/newline handling, introducing the following differences: * Each backslash/newline in a variable value is replaced with a space; multiple consecutive backslash/newlines do not condense into one space. * In recipes, a recipe prefix following a backslash-newlines is removed. * New feature: The "job server" capability is now supported on Windows. Implementation contributed by Troy Runkel * New feature: "!=" shell assignment operator as an alternative to the $(shell ...) function. Implemented for compatibility with BSD makefiles. WARNING: Backward-incompatibility! Variables ending in "!" previously defined as "variable!= value" will now be interpreted as shell assignment. Change your assignment to add whitespace between the "!" and "=": "variable! = value" * New command line option: --trace enables tracing of targets. When enabled the recipe to be invoked is printed even if it would otherwise be suppressed by .SILENT or a "@" prefix character. Also before each recipe is run the makefile name and linenumber where it was defined are shown as well as the prerequisites that caused the target to be considered out of date. * On failure, the makefile name and linenumber of the recipe that failed are shown. * A .RECIPEPREFIX setting is remembered per-recipe and variables expanded in that recipe also use that recipe prefix setting. * In -p output, .RECIPEPREFIX settings are shown and all target-specific variables are output as if in a makefile, instead of as comments. Version 3.82 A complete list of bugs fixed in this version is available here: http://sv.gnu.org/bugs/index.php?group=make&report_id=111&fix_release_id=104&set=custom * Compiling GNU make now requires a conforming ISO C 1989 compiler and standard runtime library. * WARNING: Backward-incompatibility! The POSIX standard for make was changed in the 2008 version in a fundamentally incompatible way: make is required to invoke the shell as if the '-e' flag were provided. Because this would break many makefiles that have been written to conform to the original text of the standard, the default behavior of GNU make remains to invoke the shell with simply '-c'. However, any makefile specifying the .POSIX special target will follow the new POSIX standard and pass '-e' to the shell. See also .SHELLFLAGS below. * WARNING: Backward-incompatibility! The '$?' variable now contains all prerequisites that caused the target to be considered out of date, even if they do not exist (previously only existing targets were provided in $?). * WARNING: Backward-incompatibility! Wildcards were not documented as returning sorted values, but the results have been sorted up until this release.. If your makefiles require sorted results from wildcard expansions, use the $(sort ...) function to request it explicitly. * WARNING: Backward-incompatibility! In previous versions of make it was acceptable to list one or more explicit targets followed by one or more pattern targets in the same rule and it worked "as expected". However, this was not documented as acceptable and if you listed any explicit targets AFTER the pattern targets, the entire rule would be mis-parsed. This release removes this ability completely: make will generate an error message if you mix explicit and pattern targets in the same rule. * WARNING: Backward-incompatibility! As a result of parser enhancements, three backward-compatibility issues exist: first, a prerequisite containing an "=" cannot be escaped with a backslash any longer. You must create a variable containing an "=" and use that variable in the prerequisite. Second, variable names can no longer contain whitespace, unless you put the whitespace in a variable and use the variable. Thir
Re: Redirecting output from running proc doesn't modify the "last modified time" field for target file
On Fri, Dec 2, 2011 at 1:42 PM, ajshower wrote: > >>IMHO, this is a very dubious "feature" to depend upon. If you want to >>know if the file has changed, why not check its length instead? > > I have switched to using the length instead but I was interested in what > people thought of the issue. > > I'm having trouble reproducing this using just Cygwin so I'm not presenting > the problem accurately. My process is to call Runtime.getRuntime.exec() > within a java process which opens cygwin/bin/bash.exe and then runs the > redirection command from within the bash. From the same java process that > called exec(), I'm trying to monitor the last modified time based on what's > going on in the previously called bash.exe. That does sound pretty > convoluted. I guess it's some kind of scope problem, but checking length() > is working, so it's all moot anyway. > I reproduced your symptoms with this simple shell script: while sleep 10 ; do echo done >x.log & While this loop is running, the timestamp on "x.log" doesn't change (whereas on Linux it changes every 10 seconds). It sure looks to me that Windows just doesn't bother updating the file timestamp while it is open. I don't know if this update is required by POSIX - I would doubt that it is. Jon -- 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: best way to prevent a cygwin build?
On 02/12/2011 09:47, Csaba Raduly wrote: > On Fri, Dec 2, 2011 at 8:46 AM, Paul Allen Newell wrote: >> I am not happy with having to run two separate source trees and would like a >> way (as in "best standard") to add something to any Maya makefile which will >> prevent execution if it is being compiled on Cygwin. The best I have been >> able to come up with is a check under each make directive, but that's alot >> of exceptions where I would think only one would be necessary. >> >> I searched the GNU make docs and googled for such, but the best I could see >> were bailout rules under a given make rule directive. I can find out whether >> I need to bail by the test "ifeq (Cygwin, $(shell uname -o))" but can't >> figure out a way to have the makefile ask this question once for the entire >> set of make directives in it. > > ifeq (Cygwin, $(shell uname -o)) > PLATFORM := CYGWIN > endif Well, in this particular case: ifeq (Cygwin, $(shell uname -o)) $(error This project does not build in Cygwin) endif Can be placed anywhere in the makefile, no need to modify the build rules. 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: Redirecting output from running proc doesn't modify the "last modified time" field for target file
>IMHO, this is a very dubious "feature" to depend upon. If you want to >know if the file has changed, why not check its length instead? I have switched to using the length instead but I was interested in what people thought of the issue. I'm having trouble reproducing this using just Cygwin so I'm not presenting the problem accurately. My process is to call Runtime.getRuntime.exec() within a java process which opens cygwin/bin/bash.exe and then runs the redirection command from within the bash. From the same java process that called exec(), I'm trying to monitor the last modified time based on what's going on in the previously called bash.exe. That does sound pretty convoluted. I guess it's some kind of scope problem, but checking length() is working, so it's all moot anyway. I'll close this thread. -Alex -- View this message in context: http://old.nabble.com/Redirecting-output-from-running-proc-doesn%27t-modify-the-%22last-modified-time%22-field-for-target-file-tp32903475p32904332.html Sent from the Cygwin list mailing list archive at Nabble.com. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: File size error using sftp
On 12/2/2011 7:50 AM, Andrew Erskine wrote: Im using an enterprise tool to sftp files from a remote server but it is failing with the error .. [snip] > If i try and grab the file manually it works fine .. Soyou're asking us to debug Unspecified Enterprise Tool Which Is Not Cygwin 2012 Edition (TM)? I assume the 2012 Edition of Unspecified Enterprise Tool Which Is Not Cygwin uses Cygwin's sftp, else it wouldn't be on topic here. If so, why doesn't it use scp? scp is a better tool for automated copying. Both scp and sftp ride on top of SSH, doing roughly the same thing, but with a different UI. scp mimics cp(1), while sftp mimics ftp(1). That makes sftp better for interactive use when the user isn't sure exactly what they want to copy before they connect. The equivalent scp to what you show in your sftp session is: scp ehealth@2e2ehpr01:modules/remotepoller/spool/rpCfg.3952.1322675313.dci . (Quoted to prevent my mailer from wrapping the line.) C:\Users\ehealth> C:\Users\ehealth>sftp ehealth@2e2ehpr01 Connected to 2e2ehpr01. cygwin warning: MS-DOS style path detected: Now you have a second opinion telling you to stop using CMD and DOS style paths with Cygwin. This one comes from the developers of the core Cygwin DLL, rather than some random guy answering questions on the Internet. No entry for terminal type "nutc"; Upgrading to the latest Cygwin and using its new MinTTY based Bash shell icon will fix this. It doesn't have anything to do with your present problem, but the misconfiguration it warns about might cause some other failure for you down the line. -- 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: best way to prevent a cygwin build?
On 12/2/2011 12:46 AM, Paul Allen Newell wrote: I am not happy with having to run two separate source trees and would like a way (as in "best standard") to add something to any Maya makefile which will prevent execution if it is being compiled on Cygwin. You might get better answers if you give an example of what you mean by "prevent execution". Not because we don't know what that means in general, but because it *is* too general. For example, if what you were after is to have some programs in a system compiled conditionally, Automake + Autoconf makes that easy: https://www.gnu.org/s/hello/manual/automake/Conditional-Programs.html If you want something else suppressed, the answer might be different. Generally speaking, any time you want to do some up-front tests for platform compatibility issues that affect how a program gets built, Autoconf is probably a good answer. It is not a pretty tool, but it's one of those tools that keeps getting reinvented poorly, so it remains the most popular out of lack of better alternatives. On one of my projects, I use another Automake competitor, Bakefile. Bakefile builds Autoconf Makefile.in files, generic GNU Makefiles, Visual C++ project files, Xcode project files, etc., all from a single high-level description of what you want built. You can include things conditionally based on platform or pretty much any criterion you can code up in a Python extension to Bakefile. Bakefile is not in the Cygwin package repo, however, partly because it doesn't build cleanly on Cygwin. The native Windows port works just fine with Cygwin, though. You might also look at cmake, which competes with the Autotools and Bakefile, and *is* in the Cygwin package repo. I can't tell you anything more about it. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Redirecting output from running proc doesn't modify the "last modified time" field for target file
On Fri, Dec 2, 2011 at 11:51 AM, ajshower wrote: > > I've got a bash script running in Cygwin whose output has been redirected to > another file. MS-DOS exhibits this same behavior if I run the bash script > as a batch job. > > bash.exe &> log.txt > > Adding content to log.txt through redirection does not change log.txt's last > modified time while bash.exe is executing. > > Baseline: > # ls -la --full-time log.txt > -r-xr-x---+ 1 user Domain Users 66455 2011-11-30 16:16:45.246664800 > -0500 log.txt > > Some time later: > # ls -la --full-time log.txt > -r-xr-x---+ 1 user Domain Users 66838 2011-11-30 16:16:45.246664800 > -0500 log.txt > > Note that even though log.txt has gotten larger, the last modified time has > not changed. The last modified time is updated only when bash.exe > terminates. > > Ubuntu 11.04 handles this scenario, IMO, correctly. Is there a way I can > get the last modified time to be updated when the content of the file > changes and while bash.exe is executing? > > Cygwin: CYGWIN_NT-6.1 > MS-DOS: Microsoft Windows [Version 6.1.7601] > I don't see how this could be a Cygwin issue. If writing to a file (while it is open) doesn't immediately update the last modified time on Windows, there is no reasonable way for Cygwin to "fix" that. IMHO, this is a very dubious "feature" to depend upon. If you want to know if the file has changed, why not check its length instead? Jon -- 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
Redirecting output from running proc doesn't modify the "last modified time" field for target file
I've got a bash script running in Cygwin whose output has been redirected to another file. MS-DOS exhibits this same behavior if I run the bash script as a batch job. bash.exe &> log.txt Adding content to log.txt through redirection does not change log.txt's last modified time while bash.exe is executing. Baseline: # ls -la --full-time log.txt -r-xr-x---+ 1 user Domain Users 66455 2011-11-30 16:16:45.246664800 -0500 log.txt Some time later: # ls -la --full-time log.txt -r-xr-x---+ 1 user Domain Users 66838 2011-11-30 16:16:45.246664800 -0500 log.txt Note that even though log.txt has gotten larger, the last modified time has not changed. The last modified time is updated only when bash.exe terminates. Ubuntu 11.04 handles this scenario, IMO, correctly. Is there a way I can get the last modified time to be updated when the content of the file changes and while bash.exe is executing? Cygwin: CYGWIN_NT-6.1 MS-DOS: Microsoft Windows [Version 6.1.7601] Thanks -- View this message in context: http://old.nabble.com/Redirecting-output-from-running-proc-doesn%27t-modify-the-%22last-modified-time%22-field-for-target-file-tp32903475p32903475.html Sent from the Cygwin list mailing list archive at Nabble.com. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated: stunnel 4.49-1
A new version of stunnel, 4.49-1, is available in the Cygwin distribution. This is a new upstream release, with assorted minor updates and bug fixes since the previous Cygwin release, 4.44-1. You can read the upstream changelog at http://www.stunnel.org/news/. stunnel is a program that allows you to encrypt arbitrary TCP connections inside SSL (Secure Sockets Layer). stunnel can allow you to secure non-SSL aware daemons and protocols (like POP, IMAP, LDAP, etc) by having stunnel provide the encryption, requiring no changes to the daemon's code. Andrew E. Schulman *** To update your installation, click on the "Install Cygwin now" link on the http://cygwin.com/ web page. This downloads setup.exe to your system. Then, run setup and answer all of the questions. *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce 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 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
File size error using sftp
Im using an enterprise tool to sftp files from a remote server but it is failing with the error .. Thursday, December 01, 2011 11:01:40 Error nhiRpImport Pgm nhiRpImport: File size error for file 'D:/ehealth/modules/remotePoller/importData/poll/2e2ehpr01/config/rpCfg.3952.1322675313.dci' check data connection to remote site and ftp server configuration. Thursday, December 01, 2011 11:01:40 Error nhiRpImport Pgm nhiRpImport: File transfer from host '2e2ehpr01' failed files: '' check data connection to remote site. If i try and grab the file manually it works fine .. any ideas or thoughts on a method to troubleshoot ? C:\Users\ehealth> C:\Users\ehealth>sftp ehealth@2e2ehpr01 Connected to 2e2ehpr01. cygwin warning: MS-DOS style path detected: D:\nutcroot\usr\lib\terminfo Preferred POSIX equivalent is: /cygdrive/d/nutcroot/usr/lib/terminfo CYGWIN environment variable option "nodosfilewarning" turns off this warning. Consult the user's guide for more details about POSIX paths: http://cygwin.com/cygwin-ug-net/using.html#using-pathnames No entry for terminal type "nutc"; using dumb terminal settings. No entry for terminal type "nutc"; using dumb terminal settings. sftp> lcd You must specify a path after a lcd command. sftp> pwd Remote working directory: /cygdrive/d/ehealth sftp> cd modules/remotepoller/spool sftp> pwd Remote working directory: /cygdrive/d/ehealth/modules/remotepoller/spool sftp> sftp> get rpCfg.3952.1322675313.dci Fetching /cygdrive/d/ehealth/modules/remotepoller/spool/rpCfg.3952.1322675313.dci to rpCfg.3952.1322675313.dci /cygdrive/d/ehealth/modules/remotepoller/spoo 100% 16KB 15.8KB/s 00:01 sftp> sftp> bye thanks. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple -- 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
File size error using sftp
Im using an enterprise tool to sftp files from a remote server but it is failing with the error .. Thursday, December 01, 2011 11:01:40 Error nhiRpImport Pgm nhiRpImport: File size error for file 'D:/ehealth/modules/remotePoller/importData/poll/2e2ehpr01/config/rpCfg.3952.1322675313.dci' check data connection to remote site and ftp server configuration. Thursday, December 01, 2011 11:01:40 Error nhiRpImport Pgm nhiRpImport: File transfer from host '2e2ehpr01' failed files: '' check data connection to remote site. If i try and grab the file manually it works fine .. any ideas or thoughts on a method to troubleshoot ? C:\Users\ehealth> C:\Users\ehealth>sftp ehealth@2e2ehpr01 Connected to 2e2ehpr01. cygwin warning: MS-DOS style path detected: D:\nutcroot\usr\lib\terminfo Preferred POSIX equivalent is: /cygdrive/d/nutcroot/usr/lib/terminfo CYGWIN environment variable option "nodosfilewarning" turns off this warning. Consult the user's guide for more details about POSIX paths: http://cygwin.com/cygwin-ug-net/using.html#using-pathnames No entry for terminal type "nutc"; using dumb terminal settings. No entry for terminal type "nutc"; using dumb terminal settings. sftp> lcd You must specify a path after a lcd command. sftp> pwd Remote working directory: /cygdrive/d/ehealth sftp> cd modules/remotepoller/spool sftp> pwd Remote working directory: /cygdrive/d/ehealth/modules/remotepoller/spool sftp> sftp> get rpCfg.3952.1322675313.dci Fetching /cygdrive/d/ehealth/modules/remotepoller/spool/rpCfg.3952.1322675313.dci to rpCfg.3952.1322675313.dci /cygdrive/d/ehealth/modules/remotepoller/spoo 100% 16KB 15.8KB/s 00:01 sftp> sftp> bye thanks. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: best way to prevent a cygwin build?
On Fri, Dec 2, 2011 at 8:46 AM, Paul Allen Newell wrote: > Dear Cygwin: > > I have a network of Fedora machines and WinXP running Cygwin. Most of the > projects I work on can be compiled/linked/run under both, but there are > exceptions. As in Maya ... > > I am not happy with having to run two separate source trees and would like a > way (as in "best standard") to add something to any Maya makefile which will > prevent execution if it is being compiled on Cygwin. The best I have been > able to come up with is a check under each make directive, but that's alot > of exceptions where I would think only one would be necessary. > > I searched the GNU make docs and googled for such, but the best I could see > were bailout rules under a given make rule directive. I can find out whether > I need to bail by the test "ifeq (Cygwin, $(shell uname -o))" but can't > figure out a way to have the makefile ask this question once for the entire > set of make directives in it. ifeq (Cygwin, $(shell uname -o)) PLATFORM := CYGWIN endif . . . ifeq ($(PLATFORM), CYGWIN) # Cygwin-specific stuff endif -- GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++ The Tao of math: The numbers you can count are not the real numbers. Life is complex, with real and imaginary parts. "Ok, it boots. Which means it must be bug-free and perfect. " -- Linus Torvalds "People disagree with me. I just ignore them." -- Linus Torvalds -- 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
