Re: ITP dos2unix 5.2.1-1
On Wed, 2011-03-16 at 17:38 -0400, Charles Wilson wrote: So: I don't see any insurmountable problems with entirely replacing cygutils' unix2dos/dos2unix/u2d/d2u programs with these other versions. (I would hope that cygwin's package would provide a u2d.exe hardlinked to unix2dos.exe, etc) +1 Yaakov
Re: [RFU] serf-0.7.1-1
On Mar 16 15:58, David Rothenberger wrote: 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 Uploaded. Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: [RFU] subversion-1.6.15-1
On Mar 16 16:02, David Rothenberger wrote: 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 Uplaoded and 1.6.13-1 removed. Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: ITP dos2unix 5.2.1-1
On 03/16/2011 10:38 PM, Charles Wilson wrote:
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
That is an old version. Here is the latest:
dos2unix 5.2.1 (2011-03-04)
Usage: dos2unix [options] [file ...] [-n infile outfile ...]
-ascii convert only line breaks (default)
-iso conversion between DOS and ISO-8859-1 character set
-1252 Use Windows code page 1252 (Western European)
-437 Use DOS code page 437 (US) (default)
-850 Use DOS code page 850 (Western European)
-860 Use DOS code page 860 (Portuguese)
-863 Use DOS code page 863 (French Canadian)
-865 Use DOS code page 865 (Nordic)
-7 Convert 8 bit characters to 7 bit space
-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
Re: [ITP] gnucap-2009.12.07-1
Please don't http://cygwin.com/acronyms/#TOFU On Mar 16 14:44, Peter Li wrote: 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 Packaging looks good. Given that this package is new anyway, there's no reason to provide an old version. Therefore I only uploaded 2009.12.07-1 and removed the curr and prev lines from your setup.hint. Thanks for this new package. Please send an announcement to the cygwin-announce list per http://cygwin.com/setup.html#submitting Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: [ITP] gnucap-2009.12.07-1
On 3/17/2011 2:07 AM, Corinna Vinschen wrote: Packaging looks good. Great! Given that this package is new anyway, there's no reason to provide an old version. Therefore I only uploaded 2009.12.07-1 and removed the curr and prev lines from your setup.hint. I believe 2009.12.07 to be quite stable, but I thought it might be good to include 0.35 as a backup. In addition the 0.35 package includes a (still relevant) documentation PDF that is absent in the 2009.12.07 package. I could try to add this PDF into 2009.12.07-2? Best, Peter
Re: [ITP] gnucap-2009.12.07-1
On Mar 17 02:17, Peter Li wrote: On 3/17/2011 2:07 AM, Corinna Vinschen wrote: Packaging looks good. Great! Given that this package is new anyway, there's no reason to provide an old version. Therefore I only uploaded 2009.12.07-1 and removed the curr and prev lines from your setup.hint. I believe 2009.12.07 to be quite stable, but I thought it might be good to include 0.35 as a backup. In addition the 0.35 package includes a (still relevant) documentation PDF that is absent in the 2009.12.07 package. I could try to add this PDF into 2009.12.07-2? That would be better. Given that you have usually only one version of a package installed, the user would otherwise have the choice of installing the old package and get the PDF doc, or installing the current package and not have it. That doesn't sound very satisfying for a user. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: [ITP] gnucap-2009.12.07-1
On 3/17/2011 3:34 AM, Corinna Vinschen wrote: On Mar 17 02:17, Peter Li wrote: I believe 2009.12.07 to be quite stable, but I thought it might be good to include 0.35 as a backup. In addition the 0.35 package includes a (still relevant) documentation PDF that is absent in the 2009.12.07 package. I could try to add this PDF into 2009.12.07-2? That would be better. Given that you have usually only one version of a package installed, the user would otherwise have the choice of installing the old package and get the PDF doc, or installing the current package and not have it. That doesn't sound very satisfying for a user. Agreed! I wasn't sure how much doctoring of the package is a good idea; I have a notion that we wouldn't want a Cygwin package to behave too differently from the original due to cobbling versions or other tweaks. But in any case this is not that level of tweaking at all. Thanks! P
RFU: mercurial-1.8.1-1
New upstream release: wget --recursive --no-host-directories --cut-dirs=3 \ http://cante.net/~jaalto/tmp/cygwin/mercurial/mercurial-1.8.1-1-src.tar.bz2 \ http://cante.net/~jaalto/tmp/cygwin/mercurial/mercurial-1.8.1-1.tar.bz2 \ http://cante.net/~jaalto/tmp/cygwin/mercurial/setup.hint Jari
RFU: bzr-2.3.1-1
New upstream release: wget --recursive --no-host-directories --cut-dirs=3 \ http://cante.net/~jaalto/tmp/cygwin/bzr/bzr-2.3.1-1-src.tar.bz2 \ http://cante.net/~jaalto/tmp/cygwin/bzr/bzr-2.3.1-1.tar.bz2 \ http://cante.net/~jaalto/tmp/cygwin/bzr/setup.hint Jari
[RFC] Making Cygwin README optional
I wish to propose that Cygwin READMEs no longer be absolutely required for Cygwin packages, for several reasons: * None of the major distros require a distro-specific documentation file. * Many packages, particularly those higher up the stack, just work on Cygwin, so there's really not much Cygwin-specific to say. * Most of the information contained therein is duplicated elsewhere: - the package description is in setup.int - runtime deps are handled by setup; - rebuild instructions for cygport-based packages are already covered in cygport's documentation, and in any case, how to rebuild the source package is not really relevant to the *binary* package; - the package contents are available through cygcheck; - changes in the latest release are already in announcements, and in many cases, there may not be any Cygwin-specific changes, just upstream ones already covered by ChangeLog/NEWS/etc. That leaves build-time deps and long-term package history. For those, I would suggest the following: * I'm working on a method to add build deps to .cygport(5) files and have cygport(1) verify their presence. * Each package would get a git repository on sourceware for its .cygport, .hint, and other packaging files, as in Fedora and as I started doing in Ports. Packages which do need Cygwin-specific documentation could certainly continue providing it; all I'm suggesting is they no longer be required for every single package. Yaakov
src/winsup/cygwin ChangeLog crt0.c dcrt0.cc
CVSROOT:/cvs/src Module name:src Changes by: cori...@sourceware.org 2011-03-17 08:40:25 Modified files: winsup/cygwin : ChangeLog crt0.c dcrt0.cc Log message: * crt0.c (mainCRTStartup): Move call to _feinitialise from here... * dcrt0.cc (_dll_crt0): ...to here. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/ChangeLog.diff?cvsroot=srcr1=1.5192r2=1.5193 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/crt0.c.diff?cvsroot=srcr1=1.6r2=1.7 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/dcrt0.cc.diff?cvsroot=srcr1=1.392r2=1.393
src/winsup/cygwin ChangeLog crt0.c dcrt0.cc
CVSROOT:/cvs/src Module name:src Branch: cv-post-1_7_9 Changes by: cori...@sourceware.org 2011-03-17 08:41:20 Modified files: winsup/cygwin : ChangeLog crt0.c dcrt0.cc Log message: * crt0.c (mainCRTStartup): Move call to _feinitialise from here... * dcrt0.cc (_dll_crt0): ...to here. 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.15r2=1.5189.2.16 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/crt0.c.diff?cvsroot=srconly_with_tag=cv-post-1_7_9r1=1.6r2=1.6.2.1 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/dcrt0.cc.diff?cvsroot=srconly_with_tag=cv-post-1_7_9r1=1.392r2=1.392.2.1
src/winsup/cygwin ChangeLog syslog.cc autoload ...
CVSROOT:/cvs/src Module name:src Branch: cv-post-1_7_9 Changes by: cori...@sourceware.org 2011-03-17 16:14:51 Modified files: winsup/cygwin : ChangeLog syslog.cc autoload.cc fhandler_socket.cc Log message: * fhandler_socket.cc (get_inet_addr): Make externally available. * autoload.cc (GetUdpTable): Define. * syslog.cc (connect_syslogd): Use get_inet_addr rather than _stat64 to check for local socket file. Create socket with type returned by get_inet_addr. If connect on UDP socket works, test if there's really a listening peer, otherwise fall back to Windows event log. (try_connect_syslogd): Use syslogd_inited flag to check if syslogd is available. 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.16r2=1.5189.2.17 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/syslog.cc.diff?cvsroot=srconly_with_tag=cv-post-1_7_9r1=1.48.4.1r2=1.48.4.2 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/autoload.cc.diff?cvsroot=srconly_with_tag=cv-post-1_7_9r1=1.189.2.2r2=1.189.2.3 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/fhandler_socket.cc.diff?cvsroot=srconly_with_tag=cv-post-1_7_9r1=1.269r2=1.269.2.1
Re: Compiled program does nothing when executing it under Cygwin
On Mar 11 16:48, Corinna Vinschen wrote: On Mar 11 15:14, Greg Chicares wrote: On 2011-03-11 14:56Z, Mengsk wrote: [...previously-compiled program stopped working after partial Cygwin upgrade...] Cannot find entry point _feinitialise in dynamic link library cygwin1.dll Try rebuilding your program from scratch. It sounds like the cygwin1.dll you now have (after the upgrade) is a different version than the program expects. Sounds like an executable built under 1.7.8 trying to be run under an earlier version. Dave, is it really necessary to call _feinitialise in crt0.c? We usally have new entry points in newer versions of Cygwin, and we don't guarantee that applications build under newer DLLs will not run under older DLLs. However, that doesn'usually mean that these applications never work, only if they use one of the new entry points. With _feinitialise called from crt0.c apps build under 1.7.8 can never work under earlier DLLs. So my question is, isn't it sufficient to call _feinitialise from _dll_crt0? I had a private talk with Dave and it's no problem to move the _feinitialise call into the DLL itself. I applied a patch to 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: ITP dos2unix 5.2.1-1
On 03/16/2011 10:38 PM, Charles Wilson wrote:
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
That is an old version. Here is the latest:
dos2unix 5.2.1 (2011-03-04)
Usage: dos2unix [options] [file ...] [-n infile outfile ...]
-ascii convert only line breaks (default)
-iso conversion between DOS and ISO-8859-1 character set
-1252 Use Windows code page 1252 (Western European)
-437 Use DOS code page 437 (US) (default)
-850 Use DOS code page 850 (Western European)
-860 Use DOS code page 860 (Portuguese)
-863 Use DOS code page 863 (French Canadian)
-865 Use DOS code page 865 (Nordic)
-7 Convert 8 bit characters to 7 bit space
-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
Re: Cygwin 1.7 string pattern matching problem with case sensitivity
On 2011-03-17 12:44Z, jean-benoit.ouel...@hidden.ca wrote:
I just upgraded Cygwin from 1.5.21-2 to 1.7.8-1 and I'm getting problems with
case sensitivity.
Let's assume that 'file.csv' contains these 2 lines:
Hello, 123
hello, 456
The following commands will output both lines instead of the desired first
line only:
awk -F, '$1 ~ /^[A-Z]/ {print $0}' file.csv
grep ^[A-Z]/ file.csv
Either override the locale
http://www.cygwin.com/cygwin-ug-net/setup-locale.html
or, preferably, use character classes, e.g.:
$grep '^[[:upper:]]' file.csv
Hello, 123
--
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 make a COM port in windows accessible using cygwin?
When I typed ls /dev/tty, I did not get any response. Any other possible solutions Vaclav Haisman wrote: Vinod Pillai wrote, On 15.3.2011 21:03: Im sorry but Im a complete novice at this. I cd-ed into the /dev folder. But I could not find a ttyS1. If you could elaborate what exactly I must do, it would be helpful. Thank you. Read the page I have linked: These devices cannot be seen with the command ls /dev/ although commands such as ls /dev/tty work fine. -- VH Vinod Vaclav Haisman wrote: On Tue, 15 Mar 2011 06:18:00 -0700 (PDT), Vinod Pillai wrote: I have a virtual serial port set up on my COM2 port. I am trying to run a program on cygwin which will require the use of this serial port on COM2. I was wondering how I could connect to the COM port using cygwin? See http://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-posixdevices. You probably want /dev/ttyS1 for COM2. -- VH -- 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 -- View this message in context: http://old.nabble.com/How-do-I-make-a-COM-port-in-windows-accessible-using-cygwin--tp31152875p31172378.html Sent from the Cygwin list mailing list archive at Nabble.com. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: ITP dos2unix 5.2.1-1
Dropped cygwin-apps. On 3/17/2011 5:05 AM, Erwin Waterlander wrote: On 03/16/2011 10:38 PM, Charles Wilson wrote: 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 The new package does not follow symlinks, so you don't damage files on other locations. If you force conversion a copy is created. The symlink target remains unmodified. There is not a separate option to force conversion of symlinks. Perhaps the creation of copies should be default. 5: if the new package is used, I think we should patch it to always follow symlinks (or add a new option, and make it default to follow). I would propose a new option to follow symlinks. By default not follow, but copy (don't damage files on other locations). Erwin, you don't seem to understand the importance of not changing current behavior, when replacing existing apps. I'm trying to point out (a) how little your proposed package actually differs from the current cygutils implementations, and (b) what needs to change to make the new version a drop-in replacement. Because that's what you're trying to do: make a drop in replacement. Regardless of whether some current behavior of cygutils-dos2unix is good or bad, CHANGE is worse -- since people have been relying on the current behavior for years. Now, if you REALLY feel strongly about some particular point, then I would suggest a stepwise conversion. FIRST, patch and release the new package, dos2unix, such that it is a drop-in replacement with NO expected changes in behavior (other than, obviously, its new capabilities like 7bit, iso, etc). For instance, a --no-follow / --follow pair of options, where --follow is the default (to match the behavior of cygutils-dos2unix), but users can specify --no-follow if they want. Then, after a suitable time has elapsed -- 1 month? 3 months? -- change the default to be --no-follow, and make a BIG DEAL of this behavior change in your announcement. Rule: Users don't like change. Only make one change at a time. So, change #1: switch from cygutils-dos2unix to the new package. change #2, somewhat later: change the default follow behavior. BTW: I *guarantee* that there will be some behavioral change in your drop in replacement that we missed. A bug, packaging oops, SOMETHING. You'll want to use the 1-month (3?) grace period to wait for those reports, and fix 'em, before introducing any new, deliberate, behavior changes. (BTW, you'll want to test the behavior of the apps, on files, on pipes with redirection to a file, etc, on DOS mounts in addition to UNIX ones...voice of experience... :-( Note also that my proposal (TWO new options, where one reasserts the default -- whatever that default may be) is similar to the --force/--safe pair. Good command-line option design usually requires these paired options, so that the CLI doesn't change even when/if you (later) decide to change the default. It's not about overriding an Administrative alias; it's about easily overriding MY OWN alias, if I generally like the opposite default from what the base executable does but SOMETIMES want to behave the other way. Sure, I can use full-path-to-exe to avoid the alias, but given alias d2u='/usr/bin/d2u --force --follow' /usr/bin/d2u * vs d2u --safe --no-follow * The latter is more expressive: HERE'S what I want to do right now, rather than Oh yeah, my alias does X but the default app does !X, so to get !X I need to override some alias in my ~/.bashrc that I haven't edited in years, and just usually take for granted as THE behavior of that app... Or, interactively I like --follow, but I don't want scripts to run amuck, so I'll alias d2u to 'd2u --follow' but explicitly use 'd2u --no-follow' in scripts so they DTRT regardless of any alias settings. Or, my alias sets LOTS of (anti-)defaults, and I just want to reassert the real default behavior for ONE of them: d2u --safe (but keep the alias --follow behavior) Think '-i' vs. '-f' for 'rm' FYI, I think a patch to add --safe, plus the patch to add --follow/--no-follow (where --follow does NOT also imply --force) would be suitable patches to go upstream. Assuming that patch was adopted upstream, the only (temporary) difference between cygwin's new package and upstream would be the default behavior of the follow/no-follow pair. -- 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: How do I make a COM port in windows accessible using cygwin?
On 3/17/2011 08:22, Vinod Pillai wrote: Vaclav Haisman wrote: Vinod Pillai wrote, On 15.3.2011 21:03: Im sorry but Im a complete novice at this. I cd-ed into the /dev folder. But I could not find a ttyS1. If you could elaborate what exactly I must do, it would be helpful. Thank you. Read the page I have linked: These devices cannot be seen with the command ls /dev/ although commands such as ls /dev/tty work fine. When I typed ls /dev/tty, I did not get any response. Any other possible solutions The command ls /dev/tty works for me: $ ls -l /dev/tty crw--w 1 jeremyb Domain Users 5, 0 Mar 17 08:43 /dev/tty Even if the path you attempted to use didn't exist, you should have got /some/ response: $ ls /dev/nonexistent ls: cannot access /dev/nonexistent: No such file or directory Can you provide more details about what exactly happened when you tried to run your command? -Jeremy -- 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: Cygwin 1.7 string pattern matching problem with case sensitivity
From: jean-benoit.ouel...@bell.ca
Hi!
I just upgraded Cygwin from 1.5.21-2 to 1.7.8-1 and I'm getting
problems with case sensitivity.
Let's assume that 'file.csv' contains these 2 lines:
Hello, 123
hello, 456
The following commands will output both lines instead of the desired
first line only:
awk -F, '$1 ~ /^[A-Z]/ {print $0}' file.csv
grep ^[A-Z]/ file.csv
There must be something wrong in my setup but I'm running out of ideas
to find the problem rootcause.
Jean-Benoit Ouellet
If you set LANG=C you will probably get what you expected.
Your grep command has an extraneous slash (/), so doesn't
print either line.
--Ken Nellis
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. Personally I'd rather have the same tool in Cygwin as in Linux, because it maximizes the portability of my (common) shell startup scripts and aliases. Changing those one time to eliminate a special case is no problem. That said, this isn't a tool I have to use much, so my investment in it is pretty light. -- 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
List of available network printer
Hi all, just a simple question : how to get the list of available network printers for using lpr -P ? eg //Server/printername-x //Server/printername-y .. Thanks a lot Norbert -- Dipl. Phys. Norbert Zacharias Wind Measurements Power Curve Measurements DEWI GmbH Ebertstrasse 96 26382 Wilhelmshaven Germany Tel.: +49 4421 4808 876 Fax:+49 4421 4808 843 Email: n.zachar...@dewi.de Home: http://www.dewi.de DEWI GmbH - Deutsches Windenergie-Institut, Wilhelmshaven Commercial Register No.: Amtsgericht Oldenburg, HRB 130241 Managing Director: Jens Peter Molly Chairman of the supervisory board: Ministerialrat Dr. Niels Kämpny P Please consider the environment before printing this email. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
misleading message fatal error - cygheap base mismatch detected
Hi- I have some legacy FORTRAN code which works fine on ubuntu 64bit. However when I recompiled on cygwin I got the following error: $ bin/mseval 1 [main] mseval 5468 P:\rlstools\bin\mseval.exe: *** fatal error - cygheap base mismatch detected - 0x61239790/0x6D3D9790. This problem is probably due to using incompatible versions of the cygwin DLL. Search for cygwin1.dll using the Windows Start-Find/Search facility and delete all but the most recent version. The most recent version *should* reside in x:\cygwin\bin, where 'x' is the drive on which you have installed the cygwin distribution. Rebooting is also suggested if you are unable to find another cygwin DLL. As it turns out I was allocating too much memory and when I reduce my array sizes everything works fine. I know the message says probably but it might not hurt to suggest that the program is too big to fit in memory Regards Robert (Bob) L. Sandefur PE -- 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
On 03/17/2011 02:32 PM, Charles Wilson wrote: Dropped cygwin-apps. Erwin, you don't seem to understand the importance of not changing current behavior, when replacing existing apps. I'm trying to point out (a) how little your proposed package actually differs from the current cygutils implementations, and (b) what needs to change to make the new version a drop-in replacement. Because that's what you're trying to do: make a drop in replacement. Regardless of whether some current behavior of cygutils-dos2unix is good or bad, CHANGE is worse -- since people have been relying on the current behavior for years. Hi Chuck, I do understand you very well, but I come from the other side. The dos2unix that I packed and maintain is around on Unix/Linux since 1989. I assume there are much more Linux users than Cygwin users. So I don't want to break things on Linux. Since Cygwin tries to be Linux-alike, I offer this package to the cygwin community. Personally I prefer to have the same on Cygwin as on Linux. The cygwin community may have got used to the current cygwin tailored implementation. But I bet there are many cygwin users who also work on Linux, so there is a big chance they are already familiar with the version I maintain. Erwin -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] Updated: openssl-0.9.8r-2, openssl-devel-0.9.8r-2, libopenssl098-0.9.8r-2
On 16/03/2011 21:23, Corinna Vinschen wrote: 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 Thanks. Confirming this fixes the crash I was seeing. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[SOLVED] cygwin1.dll upgrade problem
Hi, Corinna et al. I'm not subscribed to the mailing list: I read it via gmane, but I've just solved a problem that might be run into by other users. Initial symptom: svn exits immediately without any output I traced this to a recent upgrade of base/cygwin which left behind /bin/cygwin1.dll.new and didn't copy it over. I tried closing all cygwin programs and re-installing, but still it didn't upgrade and left the .new file behind. Illumination dawned - I run cron as a service, and this was holding the old copy of the library open. Shut down cron, re-install, and all is now fine. If you feel this is useful, please feel free to forward it on to the mailing list. best regards Alan -- Alan J. Wylie http://www.wylie.me.uk/ -- 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: {serf,libserf0_1,libserf0-devel}-0.7.1-1
The serf packages have been updated to the new upstream release 0.7.1. See http://code.google.com/p/serf/source/browse/tags/0.7.1/CHANGES for more details about the changes in this release. More information about serf can be found at http://code.google.com/p/serf/. CYGWIN NOTES: = The 0.7.0 release increased the version of the libserf0 library from 0 to 1, so libserf0_0 and libserf0_1 may be installed in parallel. This is necessary because applications linked against serf 0.3.x will not run with serf 0.7.x and vice versa. Note that upstream did not increase the library version. Please note that 0.7.x is not API-compatible with 0.3.x. Applications compiled against 0.3.x may require changes to compile against 0.7.x. DESCRIPTION: The serf library is a C-based HTTP client library built upon the Apache Portable Runtime (APR) library. It multiplexes connections, running the read/write communication asynchronously. Memory copies and transformations are kept to a minimum to provide high performance operation. DOWNLOAD: = Note that downloads from sources.redhat.com (aka cygwin.com) aren't allowed due to bandwidth limitations. This means that you will need to find a mirror which has this update, please choose the one nearest to you: http://cygwin.com/mirrors.html QUESTIONS: == If you want to make a point or ask a question the Cygwin mailing list is the appropriate place. CYGWIN-ANNOUNCE UNSUBSCRIBE INFO: = To unsubscribe to the cygwin-announce mailing list, look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-YOU=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- David Rothenberger daver...@acm.org -- 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: subversion-1.6.16-1
A new version of subversion is available. This is a new upstream release. NEWS: = See CHANGES (URL below) for more information about the differences between 1.6.16 and previous Subversion releases. In addition to the normal collection of bug fixes, and stability enhancements, this release also addresses CVE-2011-0715, a remotely-triggerable DoS for httpd-based Subversion servers. More information can be found in the advisory: http://subversion.apache.org/security/CVE-2011-0715-advisory.txt IMPORTANT: This release will silently upgrade your Subversion working copies to the 1.6 format, rendering them unusable with previous major versions of Subversion. Please see the release notes http://subversion.apache.org/docs/release-notes/1.6.html for more details about the changes in Subversion. See http://svn.apache.org/repos/asf/subversion/tags/1.6.16/CHANGES for more details about the changes in 1.6.16. DESCRIPTION: Subversion is a version control system designed to be a compelling successor to CVS. Please see http://svnbook.red-bean.com/en/1.5/index.html for the latest official release of the Subversion Book, covering 1.5 or http://svnbook.red-bean.com/nightly/en/index.html for the WIP version of the book covering 1.6. DOWNLOAD: = Note that downloads from sourceware.org (aka cygwin.com) aren't allowed due to bandwidth limitations. This means that you will need to find a mirror which has this update, please choose the one nearest to you: http://cygwin.com/mirrors.html QUESTIONS: == If you want to make a point or ask a question the Cygwin mailing list is the appropriate place. CYGWIN-ANNOUNCE UNSUBSCRIBE INFO: = To unsubscribe to the cygwin-announce mailing list, look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-YOU=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- David Rothenberger daver...@acm.org -- 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
On 3/17/2011 10:41 AM, Erwin Waterlander wrote: I do understand you very well, but I come from the other side. The dos2unix that I packed and maintain is around on Unix/Linux since 1989. I assume there are much more Linux users than Cygwin users. So I don't want to break things on Linux. You want to replace a CYGWIN package. I fail to see how that would break anything on a linux machine. My suggested (upstreamable) patches don't change the linux behavior at all, except to add new option flags. In the upstreamed patch, the default behavior would remain as-is (--safe and --no-follow would be the defaults; as today, --force would override these defaults with its current behavior of [break symlink make copy modify copy] + always convert even binary files). I proposed an *additional* temporary, cygwin-only patch that is not upstreamed, that changes the default behavior of the --follow/--no-follow pair. For a short time. I might even suggest the following: assume dos2unix-5.2.3 is released with the --follow --no-follow --safe options added to upstream. Then, simultaneously release TWO packages on cygwin: dos2unix-5.2.3-1 (that has a cygwin-specific patch to make the default behavior, on cygwin, --follow) dos2unix-5.2.3-10 (that is stock upstream 5.2.3) In your setup.hint, mark curr: 5.2.3-1 test: 5.2.3-10 That way, if your users who are currently used to linux behavior complain, you can say it's a transition thing on cygwin, given their old implementation. For now, switch to the 'test' release which works just like linux. In a few months, it'll be the default. In the above, I left releases -2 thru -9 open for any necessary bug-fixes with the new version, that might be required before the flag-day switch to the linux-like behavior. Since Cygwin tries to be Linux-alike, I offer this package to the cygwin community. Personally I prefer to have the same on Cygwin as on Linux. The cygwin community may have got used to the current cygwin tailored implementation. But I bet there are many cygwin users who also work on Linux, so there is a big chance they are already familiar with the version I maintain. Any confusion of behavior only applies in two places: 1) a user's own memory and habits 2) scripts that are SHARED or copied without change between cygwin and linux environments Regarding #1 Right now, any affected cygwin user ALREADY knows that cygwin d2u behaves differently than unix d2u. So...for an *existing* cygwin user, making the new cygwin-d2u behave exactly like cygUTILS-d2u is a null event. No change. They used to adapt to the difference in behavior between the two platforms; they need to continue to adapt to that difference. In fact, it's probably a habit by now. (if this esoteric --follow behavior matters to them). NEW cygwin users might be surprised by the cygUTILS-d2u/new-cygwin-d2u behavior. But...there are far fewer of those in any given three month period than there are existing cygwin users. So it doesn't make sense to say well, since many cyg users are familiar with the linux version, it's okay to change the one they are used to using on cygwin, to match the one they are used to using on linux. This argument applies to far more than just d2u, btw -- even limited to the universe of linux software that also appears on cygwin. But from the broader universe: Here's a story from 10 years ago: I'm used to using infix notation (2 + 4 =) on dumb 4-function calculators, but I LOVED my HP48's postfix (aka reverse polish notation, or RPN) -- 2 enter 4 +. I was VERY ANNOYED when HP decided that, since people are used to infix notation on TI calculators, they should switch all new HP scientific calcs to infix by default. Sure, I could deal with it...but I really didn't want to retrain my fingers for my new (at the time) HP. Fortunately the new one could be switched back to RPN (but I eventually dumped it anyway and went back to the trusty HP48, but that was because the build quality of the new model sucked). To finish the story now that my 20-year-old HP48's screen is damaged -- I now have an HP48 emulator on my Android phone. But I miss my classic HP clicky keys; a touchscreen is just not the same -- but apparently not even the newest model HP50g has restored the classic key construction and feel. :-( So, my brain says: dumb 4-function calc: infix HP scientific calc: rpn Right now, a lot of people may have trained themselves linux: d2u works /this way/ cygwin: d2u works /that way/ Don't change it unless you must, and only introduce ONE CHANGE at a time. Right now, you're at the 'switch to alt implementation; add lots of new features like -7 and --convert=CP' stage (as viewed from the perspective of the cygwin distribution and users). Save any other changes for later...even if that means you have to
Re: [SOLVED] cygwin1.dll upgrade problem
Am 17.03.2011 16:50, schrieb Alan J. Wylie: Hi, Corinna et al. I'm not subscribed to the mailing list: I read it via gmane, but I've just solved a problem that might be run into by other users. Initial symptom: svn exits immediately without any output I traced this to a recent upgrade of base/cygwin which left behind /bin/cygwin1.dll.new and didn't copy it over. I tried closing all cygwin programs and re-installing, but still it didn't upgrade and left the .new file behind. Illumination dawned - I run cron as a service, and this was holding the old copy of the library open. Shut down cron, re-install, and all is now fine. If you feel this is useful, please feel free to forward it on to the mailing list. setup.exe will have made mention about in-use files that should have gotten replaced but were only scheduled for replacement across the next reboot, and that you need to reboot in order to finish the upgrade. Of course you can retry to shut down all processes and re-do the upgrade without a reboot, but nonetheless the reboot should happen soon, not after days or weeks with other intermitting setup.exe runs, else you might inadvertently be switched back to older installations on a reboot. Be sure to carefully read the pop-up requesters and infobubbles from setup.exe. -- Matthias Andree -- 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: Cygwin 1.7 string pattern matching problem with case sensitivity
I changed my LANG from en_US.ISO-8859-1 to C.ISO-8859-1 and it resolved the problem. Thanks for your quick input. -- 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: Cygwin 1.7 string pattern matching problem with case sensitivity
Am 17.03.2011 18:26, schrieb jean-benoit.ouel...@bell.ca: I changed my LANG from en_US.ISO-8859-1 to C.ISO-8859-1 and it resolved the problem. Thanks for your quick input. Possibly you can use LC_COLLATE and/or LC_CTYPE instead, if you're looking for narrower overrides. -- Matthias Andree -- 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
Problems with the new base-files-4.0-5?
I have just updated Cygwin, and now starting a console (Cygwin.bat or
MinTTY) prints:
-bash: ${p}: ambiguous redirect
and PRINTER variable isn't set.
Reverting to base-files-4.0-4 works just fine and PRINTER is set
correctly to my default printer.
In 4.0-5 it seems something is broken in /etc/profile.
Ciao,
Angelo.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] New package: gnucap-2009.12.07-1
Version 2009.12.07-1 of gnucap has been uploaded. GNUCAP is the GNU Circuit Analysis Package, a modern post-spice analog and mixed signal circuit simulator. It is a work in progress, but can replace Spice for many simulation purposes. It has several technical advantages over historical Spice packages (details at http://www.gnucap.org/) and is compatible with standard Spice netlists and models. This is the first Cygwin release of this program. For now documentation can be found at gnucap.org. *** 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
Re: ITP dos2unix 5.2.1-1
On Thu, Mar 17, 2011 at 10:13:51AM -0400, Andrew Schulman wrote: 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. Personally I'd rather have the same tool in Cygwin as in Linux, because it maximizes the portability of my (common) shell startup scripts and aliases. Changing those one time to eliminate a special case is no problem. That said, this isn't a tool I have to use much, so my investment in it is pretty light. We're really looking for specific observations here not general. We're trying not to break things for people who already are used to the Cygwin behavior. Are you saying that you've actually had to modify scripts because of differences in behavior between Cygwin and Linux's dos2unix? If so, that actually sounds like you've made accommodations which could break if dos2unix were to change. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Problems with the new base-files-4.0-5?
Il 17/03/2011 19.00, Angelo Graziosi ha scritto:
I have just updated Cygwin, and now starting a console (Cygwin.bat or
MinTTY) prints:
-bash: ${p}: ambiguous redirect
and PRINTER variable isn't set.
Reverting to base-files-4.0-4 works just fine and PRINTER is set
correctly to my default printer.
In 4.0-5 it seems something is broken in /etc/profile.
Perhaps you need this:
- ([[ -e ${p} ]] read -r PRINTER ${p}) PRINTER=${PRINTER%%,*}
+ ([[ -e ${p} ]] read -r PRINTER ${p}) PRINTER=${PRINTER%%,*}
Ciao,
Angelo.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Problems with the new base-files-4.0-5?
On Thu, Mar 17, 2011 at 07:59:11PM +0100, Angelo Graziosi wrote:
Il 17/03/2011 19.00, Angelo Graziosi ha scritto:
I have just updated Cygwin, and now starting a console (Cygwin.bat or
MinTTY) prints:
-bash: ${p}: ambiguous redirect
and PRINTER variable isn't set.
Reverting to base-files-4.0-4 works just fine and PRINTER is set
correctly to my default printer.
In 4.0-5 it seems something is broken in /etc/profile.
Perhaps you need this:
- ([[ -e ${p} ]] read -r PRINTER ${p}) PRINTER=${PRINTER%%,*}
+ ([[ -e ${p} ]] read -r PRINTER ${p}) PRINTER=${PRINTER%%,*}
Or even,
+ ([[ -e ${p} ]] read -r PRINTER ${p}) PRINTER=${PRINTER%%,*}
--
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 with cygwin1.dll after update
Hi,
I built a very simple program with g++ : int main() { return 0; }
from cygwin it always returns 127, and if I try to start it from cmd I have
the following message :
the procedure entry point _feinitiliase could not be located in the dynamic
link library cygwin1.dll
I tried to remove cygwin1.dll and reinstall it, but the result is the same.
Thank you,
Wilfried.
--
View this message in context:
http://old.nabble.com/Problem-with-cygwin1.dll-after-update-tp31175622p31175622.html
Sent from the Cygwin list mailing list archive at Nabble.com.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Problem with cygwin1.dll after update
On 17/03/2011 19:16, Wilfried Fauvel wrote:
Hi,
I built a very simple program with g++ : int main() { return 0; }
from cygwin it always returns 127, and if I try to start it from cmd I have
the following message :
the procedure entry point _feinitiliase could not be located in the dynamic
link library cygwin1.dll
I tried to remove cygwin1.dll and reinstall it, but the result is the same.
See the earlier thread Compiled program does nothing when executing it
under Cygwin(*). Your old DLL is still in use somehow; if it was in-use when
you ran setup.exe, no amount of removing and reinstalling will help until you
have rebooted.
cheers,
DaveK
--
(*) - http://cygwin.com/ml/cygwin/2011-03/threads.html#00335
--
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: Problems with the new base-files-4.0-5?
On 03/17/2011 12:59 PM, Angelo Graziosi wrote:
Il 17/03/2011 19.00, Angelo Graziosi ha scritto:
I have just updated Cygwin, and now starting a console (Cygwin.bat or
MinTTY) prints:
-bash: ${p}: ambiguous redirect
and PRINTER variable isn't set.
Reverting to base-files-4.0-4 works just fine and PRINTER is set
correctly to my default printer.
In 4.0-5 it seems something is broken in /etc/profile.
Perhaps you need this:
- ([[ -e ${p} ]] read -r PRINTER ${p}) PRINTER=${PRINTER%%,*}
+ ([[ -e ${p} ]] read -r PRINTER ${p}) PRINTER=${PRINTER%%,*}
/etc/profile is using [[ ]]? Bad. That's not required by POSIX, and
will break for anyone who logs in with a shell that doesn't understand
it (for example, dash or posh). Bashisms should not appear in /etc/profile.
--
Eric Blake ebl...@redhat.com+1-801-349-2682
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
Re: Problems with the new base-files-4.0-5?
On 3/17/2011 3:21 PM, Eric Blake wrote:
On 03/17/2011 12:59 PM, Angelo Graziosi wrote:
Perhaps you need this:
- ([[ -e ${p} ]] read -r PRINTER ${p}) PRINTER=${PRINTER%%,*}
+ ([[ -e ${p} ]] read -r PRINTER ${p}) PRINTER=${PRINTER%%,*}
/etc/profile is using [[ ]]? Bad. That's not required by POSIX, and
will break for anyone who logs in with a shell that doesn't understand
it (for example, dash or posh). Bashisms should not appear in /etc/profile.
Yep. This is /etc/profile which is used by all POSIX shells, not just
bash. Now, if we were talking about ~/.bash_profile or some mythical
/etc/bash_profile [1], that'd be different.
[1] bash doesn't actually use any file by this name
Try running this
$ dash -li
(oddly, posh -li doesn't report any errors...)
--
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: Problem with cygwin1.dll after update
Dave Korn-9 wrote:
On 17/03/2011 19:16, Wilfried Fauvel wrote:
Hi,
I built a very simple program with g++ : int main() { return 0; }
from cygwin it always returns 127, and if I try to start it from cmd I
have
the following message :
the procedure entry point _feinitiliase could not be located in the
dynamic
link library cygwin1.dll
I tried to remove cygwin1.dll and reinstall it, but the result is the
same.
See the earlier thread Compiled program does nothing when executing it
under Cygwin(*). Your old DLL is still in use somehow; if it was in-use
when
you ran setup.exe, no amount of removing and reinstalling will help until
you
have rebooted.
cheers,
DaveK
--
(*) - http://cygwin.com/ml/cygwin/2011-03/threads.html#00335
--
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
Hi,
thank you very much, I reboot rebuild and everything was fine again.
Wilfried.
--
View this message in context:
http://old.nabble.com/Problem-with-cygwin1.dll-after-update-tp31175622p31175781.html
Sent from the Cygwin list mailing list archive at Nabble.com.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Cygport woes: CHOST not defined.
Hi list,
Attempting to rebuild gcc4-4.3.4-3 from source, I got a bunch of error
messages during the install stage of cygport:
Fixing libtool modules:
/usr/lib/cygport/src_postinst.cygpart: line 763: test: i686-pc-cygwin: unary
operator expected
[ ... snip several more ... ]
Stripping executables:
/usr/lib/cygport/syntax.cygpart: line 191: test: i686-pc-cygwin: unary
operator expected
/usr/lib/cygport/syntax.cygpart: line 191: test: !=: unary operator expected
usr/bin/c++-4.exe
/usr/lib/cygport/syntax.cygpart: line 191: test: i686-pc-cygwin: unary
operator expected
/usr/lib/cygport/syntax.cygpart: line 191: test: !=: unary operator expected
[ ... snip several more ... ]
Looking at the context, I infer that CHOST must be undefined:
760 # would otherwise be CHOST, but gcc ships $target libraries
761 case ${CTARGET} in
762 *-*-cygwin*|*-*-mingw*)
763 if test ${CTARGET} != ${CHOST} # cross-compiler, use sysroot
764 then
765 dodir /usr/${CTARGET}/sys-root/$(__target_prefix)/bin
766 mv ${ltlibdir}/${dlname}
${D}/usr/${CTARGET}/sys-root/$(__target_prefix)/bin/
767 else
768 origdlname=${dlname}
... and quite likely CBUILD as well:
190 __cross_compiling() {
191 return $(test ${CBUILD} != ${CHOST} || test ${CHOST} !=
${CTARGET})
192 }
This is basically a clean build - I renumbered the -3 extensions to -4, but
the cygport script is unchanged(*) so maybe there's something wrong in my
src_install override, to do with cygport's new cross-compiling features?
I'll be grepping away trying to find out where these variables are supposed
to come from, but any hints that could speed up my debugging would be
appreciated!
cheers,
DaveK
--
(*) -
http://www.mirrorservice.org/sites/sourceware.org/pub/cygwin/release/gcc4/gcc4-4.3.4-1-src.tar.bz2/gcc4-4.3.4-1.cygport?extract=true
--
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
Op 17-3-2011 17:57, Charles Wilson schreef: Final point: I realize nobody wants to maintain a non-upstreamable forked version of software. Everybody wants to be able to build software on cygwin out of the box. So...if the upstream people really really hate --follow/--no-follow and won't accept it, then maybe an all-at-once change here on cygwin would be okay. Ditto --safe. But...that's not an issue here, because *you* are the upstream people! So let's rephrase: What is the upstream objection to providing a few new options, with no change in upstream's current default behavior: --followfollow symbolic links and modify the pointed-to file. This differs from --force, which breaks the symbolic link, replaces it with a local copy, and modifies the copy. If --force, then --follow has no effect. --no-follow do not follow symbolic links. If --force, then --no-follow has no effect. ... --safe Do not modify binary files; opposite of --force. (default) Time to create the patch? Patch requires too many internal changes that are too ugly, due to internal architecture (can't imagine this is the objection to --safe; that's a two-liner)? Style? Hi Chuck, I'm willing to maintain patches for Cygwin, to make the transition easier. But if there is no chance that the package gets accepted, I rather save myself the trouble. best regards, Erwin -- 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
On 03/17/2011 03:56 PM, Erwin Waterlander wrote: Op 17-3-2011 17:57, Charles Wilson schreef: Final point: I realize nobody wants to maintain a non-upstreamable forked version of software. Everybody wants to be able to build software on cygwin out of the box. So...if the upstream people really really hate --follow/--no-follow and won't accept it, then maybe an all-at-once change here on cygwin would be okay. Ditto --safe. But...that's not an issue here, because *you* are the upstream people! So let's rephrase: What is the upstream objection to providing a few new options, with no change in upstream's current default behavior: --followfollow symbolic links and modify the pointed-to file. This differs from --force, which breaks the symbolic link, replaces it with a local copy, and modifies the copy. If --force, then --follow has no effect. --no-followdo not follow symbolic links. If --force, then --no-follow has no effect. ... --safe Do not modify binary files; opposite of --force. (default) Time to create the patch? Patch requires too many internal changes that are too ugly, due to internal architecture (can't imagine this is the objection to --safe; that's a two-liner)? Style? Hi Chuck, I'm willing to maintain patches for Cygwin, to make the transition easier. But if there is no chance that the package gets accepted, I rather save myself the trouble. My 2cents worth: I for one look forward to the new package. All of the software we develop runs on both platforms and I personally use the dos2unix, etc tools often. Same tools on both platforms gets my vote anytime. roger wells best regards, Erwin -- 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 -- Roger Wells, P.E. SAIC 221 Third St Newport, RI 02840 401-847-4210 (voice) 401-849-1585 (fax) roger.k.we...@saic.com -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: ITP dos2unix 5.2.1-1
On 03/17/2011 01:56 PM, Erwin Waterlander wrote: So let's rephrase: What is the upstream objection to providing a few new options, with no change in upstream's current default behavior: I'm willing to maintain patches for Cygwin, to make the transition easier. But if there is no chance that the package gets accepted, I rather save myself the trouble. There's two sets of patches being talked about here: 1) What temporary (3-month?) patches are needed to make the dos2unix package a drop-in replacement to the existing cygwin dos2unix, so that people can start testing if it really was a drop-in. 2) What patches (permanent) are worth adding to upstream, to fix deficiencies in the usability of upstream when compared to what cygwin has. But having re-read this conversation, my original objection based on duplication of effort seems pretty weak; you've convinced me that the biggest reason to switch to dos2unix is that it has more features. However, I say that with reservation - I agree with Chuck that you need a transition period where we make the switch but preserve cygwin behavior, to minimize the variables. I'm definitely in agreement with making a phased switch to the upstream package. My personal habits are 'd2u file', without regards to the message it prints. So I definitely want the d2u shortcut to be part of the package (it apparently is not provided by upstream, and I'm too used to 'ln -s `which dos2unix` ~/bin/d2u' when installing a new machine). -- Eric Blake ebl...@redhat.com+1-801-349-2682 Libvirt virtualization library http://libvirt.org signature.asc Description: OpenPGP digital signature
Re: Cygport woes: CHOST not defined.
On 17/03/2011 19:39, Dave Korn wrote: Looking at the context, I infer that CHOST must be undefined: Ah, it's my cygport script. For some reason I used to have a problem with the setting of CHOST by the default cygport script, so it unsets it. Hopefully I can just omit that with the newer cygport and everything will Just Work. cheers, DaveK -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: ITP dos2unix 5.2.1-1
On 3/17/2011 4:08 PM, Eric Blake wrote: On 03/17/2011 01:56 PM, Erwin Waterlander wrote: I'm willing to maintain patches for Cygwin, to make the transition easier. But if there is no chance that the package gets accepted, I rather save myself the trouble. There's two sets of patches being talked about here: 1) What temporary (3-month?) patches are needed to make the dos2unix package a drop-in replacement to the existing cygwin dos2unix, so that people can start testing if it really was a drop-in. 2) What patches (permanent) are worth adding to upstream, to fix deficiencies in the usability of upstream when compared to what cygwin has. OK, everybody, time out for a minute. Rather than talk vapor, I'll develop the patches necessary. The first one, or first set (e.g. #2, above), I'll propose that official upstream dos2unix accept *for all platforms*. It will not change upstream's behavior in any way, except for offering some new options. The second one (#1, above), I'll propose that Erwin use as part of his initial cygwin package offering. This one would be only a transitional measure, and would be slated to be dropped from a later cygwin package after a certain amount of time has passed. With regards to the d2u/u2d aliases, for now I'd just modify the cygport script to create those as hardlinks, and not modify or patch the package source at all. Standby... -- 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: Problems with the new base-files-4.0-5?
From: Eric Blake
On 03/17/2011 12:59 PM, Angelo Graziosi wrote:
Il 17/03/2011 19.00, Angelo Graziosi ha scritto:
I have just updated Cygwin, and now starting a console (Cygwin.bat
or
MinTTY) prints:
-bash: ${p}: ambiguous redirect
and PRINTER variable isn't set.
Reverting to base-files-4.0-4 works just fine and PRINTER is set
correctly to my default printer.
In 4.0-5 it seems something is broken in /etc/profile.
I see the same thing.
Perhaps you need this:
- ([[ -e ${p} ]] read -r PRINTER ${p}) PRINTER=${PRINTER%%,*}
+ ([[ -e ${p} ]] read -r PRINTER ${p})
PRINTER=${PRINTER%%,*}
/etc/profile is using [[ ]]? Bad. That's not required by POSIX, and
will break for anyone who logs in with a shell that doesn't understand
it (for example, dash or posh). Bashisms should not appear in
/etc/profile.
Seems there are several instances of this:
$ grep '\[\[' /etc/profile
([[ -e ${p} ]] read -r PRINTER ${p}) PRINTER=${PRINTER%%,*}
if [[ -n ${BASH_VERSION} ]]; then
[[ -f /etc/bash.bashrc ]] . /etc/bash.bashrc
elif [[ -n ${KSH_VERSION} ]]; then
elif [[ -n ${ZSH_VERSION} ]]; then
$
Is it reasonable to presume a quick turnaround on a fix?
--Ken Nellis
Start a crontab service
Hello, I tried to install cron locally on my laptop, and could not find instructions to proceed. I found FAQ 41, and failed to start sshd as well. I have now the two services installed: ~ cygrunsrv --verbose --list Service : sshd Current State : Stopped Command : /usr/sbin/sshd.exe stdin path : /dev/null stdout path : /var/log/sshd.log stderr path : /var/log/sshd.log Process Type: Own Process Startup : Automatic Account : LocalSystem Service : crontab Current State : Stopped Command : /usr/sbin/cron.exe stdin path : /dev/null stdout path : /var/log/crontab.log stderr path : /var/log/crontab.log Process Type: Own Process Startup : Automatic Account : LocalSystem I created a cyg_server account and added it to /etc/passwd: cyg_server:unused:1012:513:Cygwin server account,U-EV0016D4A35054\cyg_server,S-1-5-21-1126040635-2252147014-1092054940-1012:/home/cyg_server:/bin/bash I wasn't too sure about creating a 'domain policy'... Is this relevant if I am only concerned with one laptop? I probably got sshd and httpd to work in a previous version of cygwin... Not sure anymore. As I try to start the services (as local admin), I get: ~ cygrunsrv --verbose -S crontab cygrunsrv: Error starting a service: QueryServiceStatus: Win32 error 1062: The service has not been started. ~ cygrunsrv --verbose -S sshd cygrunsrv: Error starting a service: QueryServiceStatus: Win32 error 1062: The service has not been started. This is cron 4.1-59 OK cygrunsrv 1.34-1 OK cygutils 1.4.4-1 OK cygwin 1.7.8-1 OK Cygwin Configuration Diagnostics Current System Time: Thu Mar 17 22:04:28 2011 Windows Vista Enterprise Ver 6.0 Build 6001 Service Pack 1 Cygwin DLL version info: DLL version: 1.7.8 DLL epoch: 19 DLL old termios: 5 DLL malloc env: 28 Cygwin conv: 181 API major: 0 API minor: 236 Shared data: 5 DLL identifier: cygwin1 Mount registry: 3 Cygwin registry name: Cygwin Program options name: Program Options Installations name: Installations Cygdrive default prefix: Build date: CVS tag: cygwin-1_7_8-release Shared id: cygwin1S5 Thanks, Marc -- View this message in context: http://old.nabble.com/Start-a-crontab-service-tp31176889p31176889.html Sent from the Cygwin list mailing list archive at Nabble.com. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Problems with the new base-files-4.0-5?
On Thu, Mar 17, 2011 at 04:10:27PM -0500, Nellis, Kenneth wrote:
From: Eric Blake
On 03/17/2011 12:59 PM, Angelo Graziosi wrote:
Il 17/03/2011 19.00, Angelo Graziosi ha scritto:
I have just updated Cygwin, and now starting a console (Cygwin.bat
or
MinTTY) prints:
-bash: ${p}: ambiguous redirect
and PRINTER variable isn't set.
Reverting to base-files-4.0-4 works just fine and PRINTER is set
correctly to my default printer.
In 4.0-5 it seems something is broken in /etc/profile.
I see the same thing.
Perhaps you need this:
- ([[ -e ${p} ]] read -r PRINTER ${p}) PRINTER=${PRINTER%%,*}
+ ([[ -e ${p} ]] read -r PRINTER ${p})
PRINTER=${PRINTER%%,*}
Please test if
[ -e ${p} ] read -r PRINTER ${p} PRINTER=${PRINTER%%,*}
works as expected.
/etc/profile is using [[ ]]? Bad. That's not required by POSIX, and
will break for anyone who logs in with a shell that doesn't understand
it (for example, dash or posh). Bashisms should not appear in
/etc/profile.
Seems there are several instances of this:
$ grep '\[\[' /etc/profile
([[ -e ${p} ]] read -r PRINTER ${p}) PRINTER=${PRINTER%%,*}
if [[ -n ${BASH_VERSION} ]]; then
[[ -f /etc/bash.bashrc ]] . /etc/bash.bashrc
elif [[ -n ${KSH_VERSION} ]]; then
elif [[ -n ${ZSH_VERSION} ]]; then
$
Corrected. Included in the next release.
Is it reasonable to presume a quick turnaround on a fix?
Yes. It will be available ASAP.
--
Huella de clave primaria: 0FDA C36F F110 54F4 D42B D0EB 617D 396C 448B 31EB
signature.asc
Description: Digital signature
Problems with terminal doesn't display visual elements properly
Hello. I need some help. My terminal started with a very strange behavior today. Many programs are not displaying correctly and I don't know why. I uploaded this picture: http://img851.imageshack.us/i/screenshotfc.png/ The two windows at the top are displaying the nano and top programs using putty. The two windows at the bottom are displaying the same programs using cygwin, respectively. As you can see, the visual of the applications is different, and that's not all. I'm really not able to work with these applications because of this problem. Actually, any visual enhancement is not working properly. Even grep with --color option isn't working correctly. In the image, both programs are connected to the same server thru ssh, so IMO the problem is not related with server configuration or any tool specific setting. The problem also occurs when using cygwin in the local machine. I'm almost sure the problem is related with the dos emulator, but I don't have an idea whats wrong. The problem started when I did the last cygwin update (but I also updated many programs in the machine together, so I don't know if cygwin caused this). Does anybody have guess? Any help is appreciated. Regards, --- Diego Queiroz -- 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: Problems with the new base-files-4.0-5?
David Sastre wrote:
Please test if
[ -e ${p} ] read -r PRINTER ${p} PRINTER=${PRINTER%%,*}
No, I think.
I get:
$ cat test_pr.sh
#!/bin/bash
p='/proc/registry/HKEY_CURRENT_USER/Software/Microsoft/Windows
NT/CurrentVersion/Windows/Device'
[ -e ${p} ] read -r PRINTER ${p} PRINTER=${PRINTER%%,*}
echo 'echo $PRINTER'
echo $PRINTER
$ ./test_pr.sh
echo $PRINTER
HP Deskjet 3740 Series,winspool,Ne03:
--^^^
which is *wrong*. See ^^^ above!
With base-files-4.0-4 I get:
$ echo $PRINTER
HP Deskjet 3740 Series
which is right.
Ciao,
Angelo.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Problems with the new base-files-4.0-5?
On Thu, Mar 17, 2011 at 11:43:26PM +0100, Angelo Graziosi wrote:
David Sastre wrote:
Please test if
[ -e ${p} ] read -r PRINTER ${p} PRINTER=${PRINTER%%,*}
No, I think.
I get:
$ cat test_pr.sh
#!/bin/bash
p='/proc/registry/HKEY_CURRENT_USER/Software/Microsoft/Windows
NT/CurrentVersion/Windows/Device'
[ -e ${p} ] read -r PRINTER ${p} PRINTER=${PRINTER%%,*}
echo 'echo $PRINTER'
echo $PRINTER
$ ./test_pr.sh
echo $PRINTER
HP Deskjet 3740 Series,winspool,Ne03:
--^^^
which is *wrong*. See ^^^ above!
With base-files-4.0-4 I get:
$ echo $PRINTER
HP Deskjet 3740 Series
which is right.
Ciao,
Angelo.
Thanks for testing.
It looks like it's easier to solve this with a simple if statement.
p='/proc/registry/HKEY_CURRENT_USER/Software/Microsoft/Windows
NT/CurrentVersion/Windows/Device'
if [ -e ${p} ] ; then
read -r PRINTER ${p}
PRINTER=${PRINTER%%,*}
fi
--
Huella de clave primaria: 0FDA C36F F110 54F4 D42B D0EB 617D 396C 448B 31EB
signature.asc
Description: Digital signature
Re: Problems with the new base-files-4.0-5?
On Fri, Mar 18, 2011 at 12:07:43AM +0100, David Sastre wrote:
On Thu, Mar 17, 2011 at 11:43:26PM +0100, Angelo Graziosi wrote:
David Sastre wrote:
Please test if
[ -e ${p} ] read -r PRINTER ${p} PRINTER=${PRINTER%%,*}
No, I think.
I get:
$ cat test_pr.sh
#!/bin/bash
p='/proc/registry/HKEY_CURRENT_USER/Software/Microsoft/Windows
NT/CurrentVersion/Windows/Device'
[ -e ${p} ] read -r PRINTER ${p} PRINTER=${PRINTER%%,*}
echo 'echo $PRINTER'
echo $PRINTER
$ ./test_pr.sh
echo $PRINTER
HP Deskjet 3740 Series,winspool,Ne03:
--^^^
which is *wrong*. See ^^^ above!
With base-files-4.0-4 I get:
$ echo $PRINTER
HP Deskjet 3740 Series
which is right.
Ciao,
Angelo.
Thanks for testing.
It looks like it's easier to solve this with a simple if statement.
p='/proc/registry/HKEY_CURRENT_USER/Software/Microsoft/Windows
NT/CurrentVersion/Windows/Device'
if [ -e ${p} ] ; then
read -r PRINTER ${p}
PRINTER=${PRINTER%%,*}
fi
How about:
read -r -d, PRINTER
'/proc/registry/HKEY_CURRENT_USER/Software/Microsoft/Windows
NT/CurrentVersion/Windows/Device'
I see that -d is available in ksh but I don't know about the other shells.
cgf
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Problems with the new base-files-4.0-5?
Le 17/03/2011 23:43, Angelo Graziosi a écrit :
p='/proc/registry/HKEY_CURRENT_USER/Software/Microsoft/Windows
NT/CurrentVersion/Windows/Device'
[ -e ${p} ] read -r PRINTER ${p} PRINTER=${PRINTER%%,*}
read -r $p returns 1 bcoz The return code is zero, unless end-of-file
is encountered...
alternative :
[ -e ${p} ] IFS=',' read -r PRINTER dummy ${p}
Regards,
Cyrille Lefevre
--
mailto:cyrille.lefevre-li...@laposte.net
--
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: Cygport woes: CHOST not defined.
On Thu, 2011-03-17 at 19:39 +, Dave Korn wrote: Attempting to rebuild gcc4-4.3.4-3 from source, I got a bunch of error messages during the install stage of cygport: [ ... snip several more ... ] Looking at the context, I infer that CHOST must be undefined: ... and quite likely CBUILD as well: Yes, CBUILD, CHOST, and CTARGET are used internally to support cygport's various cross-compiling scenarios. At some point I may make them public, but either way they should be considered read-only. BTW, do you need me to resend my patches for 4.5.2? Yaakov -- 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: Cygport woes: CHOST not defined.
On 18/03/2011 02:50, Yaakov (Cygwin/X) wrote: On Thu, 2011-03-17 at 19:39 +, Dave Korn wrote: Attempting to rebuild gcc4-4.3.4-3 from source, I got a bunch of error messages during the install stage of cygport: [ ... snip several more ... ] Looking at the context, I infer that CHOST must be undefined: ... and quite likely CBUILD as well: Yes, CBUILD, CHOST, and CTARGET are used internally to support cygport's various cross-compiling scenarios. At some point I may make them public, but either way they should be considered read-only. Indeed. Can't remember what the long-ago bug was I ran into that made me think unsetting it in the .cygport was the best solution, but the point is moot anyway. BTW, do you need me to resend my patches for 4.5.2? Couldn't hurt, I know I had some stuff to dig through my inbox looking for but if you wouldn't mind... g Once I've got linker plugin stuff sorted out upstream for gcc-4.6/binutils-2.21.1, I'll build a 4.5.2 for the distro (and promote it to curr, leaving 4.3.4-4 as prev) then start working on a 4.6.0 test package. cheers, DaveK -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: ld: fatal error - cmalloc would have returned NULL
On 11/03/2011 13:53, Rainer Emrich wrote: I have to be more clear. I increased the heap_chunk_in_mb to 1792 using: regtool -i set /HKLM/Software/Cygwin/heap_chunk_in_mb 1792 I run with this setting all the time, I guess that's why I haven't seen this problem. Before I did that (couple of years back) I also used to get crashes building libjava. (I'm sure there is an underlying inefficiency in ld's memory usage, and I suspect it might relate to comdat handling, 4.6 generating way more of them than earlier 4.x versions.) cheers, DaveK -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Updated: {serf,libserf0_1,libserf0-devel}-0.7.1-1
The serf packages have been updated to the new upstream release 0.7.1. See http://code.google.com/p/serf/source/browse/tags/0.7.1/CHANGES for more details about the changes in this release. More information about serf can be found at http://code.google.com/p/serf/. CYGWIN NOTES: = The 0.7.0 release increased the version of the libserf0 library from 0 to 1, so libserf0_0 and libserf0_1 may be installed in parallel. This is necessary because applications linked against serf 0.3.x will not run with serf 0.7.x and vice versa. Note that upstream did not increase the library version. Please note that 0.7.x is not API-compatible with 0.3.x. Applications compiled against 0.3.x may require changes to compile against 0.7.x. DESCRIPTION: The serf library is a C-based HTTP client library built upon the Apache Portable Runtime (APR) library. It multiplexes connections, running the read/write communication asynchronously. Memory copies and transformations are kept to a minimum to provide high performance operation. DOWNLOAD: = Note that downloads from sources.redhat.com (aka cygwin.com) aren't allowed due to bandwidth limitations. This means that you will need to find a mirror which has this update, please choose the one nearest to you: http://cygwin.com/mirrors.html QUESTIONS: == If you want to make a point or ask a question the Cygwin mailing list is the appropriate place. CYGWIN-ANNOUNCE UNSUBSCRIBE INFO: = To unsubscribe to the cygwin-announce mailing list, look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-YOU=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- David Rothenberger daver...@acm.org
Updated: subversion-1.6.16-1
A new version of subversion is available. This is a new upstream release. NEWS: = See CHANGES (URL below) for more information about the differences between 1.6.16 and previous Subversion releases. In addition to the normal collection of bug fixes, and stability enhancements, this release also addresses CVE-2011-0715, a remotely-triggerable DoS for httpd-based Subversion servers. More information can be found in the advisory: http://subversion.apache.org/security/CVE-2011-0715-advisory.txt IMPORTANT: This release will silently upgrade your Subversion working copies to the 1.6 format, rendering them unusable with previous major versions of Subversion. Please see the release notes http://subversion.apache.org/docs/release-notes/1.6.html for more details about the changes in Subversion. See http://svn.apache.org/repos/asf/subversion/tags/1.6.16/CHANGES for more details about the changes in 1.6.16. DESCRIPTION: Subversion is a version control system designed to be a compelling successor to CVS. Please see http://svnbook.red-bean.com/en/1.5/index.html for the latest official release of the Subversion Book, covering 1.5 or http://svnbook.red-bean.com/nightly/en/index.html for the WIP version of the book covering 1.6. DOWNLOAD: = Note that downloads from sourceware.org (aka cygwin.com) aren't allowed due to bandwidth limitations. This means that you will need to find a mirror which has this update, please choose the one nearest to you: http://cygwin.com/mirrors.html QUESTIONS: == If you want to make a point or ask a question the Cygwin mailing list is the appropriate place. CYGWIN-ANNOUNCE UNSUBSCRIBE INFO: = To unsubscribe to the cygwin-announce mailing list, look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-YOU=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- David Rothenberger daver...@acm.org
