src/winsup/cygserver ChangeLog cygserver-config
CVSROOT:/cvs/src Module name:src Changes by: cori...@sourceware.org 2014-04-16 08:44:58 Modified files: winsup/cygserver: ChangeLog cygserver-config Log message: * cygserver-config: Use numeric id 18 instead of system in chown. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygserver/ChangeLog.diff?cvsroot=srcr1=1.99r2=1.100 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygserver/cygserver-config.diff?cvsroot=srcr1=1.3r2=1.4
src/winsup/cygwin ChangeLog net.cc
CVSROOT:/cvs/src Module name:src Changes by: cori...@sourceware.org 2014-04-16 08:58:20 Modified files: winsup/cygwin : ChangeLog net.cc Log message: * net.cc (cygwin_setsockopt): Ignore IPV6_TCLASS the same way as IP_TOS. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/ChangeLog.diff?cvsroot=srcr1=1.6392r2=1.6393 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/net.cc.diff?cvsroot=srcr1=1.311r2=1.312
src/winsup/cygwin/release 1.7.30
CVSROOT:/cvs/src Module name:src Changes by: cori...@sourceware.org 2014-04-16 09:04:25 Modified files: winsup/cygwin/release: 1.7.30 Log message: Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/release/1.7.30.diff?cvsroot=srcr1=1.1r2=1.2
src/winsup/cygserver ChangeLog pwdgrp.cc
CVSROOT:/cvs/src Module name:src Changes by: cori...@sourceware.org 2014-04-16 09:26:41 Modified files: winsup/cygserver: ChangeLog pwdgrp.cc Log message: * pwdgrp.cc (client_request_pwdgrp::pwd_serve): Add 1 to the message length to account for the trailing NUL. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygserver/ChangeLog.diff?cvsroot=srcr1=1.100r2=1.101 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygserver/pwdgrp.cc.diff?cvsroot=srcr1=1.1r2=1.2
Re: Re: libtool: link: object name conflicts in archive
Side note, the GNU equivalent of MS lib.exe is ar. (ld corresponds to MS link.exe). Regarding the issue, it is a bad sign that the archives are named libmbmath.lib, libmbutil.lib etc. For a Cygwin build, you want them named libmbmath.a. The .lib suffix is a clear indicator of a problem earlier in the build, just like Corinna said. Is the Cygwin binutils package installed properly? I imagine something like this could happen if the binutils install is broken and the Microsoft tools are on $PATH (but I haven't tested that). I tried it now with $ echo $PATH /usr/local/bin:/usr/bin:/usr/lib/lapack and got lib: command not found /bin/sh ../../libtool --tag=F77 --mode=link gfortran -o liby12.la y12mae.lo y12maf.lo y12mbe.lo y12mbf.lo y12mce.lo y12mcf.lo y12mde.lo y12mdf.lo y12mfe.lo y12mge.lo y12mhe.lo -L/usr/lib/gcc/x86_64-pc-cygwin/4.8.2 -L/usr/lib/gcc/x86_64-pc-cygwin/4.8.2/../../../../lib -L/lib/../lib -L/usr/lib/../lib -L/usr/lib/gcc/x86_64-pc-cygwin/4.8.2/../../.. -lgfortran -lquadmath -lm -lcygwin -ladvapi32 -lshell32 -luser32 -lkernel32 -lltdl -L/usr/lib/gcc/x86_64-pc-cygwin/4.8.2 -L/usr/lib/gcc/x86_64-pc-cygwin/4.8.2/../../../../lib -L/lib/../lib -L/usr/lib/../lib -L/usr/lib/gcc/x86_64-pc-cygwin/4.8.2/../../.. -lgfortran -lquadmath -lm -lcygwin -ladvapi32 -lshell32 -luser32 -lkernel32 -L/usr/lib/gcc/x86_64-pc-cygwin/4.8.2 -L/usr/lib/gcc/x86_64-pc-cygwin/4.8.2/../../../../lib -L/lib/../lib -L/usr/lib/../lib -L/usr/lib/gcc/x86_64-pc-cygwin/4.8.2/../../.. -lgfortran -lquadmath -lm -lcygwin -ladvapi32 -lshell32 -luser32 -lkernel32 -lltdl libtool: link: lib -OUT:.libs/liby12.lib .libs/y12mae.o .libs/y12maf.o .libs/y12mbe.o .libs/y12mbf.o .libs/y12mce.o .libs/y12mcf.o .libs/y12mde.o .libs/y12mdf.o .libs/y12mfe.o .libs/y12mge.o .libs/y12mhe.o ../../libtool: line 1117: lib: command not found -- 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: mingw64-*-binutils-2.24.0.3.85cf705-1 (x86/x86_64)
Version 2.24.0.3.85cf705-1 of mingw64-*-binutils have been uploaded. This removes the previously included default-manifest.o file support. It is now in its own package. Support for automatically linking it is being moved into GCC instead. *** 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@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. signature.asc Description: OpenPGP digital signature
Re: core-dump, cygwin64-only in locate in 4.5.11.1
On Apr 15 18:22, Linda Walsh wrote: Corinna Vinschen wrote: On Apr 14 14:55, Linda Walsh wrote: I updated 77 cygwin pkgs Mar 19, and since have had problems running 'locate' to completion... it dumps core at what appears to be the end of showing files within 18K of the end of a 22M file. I can reproduce it and I *think* I found the problem in the source. Alas, what we need is a new findutils package. Eric, any chance for an update any time soon? Corinna --- Thanks for checking it out! What is wrong w/it? See my mail from October 2013: http://cygwin.com/ml/cygwin/2013-10/msg00405.html Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpaI8qf2zQEo.pgp Description: PGP signature
Re: Re: libtool: link: object name conflicts in archive
On Apr 16 07:21, Gisela Haschmich wrote: Side note, the GNU equivalent of MS lib.exe is ar. (ld corresponds to MS link.exe). Regarding the issue, it is a bad sign that the archives are named libmbmath.lib, libmbutil.lib etc. For a Cygwin build, you want them named libmbmath.a. The .lib suffix is a clear indicator of a problem earlier in the build, just like Corinna said. Is the Cygwin binutils package installed properly? I imagine something like this could happen if the binutils install is broken and the Microsoft tools are on $PATH (but I haven't tested that). I tried it now with $ echo $PATH /usr/local/bin:/usr/bin:/usr/lib/lapack and got lib: command not found /bin/sh ../../libtool --tag=F77 --mode=link gfortran -o liby12.la y12mae.lo y12maf.lo y12mbe.lo y12mbf.lo y12mce.lo y12mcf.lo y12mde.lo y12mdf.lo y12mfe.lo y12mge.lo y12mhe.lo -L/usr/lib/gcc/x86_64-pc-cygwin/4.8.2 -L/usr/lib/gcc/x86_64-pc-cygwin/4.8.2/../../../../lib -L/lib/../lib -L/usr/lib/../lib -L/usr/lib/gcc/x86_64-pc-cygwin/4.8.2/../../.. -lgfortran -lquadmath -lm -lcygwin -ladvapi32 -lshell32 -luser32 -lkernel32 -lltdl -L/usr/lib/gcc/x86_64-pc-cygwin/4.8.2 -L/usr/lib/gcc/x86_64-pc-cygwin/4.8.2/../../../../lib -L/lib/../lib -L/usr/lib/../lib -L/usr/lib/gcc/x86_64-pc-cygwin/4.8.2/../../.. -lgfortran -lquadmath -lm -lcygwin -ladvapi32 -lshell32 -luser32 -lkernel32 -L/usr/lib/gcc/x86_64-pc-cygwin/4.8.2 -L/usr/lib/gcc/x86_64-pc-cygwin/4.8.2/../../../../lib -L/lib/../lib -L/usr/lib/../lib -L/usr/lib/gcc/x86_64-pc-cygwin/4.8.2/../../.. -lgfortran -lquadmath -lm -lcygwin -ladvapi32 -lshell32 -luser32 -lkernel32 -lltdl libtool: link: lib -OUT:.libs/liby12.lib .libs/y12mae.o .libs/y12maf.o .libs/y12mbe.o .libs/y12mbf.o .libs/y12mce.o .libs/y12mcf.o .libs/y12mde.o .libs/y12mdf.o .libs/y12mfe.o .libs/y12mge.o .libs/y12mhe.o ../../libtool: line 1117: lib: command not found This is *so* wrong. That's very likely a problem in the configury then, and you should try to find out how configure gets the idea to use a tool called lib. How did you run configure? This might be a result of using wrong arguments. Also, the upstream devs might have an idea why the build process tries to use MS tools when building for Cygwin. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpdoh87HybEm.pgp Description: PGP signature
Re: Still testing needed: New passwd/group AD/SAM integration
On Apr 15 14:14, Ken Brown wrote: I've come across a glitch involving sshd and cygserver. I normally have both running, but I've discovered that I have to start sshd before I start cygserver, or else I have problems (can't ssh from a non-administrator account to an administrator account). Here are the details on 64 bit Cygwin; I haven't tested 32 bit: I've installed the full 2014-04-12 snapshot and removed /etc/passwd and /etc/group. I have an ordinary user kbrown and an administrator user kbrown-admin. I now do the following: 1. Start sshd. 2. Start cygserver. 3. Start a Cygwin Terminal as user kbrown. 4. ssh into the kbrown-admin account (with publickey authentication used by default). $ ssh kbrown-admin@localhost Enter passphrase for key '/home/kbrown/.ssh/id_rsa': setsockopt IPV6_TCLASS 16: Protocol not available: Last login: Tue Apr 15 13:57:12 2014 from fe80::9956:cbba:6928:151c%11 Everything is fine. Now I close the Cygwin Terminal, stop both services, and restart them in the other order (cygserver first, then sshd). Repeating steps 3 and 4, I can't login: $ ssh kbrown-admin@localhost kbrown-admin@localhost's password: Permission denied, please try again. kbrown-admin@localhost's password: Notice that (a) I didn't get a prompt for the passphrase for my ssh key, and (b) my password wasn't accepted. Thanks for the report, Ken. I'll have a look. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpZsQxlSC8e1.pgp Description: PGP signature
Re: [ANNOUNCEMENT] Updated: mingw64-*-binutils-2.24.0.3.85cf705-1 (x86/x86_64)
JonY wrote: This removes the previously included default-manifest.o file support. It This release fixes the issue I flagged here http://cygwin.com/ml/cygwin/2014-04/msg00016.html at least from Mingw64 side (Cygwin Windows native applications still suffer the issue). Thanks, Angelo. -- 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: libtool: link: object name conflicts in archive
On 2014-04-16 09:21, Gisela Haschmich wrote: Side note, the GNU equivalent of MS lib.exe is ar. (ld corresponds to MS link.exe). Regarding the issue, it is a bad sign that the archives are named libmbmath.lib, libmbutil.lib etc. For a Cygwin build, you want them named libmbmath.a. The .lib suffix is a clear indicator of a problem earlier in the build, just like Corinna said. Is the Cygwin binutils package installed properly? I imagine something like this could happen if the binutils install is broken and the Microsoft tools are on $PATH (but I haven't tested that). I tried it now with $ echo $PATH /usr/local/bin:/usr/bin:/usr/lib/lapack and got lib: command not found /bin/sh ../../libtool --tag=F77 --mode=link gfortran -o liby12.la y12mae.lo y12maf.lo y12mbe.lo y12mbf.lo y12mce.lo y12mcf.lo y12mde.lo y12mdf.lo y12mfe.lo y12mge.lo y12mhe.lo -L/usr/lib/gcc/x86_64-pc-cygwin/4.8.2 -L/usr/lib/gcc/x86_64-pc-cygwin/4.8.2/../../../../lib -L/lib/../lib -L/usr/lib/../lib -L/usr/lib/gcc/x86_64-pc-cygwin/4.8.2/../../.. -lgfortran -lquadmath -lm -lcygwin -ladvapi32 -lshell32 -luser32 -lkernel32 -lltdl -L/usr/lib/gcc/x86_64-pc-cygwin/4.8.2 -L/usr/lib/gcc/x86_64-pc-cygwin/4.8.2/../../../../lib -L/lib/../lib -L/usr/lib/../lib -L/usr/lib/gcc/x86_64-pc-cygwin/4.8.2/../../.. -lgfortran -lquadmath -lm -lcygwin -ladvapi32 -lshell32 -luser32 -lkernel32 -L/usr/lib/gcc/x86_64-pc-cygwin/4.8.2 -L/usr/lib/gcc/x86_64-pc-cygwin/4.8.2/../../../../lib -L/lib/../lib -L/usr/lib/../lib -L/usr/lib/gcc/x86_64-pc-cygwin/4.8.2/../../.. -lgfortran -lquadmath -lm -lcygwin -ladvapi32 -lshell32 -luser32 -lkernel32 -lltdl libtool: link: lib -OUT:.libs/liby12.lib .libs/y12mae.o .libs/y12maf.o .libs/y12mbe.o .libs/y12mbf.o .libs/y12mce.o .libs/y12mcf.o .libs/y12mde.o .libs/y12mdf.o .libs/y12mfe.o .libs/y12mge.o .libs/y12mhe.o ../../libtool: line 1117: lib: command not found Did you really rerun configure with the new $PATH? You also need to kill any configure cache, i.e. if you have one. Cheers, Peter -- 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: Still testing needed: New passwd/group AD/SAM integration
Hi Ken, On Apr 16 10:04, Corinna Vinschen wrote: On Apr 15 14:14, Ken Brown wrote: I've come across a glitch involving sshd and cygserver. I normally have both running, but I've discovered that I have to start sshd before I start cygserver, or else I have problems (can't ssh from a non-administrator account to an administrator account). Here are the details on 64 bit Cygwin; I haven't tested 32 bit: I've installed the full 2014-04-12 snapshot and removed /etc/passwd and /etc/group. I have an ordinary user kbrown and an administrator user kbrown-admin. I now do the following: 1. Start sshd. 2. Start cygserver. 3. Start a Cygwin Terminal as user kbrown. 4. ssh into the kbrown-admin account (with publickey authentication used by default). $ ssh kbrown-admin@localhost Enter passphrase for key '/home/kbrown/.ssh/id_rsa': setsockopt IPV6_TCLASS 16: Protocol not available: Last login: Tue Apr 15 13:57:12 2014 from fe80::9956:cbba:6928:151c%11 Everything is fine. Now I close the Cygwin Terminal, stop both services, and restart them in the other order (cygserver first, then sshd). Repeating steps 3 and 4, I can't login: $ ssh kbrown-admin@localhost kbrown-admin@localhost's password: Permission denied, please try again. kbrown-admin@localhost's password: Notice that (a) I didn't get a prompt for the passphrase for my ssh key, and (b) my password wasn't accepted. Thanks for the report, Ken. I'll have a look. To clarify: This is a non-domain machine, right? And sshd is running under the cyg_server account while cygserver is running under the LocalSystem account? I'm just testing this, only with a domain machine and domain accounts, and I can't reproduce this. I have a bit of a problem to test this on a non-domain machine because my network is set up for domain machines... However, I found that I made a blatant mistake in cygserver. The message length was computed one byte too short, so the trailing \0 in the passwd/group string wasn't transmitted. This *might* be the cause for your problem. I just built a new snapshot. Can you please try if this fixes it for you? Make sure to use the new cygserver! While I was at it, I also added a patch to get rid of the setsockopt IPV6_TCLASS 16: Protocol not available message. I just *love* it if Microsoft defines socket options in their headers, but then simply returns WSAENOPROTOOPT when the appliction dares to use them... Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpw2St5U7Kan.pgp Description: PGP signature
[ANNOUNCEMENT] Updated: wget-1.15-1
A new release of wget, 1.15-1, is available for download, leaving 1.13.4-1 as previous. NEWS: = This is a new upstream release, and also my first time building it for 64-bit cygwin (the existing 64-bit build was provided by others to help bootstrap the environment). This should resolve issues reported here: http://cygwin.com/ml/cygwin/2013-09/msg00161.html http://cygwin.com/ml/cygwin/2014-01/msg00327.html See also the package documentation in /usr/share/doc/wget/. DESCRIPTION: GNU Wget is a file retrieval utility which can use either the HTTP, HTTPS, or FTP protocols. Wget features include the ability to work in the background while you're logged out, recursive retrieval of directories, file name wildcard matching, remote file timestamp storage and comparison, use of Rest with FTP servers and Range with HTTP servers to retrieve files over slow or unstable connections, support for Proxy servers, and configurability. 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 'wget' from the 'Web' category. DOWNLOAD: = Note that downloads from 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 wget package 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. signature.asc Description: OpenPGP digital signature
Re: libtool: link: object name conflicts in archive
In message 20140416080331.gn3...@calimero.vinschen.deyou write: --KC+fneiph5CALyUl Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable ../../libtool: line 1117: lib: command not found This is *so* wrong. That's very likely a problem in the configury then, and you should try to find out how configure gets the idea to use a tool called lib. How did you run configure? This might be a result of using wrong arguments. Also, the upstream devs might have an idea why the build process tries to use MS tools when building for Cygwin. Corinna I have run into a couple of configure scripts that when they see you are running cygwin think that means they should try to build a native Windows version rather than follow the linux-like path to a native Cygwin version.. It's very irritating. -- 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: Trouble with running cygwin dll on Vortex86MX+ CPU
Peter A. Castro doctor at fruitbat.org writes: I've just built a newer version of upx (and ucl, etc) and now I will start archiving setup, x86 x86_64, (again). Need to update my webpage automation to generate an access list, but atleast I'm grabbing and archiving them (again). Not that I want to discourage you from building those yourself, but I should perhaps mention that these packages are current for both Cygwin32 and Cygwin64. Regards, Achim. -- 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: libtool: link: object name conflicts in archive
On Apr 16 07:35, tedno...@bellsouth.net wrote: In message 20140416080331.gn3...@calimero.vinschen.deyou write: --KC+fneiph5CALyUl Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable ../../libtool: line 1117: lib: command not found This is *so* wrong. That's very likely a problem in the configury then, and you should try to find out how configure gets the idea to use a tool called lib. How did you run configure? This might be a result of using wrong arguments. Also, the upstream devs might have an idea why the build process tries to use MS tools when building for Cygwin. Corinna I have run into a couple of configure scripts that when they see you are running cygwin think that means they should try to build a native Windows version rather than follow the linux-like path to a native Cygwin version.. It's very irritating. Indeed. It's not as bad anymore as 10 years ago, but there are still packages out there who don't understand that Cygwin is not just a frontend to build native Windows stuff. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpuemQLn7f6S.pgp Description: PGP signature
[ANNOUNCEMENT] Updated: ssmtp-2.64-7 (test on 32 bit!)
Hi folks, I created new ssmtp packages, version 2.64-7. This is the first ssmtp package for the 64 bit distro. For the 32 bit distro this new package is marked as test version! It would be nice if somebody familiar with ssmtp from the 32 bit distro could give it a try, if possible both, in 32 and 64 bit. This package is basically the same thing as the Debian version 2.64-7, just missing the Debian patch which switches from OpenSSL to GnuTLS. There are also a few patches to the build process to allow building in a separate build dir and a tweak to install the ssmtp-config script, but nothing which would change the functionality. Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developercygwin AT cygwin DOT com Red Hat, Inc. -- 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: Still testing needed: New passwd/group AD/SAM integration
On 4/16/2014 2:35 AM, Corinna Vinschen wrote: Hi Ken, On Apr 16 10:04, Corinna Vinschen wrote: On Apr 15 14:14, Ken Brown wrote: I've come across a glitch involving sshd and cygserver. I normally have both running, but I've discovered that I have to start sshd before I start cygserver, or else I have problems (can't ssh from a non-administrator account to an administrator account). Here are the details on 64 bit Cygwin; I haven't tested 32 bit: I've installed the full 2014-04-12 snapshot and removed /etc/passwd and /etc/group. I have an ordinary user kbrown and an administrator user kbrown-admin. I now do the following: 1. Start sshd. 2. Start cygserver. 3. Start a Cygwin Terminal as user kbrown. 4. ssh into the kbrown-admin account (with publickey authentication used by default). $ ssh kbrown-admin@localhost Enter passphrase for key '/home/kbrown/.ssh/id_rsa': setsockopt IPV6_TCLASS 16: Protocol not available: Last login: Tue Apr 15 13:57:12 2014 from fe80::9956:cbba:6928:151c%11 Everything is fine. Now I close the Cygwin Terminal, stop both services, and restart them in the other order (cygserver first, then sshd). Repeating steps 3 and 4, I can't login: $ ssh kbrown-admin@localhost kbrown-admin@localhost's password: Permission denied, please try again. kbrown-admin@localhost's password: Notice that (a) I didn't get a prompt for the passphrase for my ssh key, and (b) my password wasn't accepted. Thanks for the report, Ken. I'll have a look. To clarify: This is a non-domain machine, right? And sshd is running under the cyg_server account while cygserver is running under the LocalSystem account? Yes to all. I'm just testing this, only with a domain machine and domain accounts, and I can't reproduce this. I have a bit of a problem to test this on a non-domain machine because my network is set up for domain machines... However, I found that I made a blatant mistake in cygserver. The message length was computed one byte too short, so the trailing \0 in the passwd/group string wasn't transmitted. This *might* be the cause for your problem. I just built a new snapshot. Can you please try if this fixes it for you? Make sure to use the new cygserver! Yes, that fixed it. Thanks. While I was at it, I also added a patch to get rid of the setsockopt IPV6_TCLASS 16: Protocol not available message. Good. It's nice to see that anymore. Ken -- 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: Still testing needed: New passwd/group AD/SAM integration
On 4/16/2014 8:28 AM, Ken Brown wrote: On 4/16/2014 2:35 AM, Corinna Vinschen wrote: Hi Ken, On Apr 16 10:04, Corinna Vinschen wrote: On Apr 15 14:14, Ken Brown wrote: I've come across a glitch involving sshd and cygserver. I normally have both running, but I've discovered that I have to start sshd before I start cygserver, or else I have problems (can't ssh from a non-administrator account to an administrator account). Here are the details on 64 bit Cygwin; I haven't tested 32 bit: I've installed the full 2014-04-12 snapshot and removed /etc/passwd and /etc/group. I have an ordinary user kbrown and an administrator user kbrown-admin. I now do the following: 1. Start sshd. 2. Start cygserver. 3. Start a Cygwin Terminal as user kbrown. 4. ssh into the kbrown-admin account (with publickey authentication used by default). $ ssh kbrown-admin@localhost Enter passphrase for key '/home/kbrown/.ssh/id_rsa': setsockopt IPV6_TCLASS 16: Protocol not available: Last login: Tue Apr 15 13:57:12 2014 from fe80::9956:cbba:6928:151c%11 Everything is fine. Now I close the Cygwin Terminal, stop both services, and restart them in the other order (cygserver first, then sshd). Repeating steps 3 and 4, I can't login: $ ssh kbrown-admin@localhost kbrown-admin@localhost's password: Permission denied, please try again. kbrown-admin@localhost's password: Notice that (a) I didn't get a prompt for the passphrase for my ssh key, and (b) my password wasn't accepted. Thanks for the report, Ken. I'll have a look. To clarify: This is a non-domain machine, right? And sshd is running under the cyg_server account while cygserver is running under the LocalSystem account? Yes to all. I'm just testing this, only with a domain machine and domain accounts, and I can't reproduce this. I have a bit of a problem to test this on a non-domain machine because my network is set up for domain machines... However, I found that I made a blatant mistake in cygserver. The message length was computed one byte too short, so the trailing \0 in the passwd/group string wasn't transmitted. This *might* be the cause for your problem. I just built a new snapshot. Can you please try if this fixes it for you? Make sure to use the new cygserver! Yes, that fixed it. Thanks. While I was at it, I also added a patch to get rid of the setsockopt IPV6_TCLASS 16: Protocol not available message. Good. It's nice to see that anymore. ^ not -- 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: Still testing needed: New passwd/group AD/SAM integration
On Apr 16 08:32, Ken Brown wrote: On 4/16/2014 8:28 AM, Ken Brown wrote: On 4/16/2014 2:35 AM, Corinna Vinschen wrote: On Apr 16 10:04, Corinna Vinschen wrote: On Apr 15 14:14, Ken Brown wrote: I've come across a glitch involving sshd and cygserver. [...] Now I close the Cygwin Terminal, stop both services, and restart them in the other order (cygserver first, then sshd). Repeating steps 3 and 4, I can't login: $ ssh kbrown-admin@localhost kbrown-admin@localhost's password: Permission denied, please try again. kbrown-admin@localhost's password: Notice that (a) I didn't get a prompt for the passphrase for my ssh key, and (b) my password wasn't accepted. Thanks for the report, Ken. I'll have a look. To clarify: This is a non-domain machine, right? And sshd is running under the cyg_server account while cygserver is running under the LocalSystem account? Yes to all. I'm just testing this, only with a domain machine and domain accounts, and I can't reproduce this. I have a bit of a problem to test this on a non-domain machine because my network is set up for domain machines... However, I found that I made a blatant mistake in cygserver. The message length was computed one byte too short, so the trailing \0 in the passwd/group string wasn't transmitted. This *might* be the cause for your problem. I just built a new snapshot. Can you please try if this fixes it for you? Make sure to use the new cygserver! Yes, that fixed it. Thanks. While I was at it, I also added a patch to get rid of the setsockopt IPV6_TCLASS 16: Protocol not available message. Good. It's nice to see that anymore. ^ not Thanks for testing! I had hoped that this is the culprit. The difference was obviously something realted to using or not using cygserver... Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgp7lGjLjWl4D.pgp Description: PGP signature
Re: x86_64 Cygwin 1.7.29: possible bug to trace symlink (Win7)
On Apr 16 03:39, 卜勇华 wrote: Hi Corinna, Please don't top-post. Thank you. Below is what I get: RS-I9E3U8R4:[~/tmp/test_symlink]uname -a CYGWIN_NT-6.1 RS-I9E3U8R4 1.7.29(0.272/5/3) 2014-04-07 13:46 x86_64 Cygwin RS-I9E3U8R4:[~/tmp/test_symlink]echo $CYGWIN winsymlinks:nativestrict RS-I9E3U8R4:[~/tmp/test_symlink]echo test test.txt RS-I9E3U8R4:[~/tmp/test_symlink]mkdir dest RS-I9E3U8R4:[~/tmp/test_symlink]cd dest RS-I9E3U8R4:[~/tmp/test_symlink/dest]ln -s ../test.txt test.txt RS-I9E3U8R4:[~/tmp/test_symlink/dest]cd ../ RS-I9E3U8R4:[~/tmp/test_symlink]mkdir src RS-I9E3U8R4:[~/tmp/test_symlink]cd src RS-I9E3U8R4:[~/tmp/test_symlink/src]ln -s ../dest dest RS-I9E3U8R4:[~/tmp/test_symlink/src]cd ../ RS-I9E3U8R4:[~/tmp/test_symlink]cat src/dest/test.txt cat: src/dest/test.txt: No such file or directory I can reproduce it now. I made a mistake when creating the symlinks the first time, which is, I created them with tcsh. Tcsh tends to change relative paths using .. components to absolute paths on the command line. Using plain relative paths, I now see what's going on. But it'sa tricky problem. I don't know how to fix it yet. I'll have to think about it, so please be patient. Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpkEloieAzvW.pgp Description: PGP signature
Re: Trouble with running cygwin dll on Vortex86MX+ CPU
On Wed, 16 Apr 2014, Achim Gratz wrote: Peter A. Castro writes: I've just built a newer version of upx (and ucl, etc) and now I will start archiving setup, x86 x86_64, (again). Need to update my webpage automation to generate an access list, but atleast I'm grabbing and archiving them (again). Greetings, Achim, Not that I want to discourage you from building those yourself, but I should perhaps mention that these packages are current for both Cygwin32 and Cygwin64. Ah. You are making the assumption I'm running my little project (Cygwin Time Machine) on Windows? No. This is run on a Linux server I use (heresy, I know :-), mostly using automated scripts and cron jobs. As entertaining an idea of running Cygwin's upx.exe under Wine, just to unpack setup, might seem, I felt it was a bit of overkill. :-) So, I needed to build upx natively in order to unpack setup. When I tried this years ago, it didn't compile and I didn't have time to persue it. But the recent versions of upx (and ucl) both compile run just fine. Regards, Achim. -- --= Peter A. Castro Email: doctor at fruitbat dot org / Peter dot Castro at oracle dot com Cats are just autistic Dogs -- Dr. Tony Attwood -- 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: Trouble with running cygwin dll on Vortex86MX+ CPU
Peter A. Castro writes: Ah. You are making the assumption I'm running my little project (Cygwin Time Machine) on Windows? No. This is run on a Linux server I use (heresy, I know :-), mostly using automated scripts and cron jobs. I just wanted to avoid folks asking for those new versions on Cygwin when they are already here. I certainly didn't want to suggest you do or should run your server on Windows. :-) When I tried this years ago, it didn't compile and I didn't have time to persue it. But the recent versions of upx (and ucl) both compile run just fine. Yes, it just builds out-of-the-box now. All software should do that! Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptation for Waldorf microQ V2.22R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada -- 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: [ANNOUNCEMENT] Updated: ssmtp-2.64-7 (test on 32 bit!)
Greetings, Corinna Vinschen! I created new ssmtp packages, version 2.64-7. This is the first ssmtp package for the 64 bit distro. For the 32 bit distro this new package is marked as test version! It would be nice if somebody familiar with ssmtp from the 32 bit distro could give it a try, if possible both, in 32 and 64 bit. I can't test it under 64 bit yet, but I'll give a try on 32bit and see if my scripts go well with it. In a day, as I'm away from desktop right now. This package is basically the same thing as the Debian version 2.64-7, just missing the Debian patch which switches from OpenSSL to GnuTLS. There are also a few patches to the build process to allow building in a separate build dir and a tweak to install the ssmtp-config script, but nothing which would change the functionality. Thanks for taking care of it. This is one of the essential packages for me to complete the switch to 64-bit. -- WBR, Andrey Repin (anrdae...@yandex.ru) 16.04.2014, 20:19 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
Wow, just hit RCS bug
I just hit the worst Cygwin bug I've encountered, the RCS bug which silently corrupts text files 256K. That's the last thing I expect from a version control system! After some moments of panic, I was able to retrieve a good copy from backups, but have lost my revision history. Anyway, I immediately did a list search and found this is a known bug. Shouldn't this package be pulled? Just for the record, the suggested env var fix RCS_MEM_LIMIT=0 to force stdio does not work for me, but the RCS_MEM_LIMIT=10240 to allow 10megs of diffs does.. -- 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: Wow, just hit RCS bug
tedno...@bellsouth.net writes: Just for the record, the suggested env var fix RCS_MEM_LIMIT=0 to force stdio does not work for me, but the That was never suggested as a fix, but to show that the problem occurs with files much less than 256kiB size when forcing the code path through stdio (which is what the 0 setting does). The RCS test suite passes on Cygwin since it never actively tests this code path. http://thread.gmane.org/gmane.os.cygwin/142346 RCS_MEM_LIMIT=10240 to allow 10megs of diffs does.. Which will fail once you happen upon a diff that gets that large. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Samples for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra -- 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: Wow, just hit RCS bug
In message 87bnw12nuu.fsf@Rainer.invalidyou write: tedno...@bellsouth.net writes: Just for the record, the suggested env var fix RCS_MEM_LIMIT=0 to force stdio does not work for me, but the That was never suggested as a fix, but to show that the problem occurs with files much less than 256kiB size when forcing the code path through stdio (which is what the 0 setting does). The RCS test suite passes on Cygwin since it never actively tests this code path. http://thread.gmane.org/gmane.os.cygwin/142346 RCS_MEM_LIMIT=10240 to allow 10megs of diffs does.. Which will fail once you happen upon a diff that gets that large. Ah, OK -- I was just looking for a fix or workaround and didn't read what the =0 was supposed to do closely enough. I can't see ever getting up to 10M of diffs, but still I consider it an existential level bug for a version control system and think the package should be removed. It's almost as bad as if ls -l foo unlinked foo. -- 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: [ANNOUNCEMENT] Updated: mingw64-*-binutils-2.24.0.3.85cf705-1 (x86/x86_64)
On 2014-04-16 10:20, Angelo Graziosi wrote: JonY wrote: This removes the previously included default-manifest.o file support. It This release fixes the issue I flagged here http://cygwin.com/ml/cygwin/2014-04/msg00016.html at least from Mingw64 side (Cygwin Windows native applications still suffer the issue). Me too, see http://cygwin.com/ml/cygwin/2014-04/msg3.html Denis Excoffier. -- 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: Wow, just hit RCS bug
RCS does a great job for smaller projects when I don't need the overhead of any of the popular larger systems. It has saved me many times when I'm working on a short document or a set of scripts on my desktop machine. I'd miss it if it were removed simply due to the lack of handling 10Meg of diffs or similar. Wonder if this bug could be fixed some way? On Wed, Apr 16, 2014 at 11:05 AM, tedno...@bellsouth.net wrote: In message 87bnw12nuu.fsf@Rainer.invalidyou write: tedno...@bellsouth.net writes: Just for the record, the suggested env var fix RCS_MEM_LIMIT=0 to force stdio does not work for me, but the That was never suggested as a fix, but to show that the problem occurs with files much less than 256kiB size when forcing the code path through stdio (which is what the 0 setting does). The RCS test suite passes on Cygwin since it never actively tests this code path. http://thread.gmane.org/gmane.os.cygwin/142346 RCS_MEM_LIMIT=10240 to allow 10megs of diffs does.. Which will fail once you happen upon a diff that gets that large. Ah, OK -- I was just looking for a fix or workaround and didn't read what the =0 was supposed to do closely enough. I can't see ever getting up to 10M of diffs, but still I consider it an existential level bug for a version control system and think the package should be removed. It's almost as bad as if ls -l foo unlinked foo. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Wow, just hit RCS bug
In message CAFWoy7HdXgKXnPKNTsEUo38ttbj=fcr4krrolnsyxdvfuof...@mail.gmail.com you write: RCS does a great job for smaller projects when I don't need the overhead of any of the popular larger systems. It has saved me many times when I'm working on a short document or a set of scripts on my desktop machine. I'd miss it if it were removed simply due to the lack of handling 10Meg of diffs or similar. Wonder if this bug could be fixed some way? Well, I agree, or I wouldn't be using RCS in the first place. But even though I'm the only coder on the project, I've managed to work the main library file up to 256+ K, and I suspect it's not at all rare for RCS projects to have files in that range. 256K is the key number, not 10M. -- 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: sharutils-4.14-1
A new release of sharutils, 4.14-1, is available, leaving 4.10-2 as previous on 32-bit cygwin. It is also my first 64-bit build; 4.13.5-1 on 64-bit cygwin was not built by me, but provided while bootstrapping the release. NEWS: = This is a new upstream version. Using shar on text mounts continues to have the possibility that line endings on text files might not be handled the way you want, but if it was truly a text file, that should not matter to you; the heuristic that shar uses to decide between text and binary files is whether it contains non-printing characters. It is safer to use shar/unshar on binary mounts (remembering that unshar is inherently unsafe). uuencode and uudecode, on the other hand, work reliably regardless of the underlying mount point. See also the package documentation found in /usr/share/doc/sharutils/. DESCRIPTION: The sharutils package contains the GNU shar utilities, a set of tools for encoding and decoding packages of files (in binary or text format) in a special plain text format called shell archives (shar). This format can be sent through e-mail (which can be problematic for regular binary files). The shar utility supports a wide range of capabilities (compressing, uuencoding, splitting long files for multi-part mailings, providing checksums), which make it very flexible at creating shar files. After the files have been sent, the unshar tool scans mail messages looking for shar files. Unshar automatically strips off mail headers and introductory text and then unpacks the shar files. Note that unshar is inherently unsafe by design, because it executes arbitrary shell scripts; therefore the creation of shar archives should be limited to situations where the receiver trusts the sender. However, uuencode and uudecode are useful in their own right, and are safe to use. 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 'sharutils' from the 'Archive' category. DOWNLOAD: = Note that downloads from 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 sharutils package 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. signature.asc Description: OpenPGP digital signature
Re: Wow, just hit RCS bug (attn: Dr Volker Zell)
On 4/16/2014 10:09, tedno...@bellsouth.net wrote: I just hit the worst Cygwin bug I've encountered, the RCS bug which silently corrupts text files 256K. It's not a bug, it's a buffer size choice made with the rcs 5.8 release, which affects Cygwin for reasons unknown. GNU rcs 5.9.2 changed this functionality again in a way which may fix the problem: 2013-10-20 Thien-Thi Nguyen x...@xxx.org Relax RCS_MEM_LIMIT default; fall back if unspecified. * doc/rcs.texi (Environment): Update ‘RCS_MEM_LIMIT’ description; add a willful ignorance hint and speculation on its removal. I built 5.9.2 under Cygwin with default build options, and it successfully runs a test script that fails under the current Cygwin rcs, which was posted by Don Hatch when this problem came up here 6 months ago: http://cygwin.com/ml/cygwin/2013-10/msg00086.html Dr Volker Zell, the maintainer of the Cygwin rcs package, did not respond to that thread. A search shows only two emails from him to this list since that time. As far as I know, no one has investigated the reason why this change causes a problem on Cygwin, but it would seem that replacing 5.8.2 with 5.9.2 would help. -- 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
cygcc-1.dll: which package?
Hello, I am trying to provide a binary that will require Cygwin to run. The trick is, when I compile it on one system and run it on another, certain dependencies may or may not be present. Although I thought I did a thorough job on my test system, I'm missing cygcc-1.dll. When I try to run my executable on a different system than the one it was compiled on, I get the error: /cygdrive/c/Users/brand_000/Downloads/WindowsCygwin64_falcon_minDisj_1_0.exe: error while loading shared libraries: cyggc-1.dll: cannot open shared object file: No such file or directory Both systems are using Cygwin64. At first I thought this was probably libgcc, but it seems to not be the case since I explicitly checked it, updated it, and got the same result. More generally, any advice on dealing with such problems would be appreciated. Best, Brandon Barker brandon.bar...@gmail.com -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: cygcc-1.dll: which package?
On 04/16/2014 09:53 PM, Brandon Barker wrote: Hello, I am trying to provide a binary that will require Cygwin to run. The trick is, when I compile it on one system and run it on another, certain dependencies may or may not be present. Although I thought I did a thorough job on my test system, I'm missing cygcc-1.dll. When I try to run my executable on a different system than the one it was compiled on, I get the error: /cygdrive/c/Users/brand_000/Downloads/WindowsCygwin64_falcon_minDisj_1_0.exe: error while loading shared libraries: cyggc-1.dll: cannot open shared object file: No such file or directory Both systems are using Cygwin64. At first I thought this was probably libgcc, but it seems to not be the case since I explicitly checked it, updated it, and got the same result. When you're wondering what package contains something you're looking for, consult the package search engine - http://cygwin.com/packages/. It will tell you if there are any packages in the distro that have the file you're searching for. In your case. see: http://cygwin.com/cgi-bin2/package-grep.cgi?grep=cyggc-1.dllarch=x86_64 And remember, if you're actually distributing a binary, the GPL comes into play. You have to provide sources for your app and for the parts of Cygwin you're distributing. -- 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
problem reproducing perl-Error build
I'm listed as maintainer of the perl-Error module, and am trying to upgrade to the 0.17022 release. However, when I try to rebuild the 0.17019 release that was done on my behalf for 64-bit cygwin, it fails: $ cygport perl-Error.cygport fetch prep make Preparing perl-Error-0.17019-1 Unpacking source Error-0.17019.tar.gz Preparing working source directory Compiling perl-Error-0.17019-1 cygwin warning: MS-DOS style path detected: \Users\Administrator Preferred POSIX equivalent is: /cygdrive/c/Users/Administrator 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 Created MYMETA.yml and MYMETA.json Creating new 'Build' script for 'Error' version '0.17019' Module::Build version 0.39 required--this is only version 0.38 at Build line 41. *** ERROR: Module::Build build failed This raises several questions: 1. What is going wrong in cygport and/or perl's Module::Build that is triggering the nodosfile warning? 2. How did someone else (Yaakov?) build the 64-bit package? Why is it not reproducible using self-hosted stock cygwin? 3. Any chance the perl Module::Build shipped in cygwin perl can be bumped to a newer version? -- Eric Blake eblake redhat com+1-919-301-3266 Libvirt virtualization library http://libvirt.org signature.asc Description: OpenPGP digital signature
Updated: mingw64-*-binutils-2.24.0.3.85cf705-1 (x86/x86_64)
Version 2.24.0.3.85cf705-1 of mingw64-*-binutils have been uploaded. This removes the previously included default-manifest.o file support. It is now in its own package. Support for automatically linking it is being moved into GCC instead. *** 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@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. signature.asc Description: OpenPGP digital signature
Updated: wget-1.15-1
A new release of wget, 1.15-1, is available for download, leaving 1.13.4-1 as previous. NEWS: = This is a new upstream release, and also my first time building it for 64-bit cygwin (the existing 64-bit build was provided by others to help bootstrap the environment). This should resolve issues reported here: http://cygwin.com/ml/cygwin/2013-09/msg00161.html http://cygwin.com/ml/cygwin/2014-01/msg00327.html See also the package documentation in /usr/share/doc/wget/. DESCRIPTION: GNU Wget is a file retrieval utility which can use either the HTTP, HTTPS, or FTP protocols. Wget features include the ability to work in the background while you're logged out, recursive retrieval of directories, file name wildcard matching, remote file timestamp storage and comparison, use of Rest with FTP servers and Range with HTTP servers to retrieve files over slow or unstable connections, support for Proxy servers, and configurability. 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 'wget' from the 'Web' category. DOWNLOAD: = Note that downloads from 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 wget package 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. signature.asc Description: OpenPGP digital signature
Updated: ssmtp-2.64-7 (test on 32 bit!)
Hi folks, I created new ssmtp packages, version 2.64-7. This is the first ssmtp package for the 64 bit distro. For the 32 bit distro this new package is marked as test version! It would be nice if somebody familiar with ssmtp from the 32 bit distro could give it a try, if possible both, in 32 and 64 bit. This package is basically the same thing as the Debian version 2.64-7, just missing the Debian patch which switches from OpenSSL to GnuTLS. There are also a few patches to the build process to allow building in a separate build dir and a tweak to install the ssmtp-config script, but nothing which would change the functionality. Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developercygwin AT cygwin DOT com Red Hat, Inc.
Updated: sharutils-4.14-1
A new release of sharutils, 4.14-1, is available, leaving 4.10-2 as previous on 32-bit cygwin. It is also my first 64-bit build; 4.13.5-1 on 64-bit cygwin was not built by me, but provided while bootstrapping the release. NEWS: = This is a new upstream version. Using shar on text mounts continues to have the possibility that line endings on text files might not be handled the way you want, but if it was truly a text file, that should not matter to you; the heuristic that shar uses to decide between text and binary files is whether it contains non-printing characters. It is safer to use shar/unshar on binary mounts (remembering that unshar is inherently unsafe). uuencode and uudecode, on the other hand, work reliably regardless of the underlying mount point. See also the package documentation found in /usr/share/doc/sharutils/. DESCRIPTION: The sharutils package contains the GNU shar utilities, a set of tools for encoding and decoding packages of files (in binary or text format) in a special plain text format called shell archives (shar). This format can be sent through e-mail (which can be problematic for regular binary files). The shar utility supports a wide range of capabilities (compressing, uuencoding, splitting long files for multi-part mailings, providing checksums), which make it very flexible at creating shar files. After the files have been sent, the unshar tool scans mail messages looking for shar files. Unshar automatically strips off mail headers and introductory text and then unpacks the shar files. Note that unshar is inherently unsafe by design, because it executes arbitrary shell scripts; therefore the creation of shar archives should be limited to situations where the receiver trusts the sender. However, uuencode and uudecode are useful in their own right, and are safe to use. 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 'sharutils' from the 'Archive' category. DOWNLOAD: = Note that downloads from 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 sharutils package 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. signature.asc Description: OpenPGP digital signature
