whois --version
Setup tells me that I am running whois version 5.0.11-1, however, whois does not honor the --version option that it advertises: $ type whois whois is hashed (/usr/bin/whois) $ whois --version whois: unknown option -- - Usage: whois [OPTION]... OBJECT... -l one level less specific lookup [RPSL only] -L find all Less specific matches -m find first level more specific matches -M find all More specific matches -c find the smallest match containing a mnt-irt attribute -x exact match [RPSL only] -d return DNS reverse delegation objects too [RPSL only] -i ATTR[,ATTR]... do an inverse lookup for specified ATTRibutes -T TYPE[,TYPE]... only look for objects of TYPE -K only primary keys are returned [RPSL only] -r turn off recursive lookups for contact information -R force to show local copy of the domain object even if it contains referral -a search all databases -s SOURCE[,SOURCE]... search the database from SOURCE -g SOURCE:FIRST-LAST find updates from SOURCE from serial FIRST to LAST -t TYPErequest template for object of TYPE ('all' for a list) -v TYPErequest verbose template for object of TYPE -q [version|sources|types] query specified server info [RPSL only] -F fast raw output (implies -r) -h HOSTconnect to server HOST -p PORTconnect to PORT -H hide legal disclaimers --verboseexplain what is being done --help display this help and exit --versionoutput version information and exit $ --Ken Nellis
Re: CMD.EXE able to create files in directories on a shared drive, but bash in cygwin is unable to
Hello, This one is a follow-up for http://cygwin.com/ml/cygwin/2011-05/msg00183.html On 2011-05-12 09:47:15 -0600 Keith Christian wrote: This permissions problem has existed for awhile, and I'd like to find a solution. Same for me. CMD.EXE is able to create files inside directories on a standard Windows share, but from a Bash shell on Cygwin, a permission denied message occurs, and this is in most if not all directories: Same for me. I use tcsh. jupiter% uname -a CYGWIN_NT-5.1 TOLX300043890 1.7.10s(0.244/5/3) 20110510 19:08:34 i686 Cygwin jupiter% (I use the last snapshot) ===CMD.EXE=== S:\historic>cacls S:\historic S:\historic DT\AMNO:(OI)(CI)F (OI)(CI)R (OI)(CI)C S:\historic>echo foo > foo S:\historic>cacls foo S:\historic\foo DT\AMNO:F R C S:\historic>dir foo Volume in drive S is Data Volume Serial Number is 84E6-0A33 Directory of S:\historic 2011-05-13 14:55 6 foo 1 File(s) 6 bytes 0 Dir(s) 449 445 888 bytes free ===TCSH/CYGWIN=== jupiter% pwd /cygdrive/s/historic jupiter% ls -dl . d- 1 denis59 Domain Users 0 May 13 14:54 ./ jupiter% ls -dl foo -- 1 denis59 Domain Users 6 May 13 14:54 foo jupiter% echo foo2 > foo2 foo2: Permission denied. My disk has exactly the same properties as in the original message (except for Device Type 6 instead of 7): jupiter% /usr/lib/csih/getVolInfo /cygdrive/s Device Type: 6 Characteristics: 10 Volume Name: Serial Number : 2229668403 Max Filenamelength : 255 Filesystemname : Flags : 700ff FILE_CASE_SENSITIVE_SEARCH : TRUE FILE_CASE_PRESERVED_NAMES : TRUE FILE_UNICODE_ON_DISK: TRUE FILE_PERSISTENT_ACLS: TRUE FILE_FILE_COMPRESSION : TRUE FILE_VOLUME_QUOTAS : TRUE FILE_SUPPORTS_SPARSE_FILES : TRUE FILE_SUPPORTS_REPARSE_POINTS: TRUE FILE_SUPPORTS_REMOTE_STORAGE: FALSE FILE_VOLUME_IS_COMPRESSED : FALSE FILE_SUPPORTS_OBJECT_IDS: TRUE FILE_SUPPORTS_ENCRYPTION: TRUE FILE_NAMED_STREAMS : TRUE FILE_READ_ONLY_VOLUME : FALSE FILE_SEQUENTIAL_WRITE_ONCE : FALSE FILE_SUPPORTS_TRANSACTIONS : FALSE And the strace is similar, with the same requested access bits. jupiter% strace -o /tmp/bash.trace bash -c 'echo foo2 > foo2' jupiter% grep 'open: C022' /tmp/bash.trace 65 126396 [main] bash 5412 fhandler_base::open: C022 = NtCreateFile (0x0, 40160080, \??\S:\historic\foo2, io, NULL, 80, 7, 5, 4020, NULL, 0) My Windows is XP SP3. I'm a normal user. I've installed Cygwin "Just Me". Now, if i only touch the foo, or if i write inside it, or if i replace it, it works: jupiter% ls -dl foo -- 1 denis59 Domain Users 6 May 13 14:54 foo jupiter% touch foo jupiter% ls -dl foo -- 1 denis59 Domain Users 6 May 13 15:12 foo jupiter% echo foo >> foo jupiter% ls -dl foo -- 1 denis59 Domain Users 10 May 13 15:15 foo jupiter% od -c foo 000 f o o \r \n f o o \n 012 jupiter% echo foo >! foo<- remember, i'm under tcsh jupiter% ls -dl foo -- 1 denis59 Domain Users 4 May 13 15:29 foo jupiter% jupiter% strace -o /tmp/bash.trace2 bash -c 'echo foo >> foo' jupiter% strace -o /tmp/bash.trace3 bash -c 'echo foo > foo' With the corresponding line in bash.trace2 is: 51 128428 [main] bash 4300 fhandler_base::open: 0 = NtCreateFile (0x650, 40120080, \??\S:\historic\foo, io, NULL, 80, 7, 3, 4020, NULL, 0) and in bash.trace3: 49 150149 [main] bash 4948 fhandler_base::open: 0 = NtCreateFile (0x650, 40120080, \??\S:\historic\foo, io, NULL, 80, 7, 5, 4020, NULL, 0) The flag WRITE_DAC has disappeared in these cases. So it seems we have to dig into WRITE_DAC. Best regards. Denis Excoffier. This message was sent using IMP, the Internet Messaging Program. -- 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: Broken pipe / scp
On Fri, May 13, 2011 at 12:46:48PM +0200, David Sastre wrote: >Hello, > >I'm having trouble with scp in a win7 box using > >CYGWIN_NT-6.1 win7 1.7.10s(0.244/5/3) 20110510 19:08:34 i686 Cygwin > >Scp as client works ok, I can 'scp file user@remote:/path/file' >without problems from cygwin to GNU/Linux. > >But trying to scp from remote (GNU/Linux) to local (cygwin), fails >with broken pipe error. I can duplicate this. I'll take a look. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: CMD.EXE able to create files in directories on a shared drive, but bash in cygwin is unable to
On May 13 15:42, EXCOFFIER Denis wrote: > Hello, > > This one is a follow-up for http://cygwin.com/ml/cygwin/2011-05/msg00183.html > > On 2011-05-12 09:47:15 -0600 Keith Christian wrote: > >This permissions problem has existed for awhile, and I'd like to find > a solution. > Same for me. > > >CMD.EXE is able to create files inside directories on a standard > >Windows share, but from a Bash shell on Cygwin, a permission denied > >message occurs, and this is in most if not all directories: > Same for me. I use tcsh. > > jupiter% uname -a > CYGWIN_NT-5.1 TOLX300043890 1.7.10s(0.244/5/3) 20110510 19:08:34 i686 Cygwin > jupiter% > > (I use the last snapshot) > > > ===CMD.EXE=== > S:\historic>cacls S:\historic > S:\historic DT\AMNO:(OI)(CI)F > (OI)(CI)R > (OI)(CI)C > [...] > And the strace is similar, with the same requested access bits. > > jupiter% strace -o /tmp/bash.trace bash -c 'echo foo2 > foo2' > jupiter% grep 'open: C022' /tmp/bash.trace >65 126396 [main] bash 5412 fhandler_base::open: C022 = > NtCreateFile (0x0, 40160080, \??\S:\historic\foo2, io, NULL, 80, 7, > 5, 4020, NULL, 0) > > [...] > and in bash.trace3: > 49 150149 [main] bash 4948 fhandler_base::open: 0 = NtCreateFile > (0x650, 40120080, \??\S:\historic\foo, io, NULL, 80, 7, 5, 4020, > NULL, 0) > > The flag WRITE_DAC has disappeared in these cases. > > So it seems we have to dig into WRITE_DAC. Ok, so, here's the problem. The WRITE_DAC permission is requested if and only if - the underlying file system supports ACLs, and - the underlying Cygwin mount point is set to "acl", and - the file does not exist yet. The reason to do that is that under the above condition we have to write the file DACL to set correct POSIX permissions. In former versions of Cygwin there was a bug in that the WRITE_DAC permission was not requested. This in turn required to open a second handle to the file just to set the file permissions correctly. However, since the success of the function writing the POSIX permissions is not tested, the open() function succeeded even though the permissions of the file couldn't be set. With the latest Cygwin this is not the case anymore. If you don't have the right to set permissions, the file open will fail entirely. Now, keep in mind that this affects only "acl" mount points. For some reason your share doesn't allow your account the WRITE_DAC permission. This is no problem for native Win32 tools, because they usually don't set file permissions. There are two solutions to this problem: - Check the permissions on the share, not only the ACL you see with cacls, but also the share permissions. - Set the Cygwin mount point to the share to "noacl". 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
Problem compiling with SSE intrinsics and -O3
(third try, wow you guys really don't want to receive emails !) Dear Sir/Madam I have come across a problem when trying to compile a simple program using Cygwin I just did a fresh install of Cygwin from the net on W7 32bit PC and included make/g++ to build my software (which builds fine on other native linux machines) When i try to compile the attached file i get this error $ gcc -msse2 -c -O3 test.c test.c: In function `vclrx': test.c:43: internal compiler error: in output_constant_pool, at varasm.c:3190 Please submit a full bug report, with preprocessed source if appropriate. See http://cygwin.com/problems.html> for instructions. Without the -O3 option all is well Help appreciated. Thanks Phil. #include #include void vclrx(float *fc, int k, int n, int f); void vclrx_csal( float *C, int K, int N, int XFLAG); void vclrx(float *fc, int k, int n, int f) { __m128 *pC = (__m128*)fc; __m128 c0,c1,c2,c3; if (k != 1) { printf("vmovx_csal\n"); vclrx_csal(fc,k,n,f); return; } if (n > 3) { c0 = _mm_xor_ps(c0,c0); while (n >= 4) { *pC++ = c0; n -= 4; } } return; } void vclrx_csal( float *C, int K, int N, int XFLAG) { ( void ) XFLAG; inti; float zero; zero = 0.0; C -= K; for ( i = 0; i < N; i++ ) { *( C += K ) = zero; } } -- 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: CMD.EXE able to create files in directories on a shared drive, but bash in cygwin is unable to
I asked our Windows admin to check permissions on the share. They are the same as everyone else's. I tried this entry in /etc/fstab, closed all Cygwin Bash windows, opened a window, unable to create files in /cygdrive/z or subdirectories within. Z: /cygdrive/z ntfs binary,noacl 0 0 Even when I own the directory, still cannot create anything within it. I don't understand why the directories all have 700 permission. I also can't chmod 755 any directories either: Fri May 13 10:23:27 (kchristian@some-machine) /cygdrive/z>ls -dl vimfiles/ drwx--+ 1 kchristian Domain Users 0 Aug 9 2010 vimfiles/ Fri May 13 10:23:30 (kchristian@some-machine) /cygdrive/z>touch vimfiles/foo2 touch: cannot touch `vimfiles/foo2': Permission denied Fri May 13 10:23:35 (kchristian@some-machine) /cygdrive/z>getfacl -a -d ./vimfiles/ # file: ./vimfiles/ # owner: kchristian # group: Domain Users I may ask our Windows Admin to open a BASH window on my workstation with "Run AsAdministrator" privileges, and ask him to chmod 755 all directories. =Keith -- 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: Fwd: octave updated to 3.4.0-3. Please test (strcat error)
This is a problem on Windows 7 Enterprise, 64-bit; cygwin 1.7.9-1; octave 3.4.0-3 Reinstalling Octave does not resolve rebaseall does not resolve Any suggestions on how to resolve? TIA, Jeff $ uname -a CYGWIN_NT-6.1-WOW64 JKLETSKY-T41 1.7.9(0.237/5/3) 2011-03-29 10:10 i686 Cygwin $ octave GNU Octave, version 3.4.0 Copyright (C) 2011 John W. Eaton and others. This is free software; see the source code for copying conditions. There is ABSOLUTELY NO WARRANTY; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. For details, type `warranty'. Octave was configured for "i686-pc-cygwin". Additional information about Octave is available at http://www.octave.org. Please contribute if you find this software useful. For more information, visit http://www.octave.org/help-wanted.html Read http://www.octave.org/bugs.html to learn how to submit bug reports. For information about changes from previous versions, type `news'. octave:1> plot([1 2 3], [1 2 3]) error: Invalid call to strcat. Correct usage is: -- Function File: strcat (S1, S2, ...) error: called from: error: /usr/share/octave/3.4.0/m/help/print_usage.m at line 87, column 5 error: /usr/share/octave/3.4.0/m/strings/strcat.m at line 92, column 5 error: /usr/share/octave/3.4.0/m/plot/__gnuplot_get_var__.m at line 113, column 11 error: /usr/share/octave/3.4.0/m/plot/__go_draw_axes__.m at line 40, column 18 error: /usr/share/octave/3.4.0/m/plot/__go_draw_figure__.m at line 167, column 19 error: /usr/share/octave/3.4.0/m/plot/__gnuplot_drawnow__.m at line 86, column 5 octave:2> quit terminate called after throwing an instance of 'octave_interrupt_exception' panic: Aborted -- stopping myself... attempting to save variables to `octave-core'... save to `octave-core' complete Aborted (core dumped) On Fri, Apr 8, 2011 at 5:51 AM, Christopher Faylor wrote: > On Thu, Apr 07, 2011 at 06:24:31PM -0400, Stan wrote: >>On Wed, Apr 06, 2011 at 10:05:24AM -0400, Christopher Faylor wrote: >>> On Wed, Apr 06, 2011 at 03:54:05PM +0900, Tatsuro MATSUOKA wrote: >>> >Hello >>> > >>> >I have confirmed that octave-3.4.0-3 fails to plot on cygwin 1.7.9-1 but >>> >not 1.7.8-1. >>> >>> We don't need confirmation that octave doesn't work. ?We need to know if >>> rebasing works around the problem. >> >>Here on Win 7 64bit I have: >>$ uname -a >>CYGWIN_NT-6.1-WOW64 darkstar 1.7.9(0.237/5/3) 2011-03-29 10:10 i686 Cygwin >> >>Cygwin Package Information >>Package ? ? ? ? ? ? ?Version ? ? ? ?Status >>cygwin ? ? ? ? ? ? ? 1.7.9-1 ? ? ? ?OK >>octave ? ? ? ? ? ? ? 3.4.0-3 ? ? ? ?OK >>gnuplot ? ? ? ? ? ? ?4.4.0-1 ? ? ? ?OK >> >> >>I did rebaseall and I still get the error: >> >>octave:1> t = 0:2*pi/100:2*pi; >>octave:2> plot(t,sin(t)) >>error: Invalid call to strcat. ?Correct usage is: >> >> -- Function File: ?strcat (S1, S2, ...) -- 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: CMD.EXE able to create files in directories on a shared drive, but bash in cygwin is unable to
On May 13 10:27, Keith Christian wrote: > I asked our Windows admin to check permissions on the share. They are > the same as everyone else's. > > I tried this entry in /etc/fstab, closed all Cygwin Bash windows, > opened a window, unable to create files in /cygdrive/z or > subdirectories within. > > Z: /cygdrive/z ntfs binary,noacl 0 0 That doesn't work. You must choose another path which doesn't start with the cygdrive prefix, for instance: Z: /mnt/z doesnt_matter binary,noacl 0 0 > Even when I own the directory, still cannot create anything within it. It has something to do with the share permissions, which disallow WRITE_DAC permissions(*). However, since I can't reproduce this problem, I have really no idea what combination of share permissions and/or maybe domain policy have this effect. Corinna (*) http://cygwin.com/ml/cygwin/2011-05/msg00197.html -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Problem compiling with SSE intrinsics and -O3
On 5/13/2011 12:15 PM, Morris, Philip wrote: (third try, wow you guys really don't want to receive emails !) Please submit a full bug report, with preprocessed source if appropriate. Seehttp://cygwin.com/problems.html> for instructions. Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple They probably don't like to see e-mails which ignore the instructions contained in them. How many people will be curious enough to try several of the compilers provided currently or in the past by cygwin setup.exe, not even knowing whether you're running one of those? -- Tim Prince -- 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 - Could not create directory 'c/.ssh'.
On 5/12/2011 4:55 PM, Tim Allen wrote: On 12/05/11 01:57, Larry Hall (Cygwin) wrote: On 5/11/2011 5:04 PM, Tim Allen wrote: Hi Larry On 11/05/11 15:45, Larry Hall (Cygwin) wrote: On 5/11/2011 6:44 AM, Tim Allen wrote: Hi I have happily used Cygwin ssh from "DOS" command prompt for many years but on upgrading to V1.7 get this error message. Further info: OS: Vista /etc/passwd line: tda:unused_by_nt/2000/xp:1000:513:U-laptop1\tda,S-1-5-21-2414507100-3802266639-3593817948-1000:/home/tda:/bin/bash The interesting thing is that if I open up a second command prompt and run an arbitrary cygwin command (like "less filename"). ssh successfully finds /home/tda/.ssh (but only for so long as that second command is running). I suspect this is something to do with the changes to mounts, but so far I've been unable to find a fix. I think we need more information about what you're actually doing and what your configuration is. Please review the problem reporting guidelines found here: Problem reports: http://cygwin.com/problems.html OK. Steps to reproduce: 1. Open command prompt, type: c:\ ssh fleet Could not create directory 'c/.ssh'. The authenticity of host 'fleet (192.168.1.30)' can't be established. RSA key fingerprint is 17:33:a7:32:cd:e1:04:ed:d7:3b:dc:11:c6:da:3c:42. Are you sure you want to continue connecting (yes/no)? 2. Open second command prompt, type: c:\ less main.c 3. Leave less running, return to first prompt and repeat login attempt: c:\ ssh fleet Linux fleet 2.6.32-5-686 #1 SMP Tue Mar 8 21:36:00 UTC 2011 i686 (login OK) cygcheck.out is output of cygcheck -s -v -r with less NOT running. cygcheck1.out is output of cygcheck -s -v -r with less running. The difference below looks relevant: cygcheck.out: Output from c:\cygwin\bin\id.exe UID: 0(tda) GID: 0(root) 0(root) 545(Users) Indeed. Some thoughts: 1. Check that you're using Cygwin's ssh. Yes, double checked. 2. Try unsetting "HOME" before running ssh. C:\>set HOME= C:\>ssh -v fleet OpenSSH_5.8p1, OpenSSL 0.9.8r 8 Feb 2011 debug1: Connecting to fleet [192.168.1.30] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file /.ssh/id_rsa type -1 ... ssh goes on to create /.ssh off of c:\cygwin and fails since no id_rsa files. Copying .ssh/ into c:\cygwin results in this working. Try: c:\>set HOME=/home/tda c:\>ssh -v fleet OpenSSH_5.8p1, OpenSSL 0.9.8r 8 Feb 2011 debug1: Connecting to fleet [192.168.1.30] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file /home/tda/.ssh/id_rsa type 1 ... (succeeds, but I need HOME to be "correct" for other apps) Try returning to Windows default: c:\>set HOME=c:\Users\tda.DCA c:\>ssh -v fleet OpenSSH_5.8p1, OpenSSL 0.9.8r 8 Feb 2011 debug1: Connecting to fleet [192.168.1.30] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/0 Could not create directory 'c/.ssh'. debug1: identity file c/.ssh/id_rsa type -1 Sorry, I cannot reproduce this, even with all my Cygwin processes stopped prior to running this: C:\>set HOME=c:\users\lhall C:\>ssh -v ds9 OpenSSH_5.8p1, OpenSSL 0.9.8r 8 Feb 2011 debug1: Reading configuration data /etc/ssh_config debug1: Connecting to ds9 [192.168.1.190] port 22. debug1: Connection established. debug1: identity file /home/lhall/.ssh/id_rsa type 1 ... (succeeds) But looking back at your '/etc/passwd' entry, you have: tda:unused_by_nt/2000/xp:1000:513:U-laptop1\tda,S-1-5-21-2414507100-3802266639-3593817948-1000:/home/tda:/bin/bash When I compare that to the home directory you want (HOME=c:\Users\tda.DCA), I'm wondering if you have a mismatch of usernames. What does 'id' tell you your user is? Also, I note that our debug output for 'ssh -v' differs. You may want to investigate that some too. Other stray ideas which may or may not be relevant: BLODA Downgrade OpenSSH -- Larry _ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Fwd: octave updated to 3.4.0-3. Please test (strcat error)
On Fri, May 13, 2011 at 6:46 PM, Jeffrey Kletsky wrote: > This is a problem on Windows 7 Enterprise, 64-bit; cygwin 1.7.9-1; octave > 3.4.0-3 > > Reinstalling Octave does not resolve > rebaseall does not resolve > > Any suggestions on how to resolve? > try downgrading cygwin to 1.7.8-1. On windows XP , it is the current workaround; but W7-64 is more weird and some people reported other faults. > TIA, > > Jeff Marco > > > > $ uname -a > CYGWIN_NT-6.1-WOW64 JKLETSKY-T41 1.7.9(0.237/5/3) 2011-03-29 10:10 i686 Cygwin > > $ octave > GNU Octave, version 3.4.0 > Copyright (C) 2011 John W. Eaton and others. > This is free software; see the source code for copying conditions. > There is ABSOLUTELY NO WARRANTY; not even for MERCHANTABILITY or > FITNESS FOR A PARTICULAR PURPOSE. For details, type `warranty'. > > Octave was configured for "i686-pc-cygwin". > > Additional information about Octave is available at http://www.octave.org. > > Please contribute if you find this software useful. > For more information, visit http://www.octave.org/help-wanted.html > > Read http://www.octave.org/bugs.html to learn how to submit bug reports. > > For information about changes from previous versions, type `news'. > > octave:1> plot([1 2 3], [1 2 3]) > error: Invalid call to strcat. Correct usage is: > > -- Function File: strcat (S1, S2, ...) > > error: called from: > error: /usr/share/octave/3.4.0/m/help/print_usage.m at line 87, column 5 > error: /usr/share/octave/3.4.0/m/strings/strcat.m at line 92, column 5 > error: /usr/share/octave/3.4.0/m/plot/__gnuplot_get_var__.m at line 113, > column 11 > error: /usr/share/octave/3.4.0/m/plot/__go_draw_axes__.m at line 40, column > 18 > error: /usr/share/octave/3.4.0/m/plot/__go_draw_figure__.m at line 167, > column 19 > error: /usr/share/octave/3.4.0/m/plot/__gnuplot_drawnow__.m at line 86, > column 5 > octave:2> quit > terminate called after throwing an instance of 'octave_interrupt_exception' > panic: Aborted -- stopping myself... > attempting to save variables to `octave-core'... > save to `octave-core' complete > Aborted (core dumped) > > > On Fri, Apr 8, 2011 at 5:51 AM, Christopher Faylor wrote: >> On Thu, Apr 07, 2011 at 06:24:31PM -0400, Stan wrote: >>>On Wed, Apr 06, 2011 at 10:05:24AM -0400, Christopher Faylor wrote: On Wed, Apr 06, 2011 at 03:54:05PM +0900, Tatsuro MATSUOKA wrote: >Hello > >I have confirmed that octave-3.4.0-3 fails to plot on cygwin 1.7.9-1 but >not 1.7.8-1. We don't need confirmation that octave doesn't work. ?We need to know if rebasing works around the problem. >>> >>>Here on Win 7 64bit I have: >>>$ uname -a >>>CYGWIN_NT-6.1-WOW64 darkstar 1.7.9(0.237/5/3) 2011-03-29 10:10 i686 Cygwin >>> >>>Cygwin Package Information >>>Package ? ? ? ? ? ? ?Version ? ? ? ?Status >>>cygwin ? ? ? ? ? ? ? 1.7.9-1 ? ? ? ?OK >>>octave ? ? ? ? ? ? ? 3.4.0-3 ? ? ? ?OK >>>gnuplot ? ? ? ? ? ? ?4.4.0-1 ? ? ? ?OK >>> >>> >>>I did rebaseall and I still get the error: >>> >>>octave:1> t = 0:2*pi/100:2*pi; >>>octave:2> plot(t,sin(t)) >>>error: Invalid call to strcat. ?Correct usage is: >>> >>> -- Function File: ?strcat (S1, S2, ...) > > > > > -- > 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
[ANNOUNCEMENT] Updated: git-1.7.5.1-1, git{k,-gui,-completion,-svn}-1.7.5.1-1
A new release of git, 1.7.5.1-1, has been uploaded, and will be available for use when your mirror catches up. This leaves 1.7.4-1 as previous. NEWS: = This is a new upstream release, with upstream release notes attached. See also the package documentation in /usr/share/doc/git/. When compiled out of the box, the upstream git maintainers cater to older cygwin releases, and intentionally disable certain features that have been reported on their mailing list, even though they work with the latest cygwin. Therefore, this build turns those features back on. However, it means that this version does assume that you are not using FAT or FAT32 to hold your repositories, since they do not store file permissions very accurately. DESCRIPTION: Git is popular version control system designed to handle very large projects with speed and efficiency; it is used mainly for various open source projects, most notably the Linux kernel. Git falls in the category of distributed source code management tools, similar to e.g. GNU Arch or Monotone (or BitKeeper in the proprietary world). Every Git working directory is a full-fledged repository with full revision tracking capabilities, not dependent on network access or a central server. UPDATE: === To update your installation, click on the "Install Cygwin now" link on the http://cygwin.com/ web page. This downloads setup.exe to your system. Save it and run setup, answer the questions and pick up 'git', 'gitk', 'git-gui', 'git-svn', and/or 'git-completion' from the 'Devel' category. DOWNLOAD: = Note that downloads from sourceware.org (aka cygwin.com) aren't allowed due to bandwidth limitations. This means that you will need to find a mirror which has this update, please choose the one nearest to you: http://cygwin.com/mirrors.html QUESTIONS: == If you want to make a point or ask a question the Cygwin mailing list is the appropriate place. -- Eric Blake volunteer cygwin git maintainer CYGWIN-ANNOUNCE UNSUBSCRIBE INFO: = To unsubscribe to 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@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. Git v1.7.5.1 Release Notes == Fixes since v1.7.5 -- * When an object "$tree:$path" does not exist, if $path does exist in the subtree of $tree that corresponds to the subdirectory the user is in, git now suggests using "$tree:./$path" in addition to the advice to use the full path from the root of the working tree. * The "--date=relative" output format used to say "X years, 12 months" when it should have said "X+1 years". * The smart-HTTP transfer was broken in 1.7.5 when the client needs to issue a small POST (which uses content-length) and then a large POST (which uses chunked) back to back. * "git clean" used to fail on an empty directory that is not readable, even though rmdir(2) could remove such a directory. Now we attempt it as the last resort. * The "--dirstat" option of "diff" family of commands used to totally ignore a change that only rearranged lines within a file. Such a change now counts as at least a minimum but non zero change. * The "--dirstat" option of "diff" family of commands used to use the pathname in the original, instead of the pathname in the result, when renames are involved. * "git pack-object" did not take core.bigfilethreashold into account (unlike fast-import); now it does. * "git reflog" ignored options like "--format=.." on the command line. * "git stash apply" used to refuse to work if there was any change in the working tree, even when the change did not overlap with the change the stash recorded. * "git stash apply @{9}" was not diagnosed as an error, even when you did not have that many stash entries. * An error message from "git send-email" to diagnose a broken SMTP connection configuration lacked a space between "hello=" and "port=". And other minor fixes and documentation updates. Git v1.7.5 Release Notes Updates since v1.7.4 * Various MinGW portability fixes. * Various git-p4 enhancements (in contrib). * Various vcs-svn, git-svn and gitk enhancements and fixes. * Various git-gui updates (0.14.0). * Update to more modern HP-UX port. * The codebase is getting prepared for i18n/l10n; no translated strings nor translation mechanism in the code yet, but the strings are being marked for l10n. * The bash completion script can now complete symmetric difference for "git diff" command, e.g. "git diff ..
Re: Problem compiling with SSE intrinsics and -O3
Hi Phil, Please post the output of gcc -v. In fact, I guess it has little to do with Cygwin, as it looks very much like a gcc bug, perhaps fixed in a later version of gcc. Showing that this is a Cygwin bug would need a check that the same does not happen on the same version of gcc on Linux, say. Best, Dmitrii On 14 May 2011 00:15, Morris, Philip wrote: > (third try, wow you guys really don't want to receive emails !) > > Dear Sir/Madam > > I have come across a problem when trying to compile a simple program using > Cygwin > > I just did a fresh install of Cygwin from the net on W7 32bit PC and included > make/g++ to build my software (which builds fine on other native linux > machines) > > When i try to compile the attached file i get this error > > $ gcc -msse2 -c -O3 test.c > test.c: In function `vclrx': > test.c:43: internal compiler error: in output_constant_pool, at varasm.c:3190 > Please submit a full bug report, > with preprocessed source if appropriate. > See http://cygwin.com/problems.html> for instructions. > > Without the -O3 option all is well > > Help appreciated. > > Thanks > > Phil. > -- 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