Re: [RFC] 1.7 Packaging: Toolchain
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dave Korn wrote: | I've got libgcc shared and working fine and correctly, either with a | separate static libgcc_eh, or with it shared, although that's only an option | if you also have shared libstdc++. | | Getting libstdc++ to work shared is being tricky; for some reason | libsupc++ is only built static, which means libtool links it into libstdc++ | only to resolve imports, not as objects that need to be exported. Removing | the --disable-shared libtool tag from libsupc++'s build configuration gets | me what appears to be a complete libstdc++, but it fails in early startup, | probably down to the relocs-in-.rodata issue; and that's where I've got to. | I'm not sure whether to just try and go for a shared-libstdc-static-libsupc | combo, or to try and figure out what needs to be fixed to prevent the relocs | problem - if indeed that's what it is. This thread seems to explain the logic behind libsupc++: http://gcc.gnu.org/ml/gcc/2001-06/msg01886.html I'd say it makes the most sense to stick with the upstream shared-libstdc-static-libsupc setup. I gather that this this isn't creating a complete libstdc++ though, but I don't see why. libsupc++ is being linked in via a convenience lib, which means that it should be linking the .a with -Wl,--whole-archive, and exporting any symbols therein. Which method is being used for symbol exports, and what exactly is missing? BTW, what about libg2c/libobjc/libgcj? | That's my plan. May I dare ask for a timeframe? | Famous last words. Yes, that's the scheme we decided on some time ago, | but given how long it's already taking to get vanilla gcc4 working, I was | just going to leave that as it stands for now. I'm not sure I follow. Is -mno-cygwin part of the vanilla gcc now? Yaakov -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkiRVpYACgkQpiWmPGlmQSMUDwCgjpDBQYmtpanPQXAjrSccBAJM fIoAoK8gul9UBxBM0kAxU0hW09NGTiwS =zdr0 -END PGP SIGNATURE-
Re: New Cygwin 1.7.0-18 in release-2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Corinna Vinschen wrote: | - Creating filenames with special DOS characters '', '*', ':', '', | '', '|' is supported. | | - Creating files with special DOS device filename components (aux, | nul, prn) is supported. | | - File name are case sensitive if the OS and the underlying file system | supports it. Works on NTFS and NFS. Does not work on FAT and Samba | shares. Requires to change a registry key (see the user's guide). | Can be switched off on a per-mount base. But does/will setup.exe know what to do with a package containing such filenames? Yaakov -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkiRYjsACgkQpiWmPGlmQSMcnwCg3q2JpXIOpDUhFBF9cs4vOfwN U88Ani5WrUfBySOpEM76hzNuEqnUdQLo =/Sml -END PGP SIGNATURE-
Re: New Cygwin 1.7.0-18 in release-2
On Jul 31 01:56, Yaakov (Cygwin Ports) wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Corinna Vinschen wrote: | - Creating filenames with special DOS characters '', '*', ':', '', | '', '|' is supported. | | - Creating files with special DOS device filename components (aux, | nul, prn) is supported. | | - File name are case sensitive if the OS and the underlying file system | supports it. Works on NTFS and NFS. Does not work on FAT and Samba | shares. Requires to change a registry key (see the user's guide). | Can be switched off on a per-mount base. But does/will setup.exe know what to do with a package containing such filenames? setup is a Win32 application. It won't know about this. Thou shalt not create packages which rely on case-sensitivity as part of the net distro. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: New Cygwin 1.7.0-18 in release-2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Corinna Vinschen wrote: | setup is a Win32 application. It won't know about this. Thou shalt | not create packages which rely on case-sensitivity as part of the | net distro. That's what I thought. So while managed mounts will no longer be needed for building, something still needs to be done for the packaging stage. So far my idea is to adapt cygport's make_managed_mount[1], but remove the mount/umount commands. I should also add a postinstall check to make sure illegal filenames aren't being installed without special handling. [1] http://cygwin-ports.cvs.sourceforge.net/*checkout*/cygwin-ports/cygport/bin/make_managed_mount Any other ideas? Yaakov -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkiRd50ACgkQpiWmPGlmQSPb/QCgxaNwHBXFaHGxYx4VsvIpUDqy mMIAn09jTDYpN3CiTnEoL13Rf4yKOw7n =Bpi4 -END PGP SIGNATURE-
Re: New Cygwin 1.7.0-18 in release-2
On Jul 31 03:28, Yaakov (Cygwin Ports) wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Corinna Vinschen wrote: | setup is a Win32 application. It won't know about this. Thou shalt | not create packages which rely on case-sensitivity as part of the | net distro. That's what I thought. So while managed mounts will no longer be needed for building, something still needs to be done for the packaging stage. So far my idea is to adapt cygport's make_managed_mount[1], but remove the mount/umount commands. I should also add a postinstall check to make sure illegal filenames aren't being installed without special handling. Illegal? The only illegal chars are slash and backslash, even on case-insensitive mounts. Does it really occur often that you have two filenames in the same dir only differing by case? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: New Cygwin 1.7.0-18 in release-2
Corinna Vinschen wrote: Illegal? The only illegal chars are slash and backslash, even on case-insensitive mounts. Does it really occur often that you have two filenames in the same dir only differing by case? I'd imagine aux and prn are still illegal, right? The numbers are fewer, these days, but there are still source packages out there that have 'aux/' subdirectories. -- Chuck
Re: New Cygwin 1.7.0-18 in release-2
On Jul 31 08:59, Charles Wilson wrote: Corinna Vinschen wrote: Illegal? The only illegal chars are slash and backslash, even on case-insensitive mounts. Does it really occur often that you have two filenames in the same dir only differing by case? I'd imagine aux and prn are still illegal, right? The numbers are fewer, these days, but there are still source packages out there that have 'aux/' subdirectories. No. Aux is fine now. As is nul, prn, com, ... Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: New Cygwin 1.7.0-18 in release-2
On Jul 31 15:23, Corinna Vinschen wrote: On Jul 31 08:59, Charles Wilson wrote: Corinna Vinschen wrote: Illegal? The only illegal chars are slash and backslash, even on case-insensitive mounts. Does it really occur often that you have two filenames in the same dir only differing by case? I'd imagine aux and prn are still illegal, right? The numbers are fewer, these days, but there are still source packages out there that have 'aux/' subdirectories. No. Aux is fine now. As is nul, prn, com, ... Btw., the list of changes attached to my original mail starting this thread http://cygwin.com/ml/cygwin-apps/2008-07/msg00060.html already mentioned that. This is one result of using NT functions exclusively for file access. What still won't work, though is to start an application called, for instance, aux.exe. The reason is that the CreateProcess call in spawn/exec is still a Win32 call which will treat this filename as a DOS device. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
RE: [RFC] 1.7 Packaging: Toolchain
Dave Korn wrote on 29 July 2008 14:00: Getting libstdc++ to work shared is being tricky; for some reason libsupc++ is only built static, which means libtool links it into libstdc++ only to resolve imports, not as objects that need to be exported. Removing the --disable-shared libtool tag from libsupc++'s build configuration gets me what appears to be a complete libstdc++, but it fails in early startup, probably down to the relocs-in-.rodata issue; and that's where I've got to. I'm not sure whether to just try and go for a shared-libstdc-static-libsupc combo, or to try and figure out what needs to be fixed to prevent the relocs problem - if indeed that's what it is. It wasn't and I think I've solved it! cheers, DaveK -- Can't think of a witty .sigline today
Re: New Cygwin 1.7.0-18 in release-2
On Jul 31 15:30, Corinna Vinschen wrote: On Jul 31 15:23, Corinna Vinschen wrote: On Jul 31 08:59, Charles Wilson wrote: Corinna Vinschen wrote: Illegal? The only illegal chars are slash and backslash, even on case-insensitive mounts. Does it really occur often that you have two filenames in the same dir only differing by case? I'd imagine aux and prn are still illegal, right? The numbers are fewer, these days, but there are still source packages out there that have 'aux/' subdirectories. No. Aux is fine now. As is nul, prn, com, ... Btw., the list of changes attached to my original mail starting this thread http://cygwin.com/ml/cygwin-apps/2008-07/msg00060.html already mentioned that. This is one result of using NT functions exclusively for file access. What still won't work, though is to start an application called, for instance, aux.exe. The reason is that the CreateProcess call in spawn/exec is still a Win32 call which will treat this filename as a DOS device. Hang on, I have a workaround for that problem. It works fine when using the long path prefix \\?\ in the call to CreateProcessW. Unfortunately I had to add code to remove the \\?\ prefix for paths which fit into 260 chars to avoid problems with native Win32 apps so that's kind of a chicken-egg. Hmm, tricky. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: New Cygwin 1.7.0-18 in release-2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Corinna Vinschen wrote: | Illegal? The only illegal chars are slash and backslash, even on | case-insensitive mounts. Does it really occur often that you have two | filenames in the same dir only differing by case? For Cygwin I understand that, but you mean to say that *setup* will be able to install a file with a *:|? (The : is the most common case, usually within API docs, for obvious reasons.) If the only thing I have to worry about not installing is case-insensitive files in the same directory, I know of three cases (WindowMaker, gnome-chess, and liblouis) among 1650+ sources. Yaakov -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkiR1LUACgkQpiWmPGlmQSPuWgCcCpCPoohY/4qxF++DZezCJZtD cPQAoI0SEFSv21YpVkguB8cgyfKk8jdD =pzfn -END PGP SIGNATURE-
Re: New Cygwin 1.7.0-18 in release-2
On Jul 31 10:05, Yaakov (Cygwin Ports) wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Corinna Vinschen wrote: | Illegal? The only illegal chars are slash and backslash, even on | case-insensitive mounts. Does it really occur often that you have two | filenames in the same dir only differing by case? For Cygwin I understand that, but you mean to say that *setup* will be able to install a file with a *:|? (The : is the most common case, usually within API docs, for obvious reasons.) Uh oh, you got me there. It shouldn't be ovberly complicated to tweak the untar code in setup to do the same special char conversion as Cygwin does, but, as usual, somebody has to do it. Maybe I'll look into that myself when I'm back in a couple of days. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: New Cygwin 1.7.0-18 in release-2
On Jul 31 16:10, Corinna Vinschen wrote: On Jul 31 15:30, Corinna Vinschen wrote: What still won't work, though is to start an application called, for instance, aux.exe. The reason is that the CreateProcess call in spawn/exec is still a Win32 call which will treat this filename as a DOS device. Hang on, I have a workaround for that problem. It works fine when using the long path prefix \\?\ in the call to CreateProcessW. Unfortunately I had to add code to remove the \\?\ prefix for paths which fit into 260 chars to avoid problems with native Win32 apps so that's kind of a chicken-egg. Hmm, tricky. I uploaded 1.7.0-23 to the release-2 area. It fixes the above problem. Now you can call an application called aux.exe just fine. Other changes: - Instead of restricting send/sendto/sendmsg calls to 64K, send data in 64K chunks under the hood to circumvent problem described in KB 201213. - Reworked tty code to handle inheritance better. - Remove some ancient code and better never used APIs. - Constify utmp/login API. - Fix for file systems which get confused when using NtQueryDirectoryFile with FileIdBothDirectoryInformation info class (just UNIXFS right now). Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
src/winsup/cygwin ChangeLog spawn.cc
CVSROOT:/cvs/src Module name:src Changes by: [EMAIL PROTECTED] 2008-07-31 14:41:19 Modified files: winsup/cygwin : ChangeLog spawn.cc Log message: * spawn.cc (spawn_guts): Check constructed short pathname for being a DOS device name and fall back to long path name, if so. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/ChangeLog.diff?cvsroot=srcr1=1.4240r2=1.4241 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/spawn.cc.diff?cvsroot=srcr1=1.265r2=1.266
Re: Pycairo on cygwin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Larry Hall (Cygwin) wrote: | I can't say. But the couple of posts I saw made me think that this | may have come from the Cygwin Ports site. I did find a python-cairo | package there. Perhaps that's what you're looking for? | | Keep in mind that the Cygwin Ports site contains packages that are | _not_ currently part of the distribution. Use at your own peril. ;-) python-cairo is available in Ports, or you could build yourself: http://cygwin-ports.cvs.sourceforge.net/cygwin-ports/ports/python/pycairo/ Yaakov -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkiRZkUACgkQpiWmPGlmQSMY/QCg/M0wAGKV7v/XpgVnwMdPdebe zl0AoKEeeGmwtH+9Vk1STg/35QJqtTGh =ymvj -END PGP SIGNATURE- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
[ANNOUNCEMENT] Updated: pcre-7.7-2 [SECURITY]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The following packages have been updated in the Cygwin net release: +++ libpcre0-7.7-2 +++ pcre-7.7-2 +++ pcre-devel-7.7-2 +++ pcre-doc-7.7-2 This is an upstream version bump, and includes a patch for CVE-2008-2371. Yaakov *** 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: [EMAIL PROTECTED] If you need more information on unsubscribing, start reading here: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkiRWkgACgkQpiWmPGlmQSP8ZwCeKZTWIxJ4/B/+idIQmem/T3Sk AjQAn2tZwlkF/s+ot/wPbCqr0fBPqwIo =TF1Z -END PGP SIGNATURE- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
[ANNOUNCEMENT] Updated: libart_lgpl2-2.3.20-1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The following packages have been updated in the Cygwin net release: *** libart_lgpl2-2.3.20-1 +++ libart_lgpl2-devel-2.3.20-1 This is the latest upstream version bump. A separate -devel package has been created. Yaakov *** 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: [EMAIL PROTECTED] If you need more information on unsubscribing, start reading here: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkiRWswACgkQpiWmPGlmQSPlowCg3JSYl34TP4tPobO+HJ4OdibD ajgAoOw54tOS6cDArvMv1wnY6Lk6VsJA =SLLg -END PGP SIGNATURE- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
[ANNOUNCEMENT] Updated: intltool-0.40.3-1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The following packages have been updated in the Cygwin net release: *** intltool-0.40.3-1 This is the latest upstream version bump. intltool no longer installs its scripts into the source tree, rather it uses the system-installed scripts. This means intltool must now be installed for building most GNOME packages. Yaakov *** 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: [EMAIL PROTECTED] If you need more information on unsubscribing, start reading here: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkiRW3MACgkQpiWmPGlmQSMdjACfQFMyFsuo1TfTbXliTGieoKa5 PwIAoIsO/di4V02TnWkmF0+7ZIs9WYLi =sBi8 -END PGP SIGNATURE- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
[ANNOUNCEMENT] Updated: gnome-common-2.20.0-2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The following packages have been updated in the Cygwin net release: *** gnome-common-2.20.0-2 This package contains gnome-autogen.sh and gnome-doc-common. It is used by the new release of cygport for building almost all GNOME packages. Yaakov *** 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: [EMAIL PROTECTED] If you need more information on unsubscribing, start reading here: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkiRXB0ACgkQpiWmPGlmQSPZrwCfQfedh3EzrgJSsSKPZEt27gsR ftwAoLEyhlpIwApYUSITRj/kGVJjxnWZ =AhqU -END PGP SIGNATURE- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
[ANNOUNCEMENT] Updated: libexif-0.6.16-2 [SECURITY]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The following packages have been updated in the Cygwin net release: *** libexif-0.6.16-2 *** libexif12-0.6.16-2 *** libexif-devel-0.6.16-2 This release includes patches for CVE-2007-6351 and CVE-2007-6352. Yaakov *** 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: [EMAIL PROTECTED] If you need more information on unsubscribing, start reading here: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkiRXYQACgkQpiWmPGlmQSNlOwCfQTxA0CeW7cKsqDlcc/UjBzoA gkwAoMYBWA9r1vNsYRC9oKyVjz4nMxok =Kog4 -END PGP SIGNATURE- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
[ANNOUNCEMENT] Updated: libxml2-2.6.32-1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The following packages have been updated in the Cygwin net release: *** libxml2-2.6.32-1 *** libxml2-devel-2.6.32-1 *** libxml2-doc-2.6.32-1 *** python-libxml2-2.6.32-1 This is the latest upstream version. Yaakov *** 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: [EMAIL PROTECTED] If you need more information on unsubscribing, start reading here: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkiRXyUACgkQpiWmPGlmQSNViACdGdhtYG/tDKJ7UmefrgHkFY1q 4xcAoMeGu/Oju0OH4qtoOpAhufuyWcg+ =mUN0 -END PGP SIGNATURE- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
[ANNOUNCEMENT] Updated: libxslt-1.1.24-1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The following packages have been updated in the Cygwin net release: *** libxslt-1.1.24-1 *** libxslt-devel-1.1.24-1 *** libxslt-doc-1.1.24-1 *** python-libxslt-1.1.24-1 This is the latest upstream version. Yaakov *** 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: [EMAIL PROTECTED] If you need more information on unsubscribing, start reading here: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkiRX18ACgkQpiWmPGlmQSMkkQCcDpQabIE8wwKMhmvN0+p7+ECI 4JsAoMJSpkYHyswn4oTQc0tJMaU/y0l8 =Mchz -END PGP SIGNATURE- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
[ANNOUNCEMENT] Updated: cygport-0.3.12-1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following packages have been updated in the Cygwin net release:
*** cygport-0.3.12-1
This is the latest release of the cygport package building tool.
New in 0.3.12:
* unpack(): now handles .tar.bz tarballs.
* KEEPDIRS can be defined in place to call keepdir() automatically.
* claws-mail.cygclass: NEW for claws-mail plugins.
* gst-plugins0.10.cygclass: Added gst-plugins-gl; default sinks/srcs.
* octave.cygclass: NEW for Octave extensions.
* ruby-gnome2.cygclass: Now builds split packages from monolithic source.
New in 0.3.11:
* {SRC,PATCH}_URI may contain CGI query arguments.
* Empty subpackages may be created by defining empty PKG_CONTENTS[n].
* RESTRICT=postinst-gconf stops automatic GConf schemas postinst/prerm.
* ebook.cygclass: NEW for EBook documentation packages.
* ggz.cygclass: NEW for GGZ Gaming Zone packages.
* gnome2.cygclass: Several improvements for GNOME 2.22.
* mtn.cygclass: NEW for Monotone repository checkouts.
* opensync.cygclass: NEW for libopensync-plugin-* packages.
New in 0.3.10:
* Accept PKG_IGNORE to avoid missing files warning.
* Notify when removing empty directories during postinstall.
* Move /usr/man to /usr/share/man.
* Remove Mono .mdb debug symbols during strip.
* fox.cygclass: Libs and separate apps can be built from one -src.
* gnome2.cygclass: Use gnome-autogen.sh for autoreconf.
* gst-plugins0.10.cygclass: Update for GStreamer 0.10.19 et al.
* php.cygclass: Fixes for external PHP_CHANNEL, Zend extensions.
Yaakov
*** 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:
[EMAIL PROTECTED]
If you need more information on unsubscribing, start reading here:
http://sources.redhat.com/lists.html#unsubscribe-simple
Please read *all* of the information on unsubscribing that is available
starting at this URL.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEAREIAAYFAkiRYEkACgkQpiWmPGlmQSPNvACg14hEWDJc8qQhrV/bVD/Vk80v
DMUAoKQZZKOWb5oJUar7/GnICA33leHz
=+cLv
-END PGP SIGNATURE-
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
[ANNOUNCEMENT] Updated: check-0.9.5-1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The following packages have been updated in the Cygwin net release: *** check-0.9.5-1 This is the latest upstream version. Yaakov *** 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: [EMAIL PROTECTED] If you need more information on unsubscribing, start reading here: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkiRYTUACgkQpiWmPGlmQSNHmwCeI/4bQ0VpygXDdqA8gyxmeIeU z7YAnRlNgX9kAl91VIelN66upTDoarMX =gQa0 -END PGP SIGNATURE- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: CSIH file permission tests on non-NTFS broken (was Re: ssh-host-config script fails)
On Jul 31 00:53, Charles Wilson wrote:
Corinna Vinschen wrote:
Eeek! You're using FAT32 on a NT based OS? This isn't such a good
idea, actually. There's no security and no permission settings on FAT.
The csih script seems to miss the fact that the directory is on a
non-NTFS drive which isn't capable of setting permissions. Given that
you're installing ssh, which is a paranoid secure playing package,
that's actually a good idea. Ever thought of running convert.exe on
your drive? ;)
Nevertheless that should be changed in csih.
Could you have a look into this, please?
I'm not sure what you think csih should do, here. The whole point is that
we know services require certain things of the system directories, or they
won't work. Are you suggesting that csih just ignore that, and pretend to
correctly install sshd on a FAT32 system?
Only to have sshd itself fail for some hard-for-a-newbie-to-diagnose
reason?
Sshd won't fail on FAT32 since it checks the file system capbailities
before checking for strict permissions.
Perhaps, rather than checking:
# daemons need access to subdirs, so need traverse permissions...
if ! csih_check_dir_perms ${LOCALSTATEDIR} d..x..x..x ; then ERROR
[...]
in _csih_setup() (which is called by the main csih entry points), those
permission checks could be delegated to the foo_install scripts which know
more about their own specific requirements, rather than the fairly general
requirements above?
Or are you saying that csih should still perform those general checks, but
first:
if the drive on which ${LOCALSTATEDIR} lives is
(1) FAT32
(2) nontsec
(3) on a server and nosmbntsec
then issue a big fat warning, and in that case skip the
permissions tests? What about 1.7 and the acl flag?
A check for non-NTFS should be sufficient for now, IMHO. It's bad
enough to run an OS on such an insecure file system, but it's hard to
enforce upgrading to NTFS. However, ntsec and smbntsec are dead in the
water and I don't think we should encourage usage of noacl more than
necessary, especially for sensitive services.
ASIDE:
csih_check_basic_mounts
csih_check_sys_mount
might need to be revisited for 1.7
FYI, the other changes to csih that you requested are actually rather more
involved than you would suspect. I've worked on it a bit, but haven't been
able to test it yet. Stay tuned.
Ok, no worries,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
Re: Pycairo on cygwin
Yaakov (Cygwin Ports) ha scritto: Larry Hall (Cygwin) wrote: | I can't say. But the couple of posts I saw made me think that this | may have come from the Cygwin Ports site. I did find a python-cairo | package there. Perhaps that's what you're looking for? | | Keep in mind that the Cygwin Ports site contains packages that are | _not_ currently part of the distribution. Use at your own peril. ;-) python-cairo is available in Ports, or you could build yourself: http://cygwin-ports.cvs.sourceforge.net/cygwin-ports/ports/python/pycairo/ Thanks Larry and Yaakox for your answers, this solved my problem (though I will probably need to better understand pkgconfig in the future). Pietro -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: flex: exec failed?
Arg.. simple repro is this Python code, with the appropriate gcc source tree: #! /usr/bin/env python import os import sys def Run(Directory, Command): sys.stderr.flush() sys.stdout.flush() print(cd + Directory ++ Command) PreviousDirectory = os.getcwd() os.chdir(Directory) if os.name == nt: Command = sh -c \ + Command + \ sys.stderr.flush() sys.stdout.flush() ExitCode = os.system(Command) os.chdir(PreviousDirectory) sys.stderr.flush() sys.stdout.flush() if ExitCode != 0: sys.exit(ExitCode) if not os.path.isdir(./obj): Run(., mkdir ./obj) if not os.path.isfile(./obj/Makefile): Run(./obj, ../gcc/configure) Run(., rm -rf ./obj/gmp) Run(./obj, make configure-gmp) Repros in Python, not outside of Python? Why? That is the question. Other tidbits: flex actually fails to exec m4 either way, just that one way it manages to create lex.yy.c first. It fails to exec m4 because gmp's configure has set M4=m4-not-needed. This is almost certainly a simple bug in gmp's configure. A fix would be to probe for external programs (yacc, lex), earlier, before it sets M4. Or unset M4 after it is done with it. But there is still something amiss, maybe Cygwin specific, maybe not. Oh, and whether or not gmp sets M4 varies somewhat on build/host/target. Usually, configuring gmp on its own, probably it is set. But within gcc, generally not, because gcc configures it with processor=none for reasons I don't understand.. I guess it'd be nice if flex printed what it was trying to run -- getenv(M4) and not just m4. I'll follow up separately, at least gcc and gmp.. Still not completely solved. I do have a quick repro though, you can strip down the configure script a bunch and it repros in just a few seconds. Going through the strace logsbut need to read flex also for when it creates the output vs. running m4.. - Jay From: [EMAIL PROTECTED] To: cygwin@cygwin.com Subject: RE: flex: exec failed? Date: Sat, 26 Jul 2008 12:40:01 + anecdotes... I've seen this quite a few times now, like 10. Always this same error -- always configure unable to determine the (f)lex output, I think always configuring gmp. (Maybe binutils sometimes, due to the flex source directory, understood, red herring.) I've done a lot else successfully, configure/built gcc/binutils/gmp/mpfr, this is the one failure I've seen a few of. That is -- lots of stuff works, I'm not messing things up in some large way, but this fails often. I'm not using tee any longer, but still running all of this within Python (os.system). I don't usually check config.log, but it always the same configure test. Peeling one layer, either cd'ing in cmd or bash to gcc toplevel and doing make configure-gmp or two layers, cd'ing to gcc/gmp and whatever/configure whatever, has a much much higher success rate. And then I can run my stuff, which is incremental enough, and so I skip past this. I stopped installing Cygwin at the root, though I've seen it both work and not-work that way. I am usually on XP/AMD64, and maybe every repro is on that. I do notice comments about thread unsafety in Cygwin's fork/exec code. My Python is single threaded (I was getting intermittent errors about unable to allocate locks). I'll have to put strace in there and focus in on it, instead of continuing to workaround. ..Jay From: [EMAIL PROTECTED] To: cygwin@cygwin.com Subject: FW: flex: exec failed? Date: Wed, 16 Jul 2008 18:55:06 + It failed again without the time/tee. Time to try with -disable-bootstrap, and if it still failed, reboot, and... From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: flex: exec failed? Date: Wed, 16 Jul 2008 18:53:23 + anyone familiar with this: flex: fatal internal error, exec failed flex: error writing output file lex.yy.c It comes while configuring gmp, in a merged (Cygnus) gcc tree. I've been able to build this several times, various configurations. (various host/target and options, mostly build=cygwin, but on some other systems too, unrelated..) What I am doing differently this time is two things. 1) I'm no longer -disable-bootstrap. I am running under a wrapper .py file. (It goes through multiple configurations.) That isn't changed, but: 2) previously: ./build.py now: time (sh -c ./build.py | tee 1.log) or time (./build.py | tee 1.log) I have tried both. config.log nearby: configure:32814: checking for flex configure:32840: result: flex configure:32853: checking for yywrap in -lfl configure:32883: gcc -o conftest.exe -g -fkeep-inline-functions -DNO_ASM conftest.c -lfl5 configure:32889: $? = 0 configure:32893: test -z || test ! -s conftest.err configure:32896: $? = 0 configure:32899: test -s conftest.exe configure:32902: $? = 0 configure:32915: result: yes configure:32993: checking lex output file root configure:33004: flex conftest.l flex:
RE: flex: exec failed?
Ok, it works the same on Cygwin and Linux/x86, but Python/NTAMD64 works. Somehow Python/Posix related, portably. For anyone interested: $ echo %% conftest.l $ echo %% conftest.l $ rm lex.yy.c $ export M4=foo $ flex conftest.l flex: fatal internal error, exec failed lex.yy.c exists $ rm lex.yy.c $ python -c import os; os.system(\flex conftest.l\) flex: fatal internal error, exec failed flex: 2 error writing output file lex.yy.c (I added the 2 to disambiguate 4 identical error messages) lex.yy.c does not exists -- make configure-gmp fails relevant code in flex: filter_tee_header: if ((to_cfd = dup (1)) == -1) flexfatal (_(dup(1) failed)); to_c = fdopen (to_cfd, w); ... fflush (to_c); if (ferror (to_c)) lerrsf (_(2 error writing output file %s), outfilename ? outfilename : ); else if (fclose (to_c)) lerrsf (_(error closing output file %s), outfilename ? outfilename : ); while (wait (0) 0) ; again, I added the 2. Digging deeper... - Jay [snip snip snip] -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
How to run cygwin compiled/linked application on machine without cygwin installed?
I have c++ application built on machine A with cygwin (1.5.25-14) installed. I have copied the application and cygwin1.dll to machine B, where cygwin has not been installed. When I attempt to execute the application I get alert messages that various cygwin dlls are missing and that reinstalling may help to solve the problem. My understanding is that only the cygwin1.dll was required. I ran cygcheck on my application executable and I did get list of several dlls (eg: cygXm-2.dll) as dependencies. I am uncertain how to proceed. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
ctrl-c terminates ssh session using cmd.exe login shell
Using cmd.exe as the login shell, ctrl-c terminates the ssh session (rather than being propagated to the process on the remote server). I have read that the shell is not a Windows console but rather a Cygwin pseudo tty session. Hence there is no Windows console signal handling to take care of the ctrl-c. Hence ctrl-c is sent to ssh. My question is - is there some way to work around this? For example, running bash as the login shell, and then running cmd.exe, does not fix the problem (as expected). Nor does using rxvt (as expected). Is there any way to get a functional cmd login shell - With working arrow keys, ctrl-c, edit, etc? Thank you for any insight into this problem. Stephen cygcheck.out Description: cygcheck.out -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: How to run cygwin compiled/linked application on machine without cygwin installed?
Karen Frank wrote: I have c++ application built on machine A with cygwin (1.5.25-14) installed. I have copied the application and cygwin1.dll to machine B, where cygwin has not been installed. When I attempt to execute the application I get alert messages that various cygwin dlls are missing and that reinstalling may help to solve the problem. My understanding is that only the cygwin1.dll was required. I ran cygcheck on my application executable and I did get list of several dlls (eg: cygXm-2.dll) as dependencies. I am uncertain how to proceed. If installing Cygwin is not an option for some reason, then you need all the DLLs you see listed by 'cygcheck'. Of course this will make you a http://cygwin.com/acronyms/#3PP. You have been warned and may be shunned. See if you can sleep well now! ;-) -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: How to run cygwin compiled/linked application on machine without cygwin installed?
Larry Hall (Cygwin) wrote: Karen Frank wrote: I have c++ application built on machine A with cygwin (1.5.25-14) installed. I have copied the application and cygwin1.dll to machine B, where cygwin has not been installed. When I attempt to execute the application I get alert messages that various cygwin dlls are missing and that reinstalling may help to solve the problem. My understanding is that only the cygwin1.dll was required. I ran cygcheck on my application executable and I did get list of several dlls (eg: cygXm-2.dll) as --^ dependencies. I am uncertain how to proceed. If installing Cygwin is not an option for some reason, then you need all the DLLs you see listed by 'cygcheck'. Of course this will make you a http://cygwin.com/acronyms/#3PP. You have been warned and may be shunned. See if you can sleep well now! ;-) And you need Cywin/X running (the above library is for X windows) which is a lot more than a list of libraries. -- René Berber -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
GCC 3.4.4-3 in version 1.7 produces an error during setup
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ok. I finally decided to do the update to 1.7 and in being that I like to make sure there are no conflicts I dumped my entire 1.5 install that I had working. While trying to install gcc I get the following error... Can't open file://C:\cygwin\packages/http%3a%2f%2fcygwin.elite-systems.org%2f/release-2/gcc/gcc-3.4.4-3.tar.bz2 for reading: Invalid or unsupported tar format. Just in case I tried another mirror. Afterwards I checked it on the server. The actual archive is empty. When the 1st level compression is removed (only a tar file) then I did a hex dump and it looks like it is just a filler file that contains only hex 00 in it. Any chance we might be able to fix this error in the installer. I can tell this method was intentional but the error kinda threw me off. This was using the latest cygwin 1.7 installer file. - -- Robert Pendell [EMAIL PROTECTED] A perfect world is one of chaos. Thawte Web of Trust Notary CAcert Assurer -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIklIas1pR2j1qW+sRAihJAJ0TGFaDkIwEUIopiPc5SG9O9unOLwCeNesg aj8TVcRlwfFLS91wY/4JrOA= =69Tf -END PGP SIGNATURE- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Updated: pcre-7.7-2 [SECURITY]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The following packages have been updated in the Cygwin net release: +++ libpcre0-7.7-2 +++ pcre-7.7-2 +++ pcre-devel-7.7-2 +++ pcre-doc-7.7-2 This is an upstream version bump, and includes a patch for CVE-2008-2371. Yaakov *** 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: [EMAIL PROTECTED] If you need more information on unsubscribing, start reading here: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkiRWkgACgkQpiWmPGlmQSP8ZwCeKZTWIxJ4/B/+idIQmem/T3Sk AjQAn2tZwlkF/s+ot/wPbCqr0fBPqwIo =TF1Z -END PGP SIGNATURE-
Updated: libart_lgpl2-2.3.20-1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The following packages have been updated in the Cygwin net release: *** libart_lgpl2-2.3.20-1 +++ libart_lgpl2-devel-2.3.20-1 This is the latest upstream version bump. A separate -devel package has been created. Yaakov *** 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: [EMAIL PROTECTED] If you need more information on unsubscribing, start reading here: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkiRWswACgkQpiWmPGlmQSPlowCg3JSYl34TP4tPobO+HJ4OdibD ajgAoOw54tOS6cDArvMv1wnY6Lk6VsJA =SLLg -END PGP SIGNATURE-
Updated: intltool-0.40.3-1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The following packages have been updated in the Cygwin net release: *** intltool-0.40.3-1 This is the latest upstream version bump. intltool no longer installs its scripts into the source tree, rather it uses the system-installed scripts. This means intltool must now be installed for building most GNOME packages. Yaakov *** 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: [EMAIL PROTECTED] If you need more information on unsubscribing, start reading here: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkiRW3MACgkQpiWmPGlmQSMdjACfQFMyFsuo1TfTbXliTGieoKa5 PwIAoIsO/di4V02TnWkmF0+7ZIs9WYLi =sBi8 -END PGP SIGNATURE-
Updated: gnome-common-2.20.0-2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The following packages have been updated in the Cygwin net release: *** gnome-common-2.20.0-2 This package contains gnome-autogen.sh and gnome-doc-common. It is used by the new release of cygport for building almost all GNOME packages. Yaakov *** 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: [EMAIL PROTECTED] If you need more information on unsubscribing, start reading here: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkiRXB0ACgkQpiWmPGlmQSPZrwCfQfedh3EzrgJSsSKPZEt27gsR ftwAoLEyhlpIwApYUSITRj/kGVJjxnWZ =AhqU -END PGP SIGNATURE-
Updated: check-0.9.5-1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The following packages have been updated in the Cygwin net release: *** check-0.9.5-1 This is the latest upstream version. Yaakov *** 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: [EMAIL PROTECTED] If you need more information on unsubscribing, start reading here: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkiRYTUACgkQpiWmPGlmQSNHmwCeI/4bQ0VpygXDdqA8gyxmeIeU z7YAnRlNgX9kAl91VIelN66upTDoarMX =gQa0 -END PGP SIGNATURE-
