Re: ITP dos2unix 5.2.1-1
On 03/15/2011 11:17 PM, Eric Blake wrote: dos2unix is already part of cygwin. 'cygcheck -p dos2unix' shows that it is part of cygutils, so I see no reason to repackage it as an alternative build. Hi, dos2unix on cygwin is different, it is 'conv'. The implementation I propose is used on major Linux distributions. You could keep 'conv' on cygwin. I propose to obsolete the links dos2unix and unix2dos to conv, and replace them with the dos2unix implementation as used on Linux. Erwin
Re: ITP dos2unix 5.2.1-1
On 3/16/2011 3:59 AM, Erwin Waterlander wrote: dos2unix on cygwin is different, it is 'conv'. The implementation I propose is used on major Linux distributions. You could keep 'conv' on cygwin. I propose to obsolete the links dos2unix and unix2dos to conv, and replace them with the dos2unix implementation as used on Linux. Then you're going to have to explain why the other implementation is better (not just but that's the one the linux people use: cygwin is not linux) AND ensure that the new version is capable of ALL the modes of operation that the old version supports. Otherwise, you may break people's existing usage patterns. Offhand, I can think of several (there might be more): * The --safe and --force options * The ability to operate as part of a pipe (stdin/stdout) * --auto mode (with 3 formats, dos/unix/mac, there is no opposite) but that doesn't really matter for the explicit d2u/u2d variants. Only 'conv' needs to worry about --auto) Now, I'm not opposed to removing u2d/d2u/dos2unix/unix2dos from cygutils. Less apps to support makes life easier for me. I just don't want to break anyone's existing setup, usage patterns, or scripts. -- Chuck cygutils maintainer
Re: ITP dos2unix 5.2.1-1
On 03/16/2011 02:52 PM, Charles Wilson wrote: Then you're going to have to explain why the other implementation is better (not just but that's the one the linux people use: cygwin is Hi Chuck, I think it's a good argument. Most cygwin programs are ported from Unix/Linux. Scripts that come from Linux don't need to be modified for dos2unix any more with the version I propose. Quota from http://cygwin.com Cygwin is: * a collection of tools which provide a Linux look and feel environment for Windows. not linux) AND ensure that the new version is capable of ALL the modes of operation that the old version supports. Otherwise, you may break people's existing usage patterns. Offhand, I can think of several (there might be more): * The --safe and --force options Dos2unix is by default safe, with an option to force conversion. * The ability to operate as part of a pipe (stdin/stdout) Yes. And in-place and paired conversion. * --auto mode (with 3 formats, dos/unix/mac, there is no opposite) but that doesn't really matter for the explicit d2u/u2d variants. Only 'conv' needs to worry about --auto) There is no auto mode. But dos/unix/mac conversion is supported. I propose to keep 'conv'. So people who like conv's auto mode can still use it. Additional features: * keep file date. * ISO and 7bit conversion like on SunOS * Internationalisation. Now, I'm not opposed to removing u2d/d2u/dos2unix/unix2dos from cygutils. Less apps to support makes life easier for me. I just don't want to break anyone's existing setup, usage patterns, or scripts. The command-line options are not compatible, but the difference is not very big. Most people will use it without options I guess. It depends on what you are used to. If you come from Linux or Cygwin. best regards, Erwin
Re: ITP dos2unix 5.2.1-1
On Wed, Mar 16, 2011 at 03:52:36PM +0100, Erwin Waterlander wrote: On 03/16/2011 02:52 PM, Charles Wilson wrote: Then you're going to have to explain why the other implementation is better (not just but that's the one the linux people use: cygwin is Hi Chuck, I think it's a good argument. Most cygwin programs are ported from Unix/Linux. Scripts that come from Linux don't need to be modified for dos2unix any more with the version I propose. It's only a good argument if you can point to messages where people have been demonstrably confused or have needed to change scripts to deal with different behavior. Quota from http://cygwin.com Cygwin is: * a collection of tools which provide a Linux look and feel environment for Windows. That is true but these tools have been in the distro for years and I don't recall any complaints. That argues for a pragmatic it's not broke philosophy. * --auto mode (with 3 formats, dos/unix/mac, there is no opposite) but that doesn't really matter for the explicit d2u/u2d variants. Only 'conv' needs to worry about --auto) There is no auto mode. But dos/unix/mac conversion is supported. I propose to keep 'conv'. So people who like conv's auto mode can still use it. cygwin-apps comprises only a limited subset of people who could be using these tools. We shouldn't just resolve to change behavior. If it is decided that this is something that needs to be addressed then we'll have to poll the community. Additional features: * keep file date. * ISO and 7bit conversion like on SunOS * Internationalisation. Now, I'm not opposed to removing u2d/d2u/dos2unix/unix2dos from cygutils. Less apps to support makes life easier for me. I just don't want to break anyone's existing setup, usage patterns, or scripts. The command-line options are not compatible, but the difference is not very big. Most people will use it without options I guess. It depends on what you are used to. If you come from Linux or Cygwin. This is, again, something that you can't assume. We don't know how people use these tools. So, if we do decide to make the switch, you will have to be dedicated to being active in responding to problem reports on the mailing list. And, if people here think it's a good idea to move this along, we'll need to get some feedback from the larger community. cgf
Re: ITP dos2unix 5.2.1-1
On 03/16/2011 04:49 PM, Christopher Faylor wrote: This is, again, something that you can't assume. We don't know how people use these tools. So, if we do decide to make the switch, you will have to be dedicated to being active in responding to problem reports on the mailing list. And, if people here think it's a good idea to move this along, we'll need to get some feedback from the larger community. I'm fine with that. I made this package, because a cygwin user asked me. For me it's a small effort to maintain a cygwin package for this. I am committed to solve problems. If the cygwin community doesn't want to switch, that's fine too. Erwin
Re: ITP dos2unix 5.2.1-1
Erwin Waterlander wrote: On 03/16/2011 04:49 PM, Christopher Faylor wrote: This is, again, something that you can't assume. We don't know how people use these tools. So, if we do decide to make the switch, you will have to be dedicated to being active in responding to problem reports on the mailing list. And, if people here think it's a good idea to move this along, we'll need to get some feedback from the larger community. I'm fine with that. I made this package, because a cygwin user asked me. For me it's a small effort to maintain a cygwin package for this. I am committed to solve problems. If the cygwin community doesn't want to switch, that's fine too. An alternative would be to modify cygutils+dos2unix packages such that the user can select the flavor of dos2unix/unix2dos commands with /usr/sbin/alternatives. If cygutils is the default if installed this should not break anything. Christian
Re: ITP dos2unix 5.2.1-1
On Wed, Mar 16, 2011 at 08:29:51PM +0100, Christian Franke wrote: Erwin Waterlander wrote: On 03/16/2011 04:49 PM, Christopher Faylor wrote: This is, again, something that you can't assume. We don't know how people use these tools. So, if we do decide to make the switch, you will have to be dedicated to being active in responding to problem reports on the mailing list. And, if people here think it's a good idea to move this along, we'll need to get some feedback from the larger community. I'm fine with that. I made this package, because a cygwin user asked me. For me it's a small effort to maintain a cygwin package for this. I am committed to solve problems. If the cygwin community doesn't want to switch, that's fine too. An alternative would be to modify cygutils+dos2unix packages such that the user can select the flavor of dos2unix/unix2dos commands with /usr/sbin/alternatives. If cygutils is the default if installed this should not break anything. Hey, good idea, assuming that Chuck is amenable. I'd be happy to just let the package in given that proviso if so. cgf
Re: ITP dos2unix 5.2.1-1
On 3/16/2011 3:32 PM, Christopher Faylor wrote: On Wed, Mar 16, 2011 at 08:29:51PM +0100, Christian Franke wrote: An alternative would be to modify cygutils+dos2unix packages such that the user can select the flavor of dos2unix/unix2dos commands with /usr/sbin/alternatives. If cygutils is the default if installed this should not break anything. Except you would no longer be able to run dos2unix/unix2dos/d2u/u2d from a non-cygwin context, such as 'naked' cmd.exe or some IDE like Eclipse. Hey, good idea, assuming that Chuck is amenable. I'd be happy to just let the package in given that proviso if so. Uh, let's think about that a minute. cygutils is pulled in as part of Base (cygutils is not in the Base category, but it is required by a packages that is: cygwin-doc). Adding alternatives as a dep of cygutils would then make alternatives an implicit part of Base. alternatives itself brings in no other unsavory dependencies. This would be a change, since although alternatives is used by some very common packages [vim, automake], it's not in the default Base-only (actually, Base+requirements) installation. It also means that cygwin's dos2unix could no longer be executed from a non-cygwin context, because of the symlinks. Finally, Eric Blake already referenced this possibility, I think: I see no reason to repackage it as an alternative build. If everybody else is ok with that, then I have no objections...but I think we should hear from folks about these (possible) issues before making a decision. -- Chuck
Re: ITP dos2unix 5.2.1-1
On Wed, Mar 16, 2011 at 04:05:17PM -0400, Charles Wilson wrote: On 3/16/2011 3:32 PM, Christopher Faylor wrote: On Wed, Mar 16, 2011 at 08:29:51PM +0100, Christian Franke wrote: An alternative would be to modify cygutils+dos2unix packages such that the user can select the flavor of dos2unix/unix2dos commands with /usr/sbin/alternatives. If cygutils is the default if installed this should not break anything. Except you would no longer be able to run dos2unix/unix2dos/d2u/u2d from a non-cygwin context, such as 'naked' cmd.exe or some IDE like Eclipse. Hey, good idea, assuming that Chuck is amenable. I'd be happy to just let the package in given that proviso if so. Uh, let's think about that a minute. cygutils is pulled in as part of Base (cygutils is not in the Base category, but it is required by a packages that is: cygwin-doc). Adding alternatives as a dep of cygutils would then make alternatives an implicit part of Base. alternatives itself brings in no other unsavory dependencies. This would be a change, since although alternatives is used by some very common packages [vim, automake], it's not in the default Base-only (actually, Base+requirements) installation. It also means that cygwin's dos2unix could no longer be executed from a non-cygwin context, because of the symlinks. Finally, Eric Blake already referenced this possibility, I think: I see no reason to repackage it as an alternative build. If everybody else is ok with that, then I have no objections...but I think we should hear from folks about these (possible) issues before making a decision. Ah, right. I didn't get that Eric was referring to this scenario but, regardless, I should have remembered that alternatives means using symlinks. Given the use that d2u is put, I don't think we want to make it a symlink. So, I guess that means that we poll the community if we want to go ahead with this. Either that or the binaries in the new package are given a different name to avoid conflicts. cgf
Re: ITP dos2unix 5.2.1-1
Christopher Faylor wrote: On Wed, Mar 16, 2011 at 04:05:17PM -0400, Charles Wilson wrote: On 3/16/2011 3:32 PM, Christopher Faylor wrote: On Wed, Mar 16, 2011 at 08:29:51PM +0100, Christian Franke wrote: An alternative would be to modify cygutils+dos2unix packages such that the user can select the flavor of dos2unix/unix2dos commands with /usr/sbin/alternatives. If cygutils is the default if installed this should not break anything. Except you would no longer be able to run dos2unix/unix2dos/d2u/u2d from a non-cygwin context, such as 'naked' cmd.exe or some IDE like Eclipse. Hey, good idea, assuming that Chuck is amenable. I'd be happy to just let the package in given that proviso if so. Uh, let's think about that a minute. cygutils is pulled in as part of Base (cygutils is not in the Base category, but it is required by a packages that is: cygwin-doc). Adding alternatives as a dep of cygutils would then make alternatives an implicit part of Base. alternatives itself brings in no other unsavory dependencies. This would be a change, since although alternatives is used by some very common packages [vim, automake], it's not in the default Base-only (actually, Base+requirements) installation. It also means that cygwin's dos2unix could no longer be executed from a non-cygwin context, because of the symlinks. ... Ah, right. I didn't get that Eric was referring to this scenario but, regardless, I should have remembered that alternatives means using symlinks. Given the use that d2u is put, I don't think we want to make it a symlink. Agree, symlinks should be avoided. Another alternative: Keep hard links as is if cygutils is installed only. If dos2unix is also installed assume that user opted-in to replace the dos2unix and unix2dos commands (and only these) with the linux variant. Undo this change if dos2unix is uninstalled. This may be possible to handle this in the postinstall/preremove scripts of both packages as follows (dos2unix case only, not tested): cygutils*.tar: remove dosunix2.exe but keep d2u.exe. dosunix*.tar: Install dos2unix.exe as e.g. dos2unix-linux.exe # /etc/postinstall/cygutils.sh: if cmp -s /usr/bin/dos2unix-linux.exe /usr/bin/dos2unix.exe; then :; else ln -f /usr/bin/conv.exe /usr/bin/dos2unix.exe fi # /etc/preremove/cygutils.sh: if cmp -s /usr/bin/conv.exe /usr/bin/dos2unix.exe; then rm -f /usr/bin/dos2unix.exe fi # /etc/postinstall/dos2unix.sh: ln -f /usr/bin/dos2unix-linux.exe /usr/bin/dos2unix.exe # /etc/preremove/dos2unix.sh: if cmp -s /usr/bin/dos2unix-linux.exe /usr/bin/dos2unix.exe; then if test -f /usr/bin/conv.exe; then ln -f /usr/bin/conv.exe /usr/bin/dos2unix.exe else rm -f /usr/bin/dos2unix.exe fi fi Christian
Re: ITP dos2unix 5.2.1-1
Moved to main cygwin list for more feedback.
Background: currently the following utilities
unix2dos
dos2unix
u2d
d2u
are all provided by the cygutils package. They are, in fact, all
hardlinks/copies of the same 'conv.exe' program, developed specifically
for cygwin.
We have a proposal to provide the dos2unix package instead, and
removing these utilities from cygutils. For more info, see:
http://cygwin.com/ml/cygwin-apps/2011-03/msg00067.html
and following.
On 3/16/2011 4:18 PM, Christopher Faylor wrote:
Ah, right.
I didn't get that Eric was referring to this scenario but, regardless,
I should have remembered that alternatives means using symlinks. Given
the use that d2u is put, I don't think we want to make it a symlink.
So, I guess that means that we poll the community if we want to go ahead
with this. Either that or the binaries in the new package are given a
different name to avoid conflicts.
Given that the unix2dos package supports pipe operation, the only real
difference is the command line options (and following symlinks on
converted files).
So, compare:
unix2dos 5.1.1 (2010-08-18)
Usage: unix2dos [-fhkLlqV] [-c convmode] [-o file ...] [-n infile
outfile ...]
-c --convmodeconversion mode
convmode ascii, 7bit, iso, mac, default to ascii
-f --force force conversion of all files
-h --helpgive this help
-k --keepdatekeep output file date
-L --license display software license
-l --newline add additional newline
-n --newfile write to new file
infile original file in new file mode
outfileoutput file in new file mode
-o --oldfile write to old file
file ... files to convert in old file mode
-q --quiet quiet mode, suppress all warnings
always on in stdio mode
-V --version display version number
vs.
unix2dos is part of cygutils version 1.4.4
converts the line endings of text files from
UNIX style (0x0a) to DOS style (0x0d 0x0a)
Usage: unix2dos [OPTION...] [input file list...]
Main options (not all may apply)
-A, --auto Output format will be the opposite of the autodetected
source
format
-D, --u2d Output will be in DOS format
--unix2dos Output will be in DOS format
-U, --d2u Output will be in UNIX format
--dos2unix Output will be in UNIX format
--forceIgnore binary file detection
--safe Do not modify binary files
Help options
-?, --help Show this help message
--usageDisplay brief usage message
--version Display version information
--license Display licensing information
Other arguments
[input file list...] for each file listed, convert in place.
If none specified, then use stdin/stdout
Now, of the cygutils options, we don't need
-D, --u2d, --unix2dos
-U, --d2u, --dos2unix
because...those really only apply to the generic 'conv.exe' application.
cygutils' unix2dos app is really only supposed to be used in, well,
unix2dos mode! So, unix2dos explicitly disallows the use of the
opposite options (--dos2unix etc) and --auto; similarly dos2unix:
if (progtype == CT_UNIX2DOS) {
if (opts.ConvType != CT_UNIX2DOS) {
fprintf(stderr,
%s: cannot accept any conversion type argument other\n \
Similarly, we don't need
-A, --auto
because, again, it really only makes sense for the generic conv.exe app
(and u2d/d2u/etc explicitly disallow its use).
All that leaves are the informational options (--help, -?, --usage,
--version, --license) which, if they go missing or renamed, I doubt that
will break any scripts.
Finally, we have
--forceIgnore binary file detection
--safe Do not modify binary files
All of cygutils' conversion progs operate in safe mode by default, so
the --safe option is a bit redundant (it was added so that if somebody
aliased unix2dos as 'unix2dos --force', they could override on the cmd
line using --safe if necessary).
The proposed package provides a similar --force option, but no --safe.
So, the only real issues are
1) somebody is (redundantly) specifying --safe
2) how does the unix2dos binary detection algorithm differ
from cygutils'?
3) Does the unix2dos package handle setmode() on stdio properly?
4) Ditto for O_BINARY on physical files?
5) cygutils always follows symlinks. This new package does not,
unless --force, according to the man page (which is
unfortunate: the same option means follow symlinks AND
convert everything even if you think it is binary
6) dos2unix foo.h foo.c (cygutils), but
Re: [ITP] gnucap-2009.12.07-1
Sorry setup.hint corrected in packages to: curr: 2009.12.07-1 prev: 0.35-1 category: Science requires: libgcc1 libreadline7 libstdc++6 termcap sdesc: Electronic circuit simulator backend ldesc: Gnucap is the Gnu Circuit Analysis Package. The primary component is a general purpose circuit simulator. It performs nonlinear dc and transient analyses, fourier analysis, and ac analysis. Spice compatible models for the MOSFET (level 1-8), BJT, and diode are included in this release. On 3/14/11 3:22 PM, Peter Li wrote: We discussed this a while back. It's in the standard distros. I pulled the version from cygports and bumped it up to the latest version. I'm also including the last versioned release (0.35) as prev. Version 0.35 is from 2006 and is missing many features, so it is preferable to have 2009.12.07 be the curr version. Hopefully I got the setup.hint files formatted correctly for curr and prev with cygports... curr (2009.12.07-1): wget -x -nH --cut-dirs=2 \ http://chichilnisky.salk.edu/peterli/cygwin/gnucap/gnucap-2009.12.07-1-src.tar.bz2 \ http://chichilnisky.salk.edu/peterli/cygwin/gnucap/gnucap-2009.12.07-1.tar.bz2 prev (0.35): wget -x -nH --cut-dirs=2 \ http://chichilnisky.salk.edu/peterli/cygwin/gnucap/gnucap-0.35-1-src.tar.bz2 \ http://chichilnisky.salk.edu/peterli/cygwin/gnucap/gnucap-0.35-1.tar.bz2 setup.hint (cygport format): curr: 2009.12.07 prev: 0.35 category: Science requires: libgcc1 libreadline7 libstdc++6 termcap sdesc: Electronic circuit simulator backend ldesc: Gnucap is the Gnu Circuit Analysis Package. The primary component is a general purpose circuit simulator. It performs nonlinear dc and transient analyses, fourier analysis, and ac analysis. Spice compatible models for the MOSFET (level 1-8), BJT, and diode are included in this release.
[RFU] serf-0.7.1-1
Please leave 0.3.1-1 and 0.7.0-1 as previous versions. Any older versions may be removed. None of the setup.hint files were updated. Thanks! wget -x -nH --cut-dirs=2 \ http://home.comcast.net/~david.rothenberger/cygwin/serf/libserf0-devel/libserf0-devel-0.7.1-1.tar.bz2 \ http://home.comcast.net/~david.rothenberger/cygwin/serf/libserf0_1/libserf0_1-0.7.1-1.tar.bz2 \ http://home.comcast.net/~david.rothenberger/cygwin/serf/serf-0.7.1-1-src.tar.bz2 \ http://home.comcast.net/~david.rothenberger/cygwin/serf/serf-0.7.1-1.tar.bz2 -- David Rothenberger daver...@acm.org Spock, did you see the looks on their faces? Yes, Captain, a sort of vacant contentment.
[RFU] subversion-1.6.15-1
Please delete 1.6.13-1 and leave 1.6.15-1 as the previous version. There were no setup.hint changes. Thanks! wget -x -nH --cut-dirs=2 \ http://home.comcast.net/~david.rothenberger/cygwin/subversion/subversion-1.6.16-1-src.tar.bz2 \ http://home.comcast.net/~david.rothenberger/cygwin/subversion/subversion-1.6.16-1.tar.bz2 \ http://home.comcast.net/~david.rothenberger/cygwin/subversion/subversion-apache2/subversion-apache2-1.6.16-1.tar.bz2 \ http://home.comcast.net/~david.rothenberger/cygwin/subversion/subversion-devel/subversion-devel-1.6.16-1.tar.bz2 \ http://home.comcast.net/~david.rothenberger/cygwin/subversion/subversion-perl/subversion-perl-1.6.16-1.tar.bz2 \ http://home.comcast.net/~david.rothenberger/cygwin/subversion/subversion-python/subversion-python-1.6.16-1.tar.bz2 \ http://home.comcast.net/~david.rothenberger/cygwin/subversion/subversion-ruby/subversion-ruby-1.6.16-1.tar.bz2 \ http://home.comcast.net/~david.rothenberger/cygwin/subversion/subversion-tools/subversion-tools-1.6.16-1.tar.bz2 -- David Rothenberger daver...@acm.org Life begins when you can spend your spare time programming instead of watching television. -- Cal Keegan
[ RFU ] base-files-4.0-5
Hello, Please upload base-files-4.0-5. It contains a bugfix to correct the PRINTER setting in /etc/profile. http://crapsteak.org/cygwin/release/base-files/base-files-4.0-5.tar.bz2 http://crapsteak.org/cygwin/release/base-files/base-files-4.0-5.tar.bz2.sig My apologies for the misleading message to the main list, as well as not properly requesting a RFU. Thanks. -- Huella de clave primaria: 0FDA C36F F110 54F4 D42B D0EB 617D 396C 448B 31EB signature.asc Description: Digital signature
Re: [ RFU ] base-files-4.0-5
On Thu, Mar 17, 2011 at 12:38:52AM +0100, David Sastre wrote: Please upload base-files-4.0-5. It contains a bugfix to correct the PRINTER setting in /etc/profile. http://crapsteak.org/cygwin/release/base-files/base-files-4.0-5.tar.bz2 http://crapsteak.org/cygwin/release/base-files/base-files-4.0-5.tar.bz2.sig .bz2 uploaded. My apologies for the misleading message to the main list, as well as not properly requesting a RFU. Don't worry about it. Thanks again for taking this package on. cgf
src/winsup/cygwin cygtls.h tlsoffsets.h syslog ...
CVSROOT:/cvs/src Module name:src Branch: cv-post-1_7_9 Changes by: cori...@sourceware.org 2011-03-16 12:20:18 Modified files: winsup/cygwin : cygtls.h tlsoffsets.h syslog.cc ChangeLog Log message: * cygtls.h (struct _local_storage): Redefine process_ident as wchar_t pointer. * syslog.cc (CYGWIN_LOG_NAME): Convert to wide char constant. (openlog): Convert incoming ident string to wide char. Fix formatting. (vsyslog): Print ident string as wide char string. Convert message string to wide char and call UNICODE Win32 Event functions to make sure to use correct codeset. * tlsoffset.h: Regenerate. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/cygtls.h.diff?cvsroot=srconly_with_tag=cv-post-1_7_9r1=1.66r2=1.66.2.1 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/tlsoffsets.h.diff?cvsroot=srconly_with_tag=cv-post-1_7_9r1=1.42r2=1.42.2.1 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/syslog.cc.diff?cvsroot=srconly_with_tag=cv-post-1_7_9r1=1.48r2=1.48.4.1 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/ChangeLog.diff?cvsroot=srconly_with_tag=cv-post-1_7_9r1=1.5189.2.13r2=1.5189.2.14
src/winsup/cygwin ChangeLog winver.rc
CVSROOT:/cvs/src Module name:src Changes by: cori...@sourceware.org 2011-03-16 21:10:51 Modified files: winsup/cygwin : ChangeLog winver.rc Log message: * winver.rc: Fix copyright dates. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/ChangeLog.diff?cvsroot=srcr1=1.5191r2=1.5192 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/winver.rc.diff?cvsroot=srcr1=1.8r2=1.9
src/winsup/cygwin ChangeLog winver.rc
CVSROOT:/cvs/src Module name:src Branch: cv-post-1_7_9 Changes by: cori...@sourceware.org 2011-03-16 21:11:50 Modified files: winsup/cygwin : ChangeLog winver.rc Log message: * winver.rc: Fix copyright dates. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/ChangeLog.diff?cvsroot=srconly_with_tag=cv-post-1_7_9r1=1.5189.2.14r2=1.5189.2.15 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/winver.rc.diff?cvsroot=srconly_with_tag=cv-post-1_7_9r1=1.8r2=1.8.6.1
Re: [PATCH] Add an additional relocation attempt pass to load_after_fork()
On 15/03/2011 23:37, Yaakov (Cygwin/X) wrote: On Sun, 2011-03-13 at 15:07 +, Jon TURNEY wrote: Attached is a patch which avoids a fork failure due to remap error in the specific circumstances described in my email [1], by adding an additional pass to load_after_fork() which forces the DLL to be relocated by VirtualAlloc()ing a block of memory at the load address as well. Hopefully it can be seen by inspection that this code doesn't change the behaviour of the first two passes, and so will only be changing the behaviour in what was an fatal error case before. This patch causes a warning with GCC 4.5: cc1plus: warnings being treated as errors dll_init.cc: In member function ‘void dll_list::load_after_fork(void*)’: dll_init.cc:328:33: error: converting to non-pointer type ‘DWORD’ from NULL Thanks, I guess that should be a 0 instead.
Bash/wget gets confused by trailing carriage return
I'm sorry if this appears twice. I'm posting it again because I did not see it appear. I have the following script that does not work! #!/usr/bin/bash /usr/bin/wget ftp://mirrors.kernel.org/debian-cd/6.0.0/i386/iso-dvd/debian-6.0.0-i386-DVD-2.iso when I type bash.exe -v it says version 3.9-3 Here are the results: --2011-03-14 16:52:30-- ftp://mirrors.kernel.org/debian-cd/6.0.0/i386/iso-dvd/debian-6.0.0-i386-DVD-2.iso%0D = `debian-6.0.0-i386-DVD-2.iso%0D' Resolving mirrors.kernel.org (mirrors.kernel.org)... 149.20.4.71, 149.20.20.135 Connecting to mirrors.kernel.org (mirrors.kernel.org)|149.20.4.71|:21... connected. Logging in as anonymous ... Logged in! == SYST ... done. == PWD ... done. == TYPE I ... done. == CWD (1) /debian-cd/6.0.0/i386/iso-dvd ... done. == SIZE debian-6.0.0-i386-DVD-2.iso\r ... done. == PASV ... done. == RETR debian-6.0.0-i386-DVD-2.iso\r ... No such file `debian-6.0.0-i386-DVD-2.iso\r'. Process compilation exited abnormally with code 8 It appears to be appending the carriage return on the end of the file name. Perhaps the C runtime is getting confused. How do I fix this? Thanks, Siegfried -- 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: Bash/wget gets confused by trailing carriage return
On 2011-03-16 06:42Z, siegfr...@deleted.com wrote: #!/usr/bin/bash /usr/bin/wget ftp://mirrors.kernel.org/debian-cd/6.0.0/i386/iso-dvd/debian-6.0.0-i386-DVD-2.iso [...] == SIZE debian-6.0.0-i386-DVD-2.iso\r ... done. == PASV ... done. == RETR debian-6.0.0-i386-DVD-2.iso\r ... No such file `debian-6.0.0-i386-DVD-2.iso\r'. Have you ruled out the possibility that your script contains '\r'? This od -t a my_script.sh |grep cr would detect its presence, and 'd2u' would remove it. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: How do I add a follow-on post to a thread in this mailing list?
Peter Binney writes: [..no http://cygwin.com/acronyms/#TOFU today please, reformatted..] But that reply has not appeared (though I got no delivery error message). You might be able to save the Raw text version to disk and open it within your email client. Click reply and the correct headers will be included. Many thanks - I'm using gmail. Any idea how I would do that with it? Also, is there no way then to join into a thread unless one has access to a mail from the mailing list? I can't answer your gmail question. But here's an alternative: read the list and write followups using gmane. See http://news.gmane.org/gmane.os.cygwin. I actually do something a little different: read the list using the archives http://cygwin.com/ml/cygwin/ but use gmane to followup. HTH, ..mark -- You never know what is enough until you know what is more than enough. -- William Blake -- 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: Calling sem_wait() in DllMain( DLL_THREAD_DETACH) crashes
On Mar 15 20:50, Jon TURNEY wrote: I did read through the UG looking for a statement like that, but the only thing I found was the caveat about mixing POSIX and Win32 calls to set cwd. Perhaps I overlooked something, or maybe it would be good if that was more clearly documented. However, it does seem that python (or one of its extensions) is doing something it shouldn't. Given the above clarification about cygwin, this is a bug in libcrypto from OpenSSL (which tries to be portable to more than just POSIX, and has a DllMain() which is built for both cygwin and Win32), and a patch like that at [1] (or perhaps one which avoids DllMain on cygwin entirely) should be applied. Thanks for the information. I will look into getting rid of DllMain. Just like in libiconv, there's no good reason to use this function in a shared lib for Cygwin. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: mtr compilation problem
On Mar 15 22:07, Olivier Lefevre wrote: I am trying to compile mtr-0.80. configure completed without errors but make puts: net.h:25:25: error: netinet/ip6.h: No such file or directory net.h:26:27: error: netinet/icmp6.h: No such file or directory I couldn't find what additional packages I should download to get IPv6 headers (which I assume are IPv6). These headers don't exist in Cygwin. IPv6 works, but only if you use the standard headers like netinet/in.h or netinet/ip.h. The in6.h and icmp6.h headers define internals of the V6 packet structure which are usually not available to the application. You can't use the ping functionality of mtr on Cygwin as a normal user anyway, given restrictions in the usage of RAW sockets in Windows. Still, if you think you can make use of the tool anyway, try to fetch the netinet/ip6.h and netinet/icmp6.h headers from FreeBSD. Both headers are pretty much self-contained, except for the usage of some base types like u_int_16, etc., which are defined in sys/types.h anyway. And most of the structures and macros defined in these files should be only protocol dependent, not system dependent. No guarantees here, though. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated: mingw64-x86_64-gcc-4.5.2-1
Version 4.5.2-1 of mingw64-x86_64-gcc has been uploaded. mingw64-x86_64-gcc contains GCC for the MinGW-w64 Win64 toolchain. mingw64-x86_64-gcc has been rebuilt with the new runtime and headers. *** 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. -- 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-x86_64-binutils-2.21.51-1
Version 2.21.51-1 of mingw64-x86_64-binutils have been uploaded. mingw64-x86_64-binutils contains Binutils for the MinGW-w64 Win64 toolchain. *** 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. -- 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-x86_64-runtime-1.0b_svn4075-1
Version 1.0b_svn4075-1 of mingw64-x86_64-runtime has been uploaded. mingw64-x86_64-runtime provides library to interface with Windows. This package is specifically for the 64bit target toolchain. *** 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. 0xED74C077.asc Description: application/pgp-keys -- 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: How do I add a follow-on post to a thread in this mailing list?
On Tue, 15 Mar 2011 21:33:11 + Peter Binney peter.bin...@gmail.com wrote: Many thanks - I'm using gmail. Any idea how I would do that with it? You should be able to import the mail via Settings - Accounts and Import. Or, access the IMAP interface and copy the email over. -- Bruce Cran -- 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: SSHD [Windows Domain Controller]: fatal: chown(/dev/tty0, 500, 513) failed: Bad file descriptor.
Corina, Please, can you dump the group policy settings of you test envirioment for compare with my group policy settings? Thanks. 2011/3/7 Corinna Vinschen On Mar 6 12:03, Bruno Galindro da Costa wrote: Corinna, The Administradores group is a local group used only by the DomainControllers. suntech-adm is the user that is the Domain Admin - like root account on Unix systems. This information might be helpful for the analisys... Did you tried to reproduce this issue in a Domain Controller? Yes, I tried it on a 2K8 domain controller. Works fine for me, unless I try to login as a non-admin user, but that's to be expected. Bellow is the output of cygcheck: Cygwin Configuration Diagnostics Current System Time: Fri Mar 04 15:58:09 2011 Windows 2003 Server R2 Enterprise Edition Ver 5.2 Build 3790 Service Pack 2 Running in Terminal Service session Oh boy, a terminal server again. I'm wondering if we got yet another problem with terminal servers. However, given that the service is running in session 0, it would be very strange. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple -- Att. Bruno Galindro da Costa -- 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: mtr compilation problem
OK, I'll try. Thanks a lot. Re. raw sockets and the need for elevated privilege, can't you use the RunAs trick to get around it? -- O.L. -- 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: SSHD [Windows Domain Controller]: fatal: chown(/dev/tty0, 500, 513) failed: Bad file descriptor. [SOLVED]
Corina, my problem was solved!! I´ve only added the cyg_server user to Admins do Dominio domain group. This group is used by all domain admins and is a domain group, not a local group like Administradores. Thank you! 2011/3/16 Bruno Galindro da Costa bruno.galin...@gmail.com: Corina, Please, can you dump the group policy settings of you test envirioment for compare with my group policy settings? Thanks. 2011/3/7 Corinna Vinschen On Mar 6 12:03, Bruno Galindro da Costa wrote: Corinna, The Administradores group is a local group used only by the DomainControllers. suntech-adm is the user that is the Domain Admin - like root account on Unix systems. This information might be helpful for the analisys... Did you tried to reproduce this issue in a Domain Controller? Yes, I tried it on a 2K8 domain controller. Works fine for me, unless I try to login as a non-admin user, but that's to be expected. Bellow is the output of cygcheck: Cygwin Configuration Diagnostics Current System Time: Fri Mar 04 15:58:09 2011 Windows 2003 Server R2 Enterprise Edition Ver 5.2 Build 3790 Service Pack 2 Running in Terminal Service session Oh boy, a terminal server again. I'm wondering if we got yet another problem with terminal servers. However, given that the service is running in session 0, it would be very strange. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple -- Att. Bruno Galindro da Costa -- Att. Bruno Galindro da Costa -- 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: mtr compilation problem
On 3/16/2011 10:59 AM, Olivier Lefevre wrote: Re. raw sockets and the need for elevated privilege, can't you use the RunAs trick to get around it? Maybe. Or you could recode the underlying implementation to use, instead of the cygwin/posix socket interface, the Win32 ICMP dll services, just like MS's own ping and tracert executables -- at least, when #if defined _WIN32 || defined __CYGWIN__ This allows to send ICMP packets as a regular user, but you don't have as much flexibility in composing those packets (you can't set TTL, for instance). This is what FPing does (http://www.kwakkelflap.com/fping.html, not to be confused with http://fping.sourceforge.net/). However, FPing is free-as-in-beer, but not free-as-in-speech (no source available). The ICMP dll interface is technically undocumented for desktop systems, but MS does provide documentation for the WinCE implementations. It is likely that the interface is the same. ICMP Reference Windows CE .NET http://msdn.microsoft.com/en-us/library/ms907315.aspx I found this page: http://www.sockets.com/ms_icmp.htm which provides ms_icmp.h: ICMP API declarations, but apparently derived from the documentation, not the MS SDK header. Also (re)defines various constants (which cygwin w32api provides in ipinfoid.h). No copyright information on this file -- but that's ok, it can be completely re-written using the docu reference above. ms_icmp.c: implements 'ping' and 'traceroute' using these functions. Copyright by Bob Quinn, 1997 but with no associated license information. You'll need to contact Bob directly (contact info at the webpage) for explicit licensing info, if you want to use his source code as the basis for a patch to mtr. There are other references out there for using ICMP API, some with explicit licensing info http://tangentsoft.net/wskfaq/examples/dllping.html explicitly placed in the public domain http://serious-code.net/moin.cgi/ICMP seems to be a c++ wrapper around the sockets.com impl no licensing info http://www.hackchina.com/en/r/13544/pingi.c__html no licensing info but they all either assume you are using the Windows SDK IcmpAPI.h, or provide their own declarations of the functions/structs without saying how they determined what they were (did they copy from IcmpAPI.h?). So, in order to use /those/ implementations as a basis for developing a patch for mtr, you'll need to get the ICMP API stuff integrated into cygwin's w32api using the procedure below. = FYI: IcmpAPI.h from the windows SDK has no corresponding element in cygwin's w32api. To correct this, one would need to propose a patch upstream to mingw-users AT lists DOT sourceforge DOT net...and be prepared to show that your patch derives from http://msdn.com/ and NOT from I looked at the MS Windows SDK IcmpAPI.h file and... That's why I gave the direct msdn link, above. = I also found this, applicable for receiving unfiltered packets (e.g. Destination Unreachable, or TTL Expired) on Vista+ http://www.okob.net/wp/index.php/2009/04/30/icmp-over-raw-sockets-under-windows-vista/ but that doesn't help for sending raw packets. It uses a couple of constants in a WSAIoctl() call [RCVALL_IPLEVEL, SIO_RCVALL] which are not currently defined in cygwin's w32api. These are documented here http://msdn.microsoft.com/en-us/library/ee309610%28v=vs.85%29.aspx but unfortunately does not define the actual numerical VALUES. Sigh. === -- Chuck -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: mtr compilation problem
Olivier Lefevre lefevrol at yahoo.com writes: Re. raw sockets and the need for elevated privilege, can't you use the RunAs trick to get around it? Also on Unix/Linux a raw socket cannot be used by a normal user. But the ping program is setuid root and thus can be called by any user. Unfortunatly there is no such mechanism in cygwin. Regards kf -- 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: LS and TAR don't see any file permissions (
Eric Blake eblake at redhat.com writes: On 03/04/2011 11:12 AM, Peter Binney wrote: When running ls -l the permissions field shows as --+. Which means that the owner has no permissions, but that there are ACLs which allow others permissions. Not entirely unusual, given Windows' ability to create files with a different owner than the current user, while allowing the current user to access the file (typically when done to places like the desktop, and caused by inheritance ACLs present on the directory where the problematic file is being created in the first place). Oddly, ls -l shows the correct permissions if the pathname uses the windows drive letter syntax. eg: $ pwd /cygdrive/c $ ls -l tmp/plb.txt --+ 1 ga2binn Domain Users 5527 Mar 3 13:54 tmp/plb.txt $ ls -l c:/tmp/plb.txt -rw-r--r-- 1 ga2binn Domain Users 5527 Mar 3 13:54 c:/tmp/plb.txt That's because using a dos-style path disregards ACL parsing, and fakes the permission bits instead. The + shows that ACLs are present, and 'getfacl tmp/plb.txt' will show you the difference between the owner and your permissions. Similarly, TAR images have no permissions on the files contained. eg: $ pwd /cygdrive/c/tmp $ tar cf - plb.txt | tar vtf - -- ga2binn/Domain Users 5527 2011-03-03 13:54 plb.txt Here, the problem is that tar doesn't preserve ACLs by default, so the original POSIX mode (000) is preserved while the ACLs are lost, resulting in an truly inaccessible file (note that there is no longer a + in the listing). Even more oddly, this behaviour (both LS and TAR) occurs on a new PC that I am moving to. That's another big case where the user ids on the old pc do not correpsond to the user ids on the new pc; copying preserved the old user id, but gave ACL access to the new user, resulting in odd permissions. Many thanks indeed for that info, Eric. I know it's not a Cygwin issue, but can you suggest an easy way to get miserable Windows to copy files to a new machine in a way that does give the current user ownership (ideally using some normal-ish Windows commands)? I tried using Windows Explorer copies and Winzip-ed .zip archives - both end up with the problem below. I have done this before when transferring PC's, but then I would have been the same user on both, Here I am also moving to a different domain\username on the new PC. -- 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: How do I add a follow-on post to a thread in this mailing list?
Many thanks indeed Mark - GMANE was prefect - so much easier than mucking around with raw mail messages. On 16 March 2011 07:11, Mark Geisert m...@maxrnd.com wrote: Peter Binney writes: [..no http://cygwin.com/acronyms/#TOFU today please, reformatted..] But that reply has not appeared (though I got no delivery error message). You might be able to save the Raw text version to disk and open it within your email client. Click reply and the correct headers will be included. Many thanks - I'm using gmail. Any idea how I would do that with it? Also, is there no way then to join into a thread unless one has access to a mail from the mailing list? I can't answer your gmail question. But here's an alternative: read the list and write followups using gmane. See http://news.gmane.org/gmane.os.cygwin. I actually do something a little different: read the list using the archives http://cygwin.com/ml/cygwin/ but use gmane to followup. HTH, ..mark -- You never know what is enough until you know what is more than enough. -- William Blake -- 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: BLODA detection (was Re: Debugging help for fork failure: resource temporarily unavailable)
On 2:59 PM, Henry S. Thompson wrote: Ryan Johnson writes: BTW, I found a good way to identify, if not fix, BLODA: given an app which loads no libraries at runtime -- such as 'ls' -- any dlls mentioned in /proc/$$/maps which cygcheck does not mention are probably dodgy. In my case, Windows Live (which I didn't think was even installed on my machine) has injected a WLIDNSP.DLL (Microsoft Windows Live ID Namespace Provider) in all my processes. This would be super-cool if true, but it doesn't work for me. . . If I try, I find C:\Windows\system32\ntmarta.dll C:\Windows\SysWOW64\sechost.dll C:\Windows\syswow64\WLDAP32.dll in /proc/[ls procid]/maps but not in cygcheck output, but none of those are BLODA, right? [Note also that maps shows many things in syswow64 which cygcheck shows in system32, but presumably that's because cygcheck itself is a 32-bit app, is it?] Interesting... $ join -i -v 1 (cat /proc/$$/maps | sed 's;^.*/;;' | sort -f) (cygcheck $(cat /proc/$$/winexename) | sed 's;^.*\\;;' | sort -f) apphelp.dll DNSAPI.dll IMM32.DLL MSCTF.dll mswsock.dll napinsp.dll NLAapi.dll NSI.dll pnrpnsp.dll PSAPI.DLL sechost.dll SHLWAPI.dll winmm.dll winrnr.dll WLIDNSP.DLL ws2_32.dll wshbth.dll The above shows all dlls loaded by the process which are not linked in at compile time. Does bash really load so many dynamic libraries, or is cygcheck missing things? Ryan -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Calling sem_wait() in DllMain( DLL_THREAD_DETACH) crashes
On Mar 16 11:00, Corinna Vinschen wrote: On Mar 15 20:50, Jon TURNEY wrote: I did read through the UG looking for a statement like that, but the only thing I found was the caveat about mixing POSIX and Win32 calls to set cwd. Perhaps I overlooked something, or maybe it would be good if that was more clearly documented. However, it does seem that python (or one of its extensions) is doing something it shouldn't. Given the above clarification about cygwin, this is a bug in libcrypto from OpenSSL (which tries to be portable to more than just POSIX, and has a DllMain() which is built for both cygwin and Win32), and a patch like that at [1] (or perhaps one which avoids DllMain on cygwin entirely) should be applied. Thanks for the information. I will look into getting rid of DllMain. Just like in libiconv, there's no good reason to use this function in a shared lib for Cygwin. Well, I have to take that back. The DLL_PROCESS_ATTACH case in openssl's DllMain function is important to maintain FIPS compatibility. So it seems the right thing to do is to remove the ERR_remove_state() call in the DLL_THREAD_DETACH case. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated: openssl-0.9.8r-2, openssl-devel-0.9.8r-2, libopenssl098-0.9.8r-2
I've updated the version of OpenSSL to 0.9.8r-2. This is a minor bugfix release, which contains a patch for a Cygwin specific issue. For details see http://cygwin.com/ml/cygwin/2011-03/msg00437.html To update your installation, click on the Install Cygwin now link on the http://cygwin.com/ web page. This downloads setup.exe to your system. Then, run setup and answer all of the questions. *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@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 the above URL. -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: ITP dos2unix 5.2.1-1
Moved to main cygwin list for more feedback.
Background: currently the following utilities
unix2dos
dos2unix
u2d
d2u
are all provided by the cygutils package. They are, in fact, all
hardlinks/copies of the same 'conv.exe' program, developed specifically
for cygwin.
We have a proposal to provide the dos2unix package instead, and
removing these utilities from cygutils. For more info, see:
http://cygwin.com/ml/cygwin-apps/2011-03/msg00067.html
and following.
On 3/16/2011 4:18 PM, Christopher Faylor wrote:
Ah, right.
I didn't get that Eric was referring to this scenario but, regardless,
I should have remembered that alternatives means using symlinks. Given
the use that d2u is put, I don't think we want to make it a symlink.
So, I guess that means that we poll the community if we want to go ahead
with this. Either that or the binaries in the new package are given a
different name to avoid conflicts.
Given that the unix2dos package supports pipe operation, the only real
difference is the command line options (and following symlinks on
converted files).
So, compare:
unix2dos 5.1.1 (2010-08-18)
Usage: unix2dos [-fhkLlqV] [-c convmode] [-o file ...] [-n infile
outfile ...]
-c --convmodeconversion mode
convmode ascii, 7bit, iso, mac, default to ascii
-f --force force conversion of all files
-h --helpgive this help
-k --keepdatekeep output file date
-L --license display software license
-l --newline add additional newline
-n --newfile write to new file
infile original file in new file mode
outfileoutput file in new file mode
-o --oldfile write to old file
file ... files to convert in old file mode
-q --quiet quiet mode, suppress all warnings
always on in stdio mode
-V --version display version number
vs.
unix2dos is part of cygutils version 1.4.4
converts the line endings of text files from
UNIX style (0x0a) to DOS style (0x0d 0x0a)
Usage: unix2dos [OPTION...] [input file list...]
Main options (not all may apply)
-A, --auto Output format will be the opposite of the autodetected
source
format
-D, --u2d Output will be in DOS format
--unix2dos Output will be in DOS format
-U, --d2u Output will be in UNIX format
--dos2unix Output will be in UNIX format
--forceIgnore binary file detection
--safe Do not modify binary files
Help options
-?, --help Show this help message
--usageDisplay brief usage message
--version Display version information
--license Display licensing information
Other arguments
[input file list...] for each file listed, convert in place.
If none specified, then use stdin/stdout
Now, of the cygutils options, we don't need
-D, --u2d, --unix2dos
-U, --d2u, --dos2unix
because...those really only apply to the generic 'conv.exe' application.
cygutils' unix2dos app is really only supposed to be used in, well,
unix2dos mode! So, unix2dos explicitly disallows the use of the
opposite options (--dos2unix etc) and --auto; similarly dos2unix:
if (progtype == CT_UNIX2DOS) {
if (opts.ConvType != CT_UNIX2DOS) {
fprintf(stderr,
%s: cannot accept any conversion type argument other\n \
Similarly, we don't need
-A, --auto
because, again, it really only makes sense for the generic conv.exe app
(and u2d/d2u/etc explicitly disallow its use).
All that leaves are the informational options (--help, -?, --usage,
--version, --license) which, if they go missing or renamed, I doubt that
will break any scripts.
Finally, we have
--forceIgnore binary file detection
--safe Do not modify binary files
All of cygutils' conversion progs operate in safe mode by default, so
the --safe option is a bit redundant (it was added so that if somebody
aliased unix2dos as 'unix2dos --force', they could override on the cmd
line using --safe if necessary).
The proposed package provides a similar --force option, but no --safe.
So, the only real issues are
1) somebody is (redundantly) specifying --safe
2) how does the unix2dos binary detection algorithm differ
from cygutils'?
3) Does the unix2dos package handle setmode() on stdio properly?
4) Ditto for O_BINARY on physical files?
5) cygutils always follows symlinks. This new package does not,
unless --force, according to the man page (which is
unfortunate: the same option means follow symlinks AND
convert everything even if you think it is binary
6) dos2unix foo.h foo.c (cygutils), but
Re: [ANNOUNCEMENT] Updated: base-files-4.0-4
On Mon, Mar 14, 2011 at 10:30:59PM +0100, David Sastre wrote: On Mon, Mar 14, 2011 at 12:14:19PM +0100, Corinna Vinschen wrote: Hi David, I was just testing some experimental Cygwin code on Windows 2000. I now get this on every invocation of the shell: bash: /proc/registry/HKEY_CURRENT_USER/Software/Microsoft/Windows NT/ CurrentVersion/Windows/Device: No such file or directory In fact there is no Device value. I guess /etc/profile should check the file for existence before trying to read it. Indeed. Thanks for catching it. I've made a 4.0-5 release available to correct that: http://crapsteak.org/cygwin/release/base-files/base-files-4.0-5.tar.bz2 http://crapsteak.org/cygwin/release/base-files/base-files-4.0-5.tar.bz2.sig Sorry, wrong list. Please wait until 4.0-5 is properly released and announced to install it using setup.exe. My apologies for the misleading message above. It wasn't intended to reach this list. -- Huella de clave primaria: 0FDA C36F F110 54F4 D42B D0EB 617D 396C 448B 31EB signature.asc Description: Digital signature
Re: /etc/profile optimization and correctness
On Wed, Mar 16, 2011 at 07:31:28PM +1100, Brian Ha wrote:
Your fix:
# Zero forks
read -r PRINTER
'/proc/registry/HKEY_CURRENT_USER/Software/Microsoft/Windows
NT/CurrentVersion/Windows/Device'
export PRINTER=${PRINTER%%,*}
Broke my install:
bash: /proc/registry/HKEY_CURRENT_USER/Software/Microsoft/Windows
NT/CurrentVers ion/Windows/Device: No such file or directory
I have no printer installed or printspooler service running.
Hello,
Please address all questions regarding cygwin packages to the cygwin
maillist, not to the maintainers.
A fix for that problem will be included in base-files-4.0-5.
If you don't want to wait, and knowing you don't have a printer
installed, you can comment those lines in /etc/profile to stop seeing
the warning message.
--
Huella de clave primaria: 0FDA C36F F110 54F4 D42B D0EB 617D 396C 448B 31EB
signature.asc
Description: Digital signature
Re: [ANNOUNCEMENT] Updated: base-files-4.0-4
David Sastre d.sastre.med...@gmail.com wrote in message news:20110314203139.ga9...@jethro.local.lan... On Mon, Mar 14, 2011 at 10:42:03AM -0700, Matt Seitz (matseitz) wrote: In the future, would you make available a list of changes that does not require first installing the package? I like to look at the list of changes before upgrading a package. Absolutely. Here it is in case it is still useful for you or others: Thank you very much! -- 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
