1.7.0 sem_open
Does the function sem_open work for anyone using Cygwin 1.7.0 ? How to use semtool ? I wrote an example that works on Jaunty on x86-64 but not on Cygwin: http://www.izecksohn.com/pedro/c/semaphores/semaphores.tar.gz Also: gcc4 does not understand the option "-lrt" so it must be removed. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: FW: OpenSSH server installation error on Windows Vista Business/Ultimate
What's your trouble? 2009/6/12 David Christensen : > cygwin: > > I installed a fresh copy of Cygwin and a fresh copy of the Cygwin > OpenSSH service on a fresh installation of Windows Vista Ultimate SP1 > 32-bit yesterday: > > 1. Download Cygwin Setup to C:\cygwin\setup\setup.exe. > > 2. Run Cygwin Setup: > > a. Install from Internet (default). > > b. C:\cygwin root directory (default). > > c. Install for all users (default). > > d. Unix/ binary default text file type (default). > > e. C:\cygwin\setup local package directory (default). > > f. Direct connection to Internet (default). > > g. ftp://mirrors.kernel.org download site. > > h. Select source packages to match base/ default packages. > > i. Create Desktop and Start menu shortcuts. > > 3. Start Cygwin Bash Shell, then exit it. > > 4. Run Cygwin Setup again: > > a-g. Same as above. > > h. Select 'openssh' package. Setup will select dependencies. > Select source packages for all of these. > > i. No need to recreate shortcuts. > > 5. Start Cygwin Bash Shell and wrestle with ssh-host-config, 'net start > sshd', and /var/log/sshd.log, rebooting several times along the way for > the sake of paranoia. In the end, I need to make four system changes to > get sshd working: > > a. 'chmod 0777 /etc/passwd' -- overkill, so that ssh-host-config > could create the cyg_server account. (I changed permissions to 0644 > afterwards.) > > b. 'chmod 0777 /etc/group' -- more overkill for ssh-host-config. > (I changed permissions to 0644 afterwards.) > > c. 'chmod 0777 /var' -- more overkill for ssh-host-config. (I left > it that way.) > > d. 'chown cyg_server /var/empty' -- necessary to start the sshd > service. > > > HTH, > > David > > > -- > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > Problem reports: http://cygwin.com/problems.html > Documentation: http://cygwin.com/docs.html > FAQ: http://cygwin.com/faq/ > > -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
[ANNOUNCEMENT] [1.7] Updated: pcre-7.9-1
The following packages have been updated for Cygwin 1.7:
* pcre/libpcre0/libpcre-devel/libpcrecpp0/libpcrecpp-devel: 7.9-1
This is an update to the latest upstream release.
These packages were built with gcc-4.3. The C++ library runtime and
devel packages, which now depend on libstdc++6{,-devel} have been split out.
Yaakov
CYGWIN-ANNOUNCE UNSUBSCRIBE INFO
If you want to unsubscribe from the cygwin-announce mailing list, please
use the automated form at:
http://cygwin.com/lists.html#subscribe-unsubscribe
If this does not work, then 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.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
Re: Using emacs in a terminal window
> I'd say it's a bug that the rxvt max_colors entry is 8, since rxvt > does support 256 colours in its default setting. (And I notice it's > the same with xterm.) Don't know whether there are compatibility > concerns that require that. Just to be clear, the default terminfo capability for Cygwin rxvt is rxvt-cygwin-native, and that is what I used for comparison. There is no corresponding 'rxvt-cygwin-256color'. > However, the correct way to address this is to set TERM to > rxvt-256color (or xterm-256color, as appropriate) rather than > Eterm-256color. That sounds reasonable and appears to be a really good suggestion (even if there is no 'rxvt-cygwin-256color'). I tried it and found that it appears to give a color/font/underlining capability identical to Eterm-256color, but it fixes a defect in Eterm-256color, namely, the mode line was not being shaded appropriately depending on which window in the frame was active. Using TERM=rxvt-256color, the mode-line highlighting now follows the active window, as expected. This appears to be the best default TERM setting for terminal-mode Emacs running in Cygwin (native) rxvt. env TERM=rxvt-256color emacs -nw ... Thank you for the suggestion! I will leave it to regular mintty+Emacs users to suggest the best default TERM setting for that terminal emulator. --- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
FW: OpenSSH server installation error on Windows Vista Business/Ultimate
cygwin: I installed a fresh copy of Cygwin and a fresh copy of the Cygwin OpenSSH service on a fresh installation of Windows Vista Ultimate SP1 32-bit yesterday: 1. Download Cygwin Setup to C:\cygwin\setup\setup.exe. 2. Run Cygwin Setup: a. Install from Internet (default). b. C:\cygwin root directory (default). c. Install for all users (default). d. Unix/ binary default text file type (default). e. C:\cygwin\setup local package directory (default). f. Direct connection to Internet (default). g. ftp://mirrors.kernel.org download site. h. Select source packages to match base/ default packages. i. Create Desktop and Start menu shortcuts. 3. Start Cygwin Bash Shell, then exit it. 4. Run Cygwin Setup again: a-g. Same as above. h. Select 'openssh' package. Setup will select dependencies. Select source packages for all of these. i. No need to recreate shortcuts. 5. Start Cygwin Bash Shell and wrestle with ssh-host-config, 'net start sshd', and /var/log/sshd.log, rebooting several times along the way for the sake of paranoia. In the end, I need to make four system changes to get sshd working: a. 'chmod 0777 /etc/passwd' -- overkill, so that ssh-host-config could create the cyg_server account. (I changed permissions to 0644 afterwards.) b. 'chmod 0777 /etc/group' -- more overkill for ssh-host-config. (I changed permissions to 0644 afterwards.) c. 'chmod 0777 /var' -- more overkill for ssh-host-config. (I left it that way.) d. 'chown cyg_server /var/empty' -- necessary to start the sshd service. HTH, David -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
[ANNOUNCEMENT] [1.7] Updated: clamav-0.95.2-1
I've made a new version of 'clamav' available for installation. This update is only available for the Cygwin 1.7 beta. Project description: Clam AntiVirus is an anti-virus toolkit designed especially for email scanning on mail gateways. It provides a number of utilities, including a flexible and scalable multi-threaded daemon, a commandline scanner, and a tool for automatic database updates. The core of the package is an anti-virus engine available as a shared library. *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then 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. == Cygwin changes: - version 0.95.2-1 - * fixed libcurl4 dependency * added -Ilibclamav to clamdtop * exchanged main.clv with updated main.cld * exchanged daily.clv with updated daily.cld - version 0.95.1-2 - libclamav6 * added -shared-libgcc * renamed DATADIR to CLAMAV_DATADIR because of clash with objidl.h * adapted libclamav6.hint dependencies * fixed dlopen "libclamunrar_iface" - version 0.95-1 - cygwin-1.7, gcc-4 Upstream changes: 0.95.2 This version improves handling of archives, adds support for --file-list in clamscan and clamdscan, and fixes various issues found in previous releases. 0.95 This release introduces many bugfixes, improvements and additions. Key features include Google Safe Browsing support, a new clamav-milter, and clamd extensions. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Garbage man pages
Hello, There's something wrong with my man pager; it's producing garbage output. My ~/.bashrc has these entries: export MANPAGER='less -isrR' export PAGER='less -r' Thanks, Bill -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: managing autoconf versions?
Spiro Trikaliotis wrote: > Hello Jay, > > * On Thu, Jun 11, 2009 at 07:02:00AM + Jay wrote: > > >>Dave, thanks, it is exactly binutils/gcc I'm interested in. >>Thank you for proving I'm not crazy -- there really is a problem. As your attorney, I advise you to take the fifth! >>Could be due to your work that cygwin is the best/easiest platform >>here (but so slow to fork. :( ). Ah, flattery. Actually, it's *bribery* that will get you everywhere, but a bit of flattery always helps the process along. >>I was/am not aware of what the version macros achieve. >>You know, I mean...ignoring binutils/gcc, though they are relevant, >>would I install versions 1.1, 1.2, 1.3, etc. (made up versions) >>all to different prefix, put all the prefixes/bin in $PATH and >>the version macros search $PATH? >>Or do all the tools append versions to all their directories/files? >> >> >>You know, ideally..ideally what I would do is >>download "every" version of autoconf/automake >>configure and install them all with no flags >>put /usr/local/bin in $PATH >>and as long as I defined "every" correct/sufficient, be able to >>make arbitrary edits to arbitrary projects, and just run >>the usual configure+make on them and the right thing would happen. >> >>Or even, better yet, error if I don't have the matching version >>of autoconfigure/automake, perhaps guided by a flag one way >>or the other. E have you ever actually looked at the selection of automake and autoconf packages in the cygwin distro? What we already have is largely what you describe above. cheers, DaveK -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Using emacs in a terminal window
> Here are some differences between the terminfo capabilities > 'rxvt-cygwin-native' and 'Eterm-256color': > > 1. max_colors: > rxvt - max_colors: 8 > Eterm - max_colors: 256 I'd say it's a bug that the rxvt max_colors entry is 8, since rxvt does support 256 colours in its default setting. (And I notice it's the same with xterm.) Don't know whether there are compatibility concerns that require that. However, the correct way to address this is to set TERM to rxvt-256color (or xterm-256color, as appropriate) rather than Eterm-256color. > We do not want to limit Emacs to 8 colors, and having > Eterm-256color set the value to 256 does not cause > any problem for rxvt. Presumably the emacs authors have learned from bitter experience that the various terminal capability mechanisms can't be relied upon and simply hardcoded the keycodes for the most popular terminals. Also, many terminal emulators (and their version) can be identified through the so-called "secondary device attribute" control sequence. > 4. key_a1, key_a3, key_c1, key_c3: > These are the Home/PgUp/PgDn/End keys > > rxvt - \E0w, \E0y, \E0q, \E0s > Eterm - \E[7~, \E[5~, \E[8~, \E[6~ > > Does this difference in key definitions matter in > Cygwin's terminal-mode Emacs running in rxvt? > > No. It may not matter for emacs, but it probably would e.g. for ncurses programs which rely on terminfo information much more. Andy -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Using emacs in a terminal window
> Yes, but nevertheless the TERM setting needs to fit the terminal that > Emacs is actually running in, so "rxvt" (or some variation thereof) > for rxvt and "xterm" for xterm or mintty. As Ken said, the "Eterm" > setting is intended for programs that run inside emacs' builtin > terminal. Using "Eterm*" outside that might appear to work because > many of its capabilities will be the same as with other terminals, but > there will also be things that don't fit. Let's consider the case of the Cygwin Bash Shell (which runs the batch file 'cygwin.bat'). In this case, we do not want to set TERM (which defaults to 'cygwin') to 'Eterm-256color'. If we do, then terminal-mode emacs will attempt to use capabilities that Cygwin bash running inside cmd.exe does not support. So, the general principal of not exceeding the capabilities of the terminal that the application is running in is correct. Similarly, if we were running Emacs in a physical terminal, then we would need to be careful to tell Emacs about the correct set of control strings to send to the terminal. Of course, we are not generally, with Cygwin, running Emacs on a physical terminal so we do not have the restrictions of, say, a VT100. Leaving aside the very limited Cygwin Bash Shell and physical terminals, do the Cygwin terminal emulators have some capabilities that 'Eterm-256color' restricts, or, conversely, does 'Eterm-256color' attempt to use some capability that the terminal emulators do not support? If so, then I would like to know what they are. Here are some differences between the terminfo capabilities 'rxvt-cygwin-native' and 'Eterm-256color': 1. max_colors: rxvt- max_colors: 8 Eterm - max_colors: 256 We do not want to limit Emacs to 8 colors, and having Eterm-256color set the value to 256 does not cause any problem for rxvt. 2. auto_left_margin: rxvt- False Eterm - True So, when you reach the left margin in rxvt, it will not automatically wrap back to the previous line. In Eterm, you will. Does it matter for Emacs? No. 3. key_f0 / key_help: rxvt- key_f0: \E[21~, key_help: NULL Eterm - key_f0: NULL, key_help: \E28~ So, rxvt defines a Function key 0, which most modern keyboards do not have, correct? And Eterm defines the "Help" key, which modern keyboards do not have (this is not the F1 key). Neither key matters for Emacs. 4. key_a1, key_a3, key_c1, key_c3: These are the Home/PgUp/PgDn/End keys rxvt - \E0w, \E0y, \E0q, \E0s Eterm - \E[7~, \E[5~, \E[8~, \E[6~ Does this difference in key definitions matter in Cygwin's terminal-mode Emacs running in rxvt? No. A test reveals that Emacs translates the keycodes to the same control-char sequence regardless of whether Emacs is started with TERM set to 'rxvt-cygwin-native' or 'Eterm-256color': Home: ^[[7~ PgUp: ^[[5~ PgDn: ^[[6~ End: ^[[8~ I am attaching to this message a complete listing of the differences between the 'rxvt-cygwin-native' and the 'Eterm-256color' terminfo capability files. Please let me know if there is some critical capability that 'rxvt-cygwin-native' provides that 'Eterm-256color' lacks, or, conversely, if 'Eterm-256color' exceeds some capability of 'rxvt-cygwin-native' which results in defective behavior by Emacs. I would really like to know. Here are three reasons for using 'env TERM=Eterm-256color emacs...': 1. More distinct visual elements can be seen in Emacs's display. (I described what some of these were in a previous message.) The developers of Emacs have written it to make these elements available to provide information that would not be available otherwise. In general, we want to provide to Emacs the maximum number of terminal capabilities that we can so that the code can make use of those capabilities instead of using a lowest-common-denominator capability. 2. The appearance of terminal-mode Emacs more closely matches the default display of "native-mode, windowing" Emacs (either MS-Windows or X-Windows). 3. There is the possibility of a more consistent display across different terminal emulators (assuming that the terminal emulators will support the Eterm-256color capabilities). We now come back to the "judgement" question: In terminal- mode Emacs under Cygwin, would it be a better default for it to be started with TERM set to 'Eterm-256color'? If not, then -- specifically -- why not? What defects appear, that outweigh the benefits listed above? I would like to know what those are. And it would be helpful if replies were confined to those users who actually use terminal-mode Emacs, and who use it with the suggested TERM setting, preferably in 'rxvt', 'mintty', or 'screen' running in one of those terminal emulators. --- comparing rxvt-cygwin-native to Eterm-256color. comparing booleans. auto_left_margin: F:T. backspaces_with_bs: T:F. can_change: F:T. prtr_silent: F:T. comparing numbers. buttons: NULL, 5. lines_of_memory: NULL, 0. ma
Re: managing autoconf versions?
Hello Jay, * On Thu, Jun 11, 2009 at 07:02:00AM + Jay wrote: >[maybe should cc cygwin] Doing so. ;) For complete reference, I am citing your complete mail. As you do not seem to be subscribed, I am keeping you as a direct recipient, too. > Just noticed your guys's responses, searching >the web. Thanks. > >Spiro, I don't your answer of not including >generating files with the patch suffices. > - I think people do include them. I am doing open source projects myself. Whenever I get a patch where these generated files (auto*, bison, flex, ...) are included, I ask the sender to send a new copy without these files. There are really a pain in the ass! They are not worth the time it takes me to remove the patches. > - It is important to match versions for testing purposes. > If I test with a non matching autoconf/make, what they generate >won't likely match, and that invalidates testing. In my experience, these differences are seldom important. If they are, I will take such a patch, of course. >Dave, thanks, it is exactly binutils/gcc I'm interested in. >Thank you for proving I'm not crazy -- there really is a problem. >Could be due to your work that cygwin is the best/easiest platform >here (but so slow to fork. :( ). >I was/am not aware of what the version macros achieve. >You know, I mean...ignoring binutils/gcc, though they are relevant, >would I install versions 1.1, 1.2, 1.3, etc. (made up versions) >all to different prefix, put all the prefixes/bin in $PATH and >the version macros search $PATH? >Or do all the tools append versions to all their directories/files? > > >You know, ideally..ideally what I would do is >download "every" version of autoconf/automake >configure and install them all with no flags >put /usr/local/bin in $PATH >and as long as I defined "every" correct/sufficient, be able to >make arbitrary edits to arbitrary projects, and just run >the usual configure+make on them and the right thing would happen. > >Or even, better yet, error if I don't have the matching version >of autoconfigure/automake, perhaps guided by a flag one way >or the other. > > - Jay Best regards, Spiro. -- Spiro R. Trikaliotis http://opencbm.sf.net/ http://www.trikaliotis.net/ http://www.viceteam.org/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: setup-1.7 (2.627) and/or cygwin-1.7.0-49
On Thu, 11 Jun 2009 13:27 -0400, "Charles Wilson" wrote: > I'm now repeating my installation test, using the freshly rsync'ed > mirror, and a hand-edited copy of the "real" setup-2.ini into which I > grafted an entry for my "fake" requires-a-lot package. More later... Works perfectly, even with %HOME% set. Great job! -- Chuck 2009/06/11 13:32:04 Starting cygwin install, version 2.627 2009/06/11 13:32:04 io_stream_cygfile: fopen(/etc/setup/last-action) failed 2 No such file or directory 2009/06/11 13:32:04 io_stream_cygfile: fopen(/etc/setup/last-mirror) failed 2 No such file or directory 2009/06/11 13:32:04 io_stream_cygfile: fopen(/etc/setup/last-connection) failed 2 No such file or directory 2009/06/11 13:32:04 io_stream_cygfile: fopen(/etc/setup/last-cache) failed 2 No such file or directory 2009/06/11 13:32:04 io_stream_cygfile: fopen(/etc/setup/last-extrakeys) failed 2 No such file or directory 2009/06/11 13:32:04 Current Directory: C:\Documents and Settings\cwilso11\Desktop 2009/06/11 13:32:04 User has backup/restore rights 2009/06/11 13:32:04 Changing gid to Administrators 2009/06/11 13:32:04 Could not open service McShield for query, start and stop. McAfee may not be installed, or we don't have access. 2009/06/11 13:32:06 source: from cwd 2009/06/11 13:32:08 root: C:\cygwin-1.7 binary system 2009/06/11 13:32:08 io_stream_cygfile: fopen(/etc/setup/installed.db) failed 2 No such file or directory 2009/06/11 13:32:21 io_stream_cygfile: fopen(/etc/setup/last-cache) failed 2 No such file or directory 2009/06/11 13:32:21 Selected local directory: C:\TEMP\cygwin-mirror Found ini file - C:\TEMP\cygwin-mirror/setup-2.ini 2009/06/11 13:32:30 io_stream_cygfile: fopen(/etc/setup/timestamp) failed 2 No such file or directory ... 2009/06/11 13:48:40 Changing gid back to original Visited: 447 nodes out of 1461 while creating dependency order. Dependency order of packages: base-cygwin base-passwd cygwin ... deleted ... xsri zip fake libidn-devel libcurl-devel 2009/06/11 13:48:41 running: C:\cygwin-1.7\bin\bash.exe --norc --noprofile -c /etc/postinstall/000-cygwin-post-install.sh 2009/06/11 13:48:51 running: C:\cygwin-1.7\bin\bash.exe --norc --noprofile -c /etc/postinstall/passwd-grp.sh ... 2009/06/11 13:50:04 running: C:\cygwin-1.7\bin\bash.exe --norc --noprofile -c /etc/postinstall/xpdf.sh 2009/06/11 13:50:04 running: C:\cygwin-1.7\bin\bash.exe --norc --noprofile -c /etc/postinstall/fake-bash.sh inner: hB /etc/postinstall/fake-bash.sh shopt -u cdable_vars shopt -u cdspell shopt -u checkhash shopt -u checkwinsize shopt -s cmdhist shopt -u compat31 shopt -u dotglob shopt -u execfail shopt -u expand_aliases shopt -u extdebug shopt -u extglob shopt -s extquote shopt -u failglob shopt -s force_fignore shopt -u gnu_errfmt shopt -u histappend shopt -u histreedit shopt -u histverify shopt -s hostcomplete shopt -u huponexit shopt -u igncr shopt -s interactive_comments shopt -u lithist shopt -u login_shell shopt -u mailwarn shopt -u no_empty_cmd_completion shopt -u nocaseglob shopt -u nocasematch shopt -u nullglob shopt -s progcomp shopt -s promptvars shopt -u restricted_shell shopt -u shift_verbose shopt -s sourcepath shopt -u xpg_echo 1 1 1 1 SHELLOPTS=braceexpand:hashall:interactive-comments BASH_ENV= ENV= end inner 2009/06/11 13:50:04 Changing gid to Administrators 2009/06/11 13:51:54 note: Installation Complete 2009/06/11 13:51:54 Ending cygwin install -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: setup-1.7 (2.627) and/or cygwin-1.7.0-49
Charles Wilson said: > However, the installation was still a bit bolluxed -- mostly the > postinstall scripts still don't run correctly. ... > Ok, never mind. Somehow I got a bunch of bad versions. No idea how -- > but obviously these versions are NOT going to work with cygwin-1.7.0-XX > going forward. Maybe they should be removed from the release-2/ area? I see what the problem was, here -- it appears to be a bug in genini. >From a freshly-rsync'ed local mirror, here's what setup-2.ini has for gettext when generated by upset (e.g. on the "real" mirrors). I've deleted the ldesc: text. @ gettext sdesc: "GNU Internationalization library and core utilities (PLUS LINK LIBS)" ldesc: "deleted" category: Devel Libs requires: cygwin libintl8 libiconv2 _update-info-dir version: 0.17-11 install: release-2/gettext/gettext-0.17-11.tar.bz2 177957 e389da2d6e9ec9fe777affb87f82cfb0 source: release-2/gettext/gettext-0.17-11-src.tar.bz2 11693299 c1c2bd596c96e5e457c7d0d1c8d23c6f [prev] version: 0.17-10 install: release-2/gettext/gettext-0.17-10.tar.bz2 178235 a77c923b36ead2f4bec72d7345d57c70 source: release-2/gettext/gettext-0.17-10-src.tar.bz2 11693290 6fd68dd68400f92253a0e654416ba914 OTOH, here's what genini reports for my local mirror @ gettext sdesc: "GNU Internationalization library and core utilities (PLUS LINK LIBS)" ldesc: "deleted" category: Devel Libs requires: cygwin libintl8 libiconv2 version: 0.17-2 install: release-2/gettext/gettext-0.17-2.tar.bz2 181964 5b98eb7a98a4e860cb0510bd93e0a206 source: release-2/gettext/gettext-0.17-2-src.tar.bz2 11689423 0b0afd83cc6d85a3cb82de6a8d8c476c [prev] version: 0.17-11 install: release-2/gettext/gettext-0.17-11.tar.bz2 177957 e389da2d6e9ec9fe777affb87f82cfb0 source: release-2/gettext/gettext-0.17-11-src.tar.bz2 11693299 c1c2bd596c96e5e457c7d0d1c8d23c6f That seems...wrong. It seems like the problem is in genini's version-number comparison routines (alphabetic, rather than numerical?) but I have not yet dug in to genini's code. I'm now repeating my installation test, using the freshly rsync'ed mirror, and a hand-edited copy of the "real" setup-2.ini into which I grafted an entry for my "fake" requires-a-lot package. More later... -- Chuck -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: [ANNOUNCEMENT] [1.7] Updated: curl-7.19.4-1 (SECURITY)
> Date: Thu, 11 Jun 2009 00:09:34 -0500 > From: yselkowitz > Subject: [ANNOUNCEMENT] [1.7] Updated: curl-7.19.4-1 (SECURITY) > > I have updated curl to 7.19.4 for Cygwin 1.7. In addition to taking > advantage of the new capabilities of 1.7 (including IPv6), this update > includes a fix for CVE-2009-0037. > Why 7.19.4 instead of 7.19.5? Just curious? Thanks, ...Karl _ Insert movie times and more without leaving Hotmail®. http://windowslive.com/Tutorial/Hotmail/QuickAdd?ocid=TXT_TAGLM_WL_HM_Tutorial_QuickAdd_062009 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
[ANNOUNCEMENT] [1.7] Updated: asciidoc-8.4.5-1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A new version of the asciidoc package, asciidoc 8.4.5-1, is now available for download for those testing cygwin 1.7, replacing 8.4.4-1. I have left asciidoc 8.3.5-1 as current for cygwin 1.5. NEWS: = This is a new upstream release, with release notes listed below. See also the package documentation in /usr/share/doc/asciidoc/. DESCRIPTION: AsciiDoc is a text document format for writing short documents, articles, books and UNIX man pages. AsciiDoc files can be translated to HTML and DocBook markups using the asciidoc(1) command. AsciiDoc is highly configurable: both the AsciiDoc source file syntax and the backend output markups (which can be almost any type of SGML/XML markup) can be customized and extended by the user. UPDATE: === To update your installation, click on the "Install Cygwin now" link on the http://cygwin.com/ web page. This downloads setup.exe to your system. Save it and run setup, answer the questions and pick up 'asciidoc' from the 'Devel' category. 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. - -- Eric Blake volunteer cygwin asciidoc maintainer CYGWIN-ANNOUNCE UNSUBSCRIBE INFO: = To unsubscribe to the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkow8e0ACgkQ84KuGfSFAYB74wCfYUCbKpVwNJnyCSn19AnAEa0m ny8AoKdryNiL1ClJtEscSQAsV1RNicXT =ymIz -END PGP SIGNATURE- 1. Version 8.4.5 (2009-05-24) Additions and changes * Added manpage Name and Synopsis section title customization to languages configuration files. * Synopsis manpage section no longer mandatory. * Section markup templates can be specified by setting the title's first positional attribute or template attribute. * The article and book document header can now include a revision remark. * A role attribute can now be applied to block elements. This adds the role attribute to DocBook elements. Patch submitted by [1]Noah Slater). * Renamed revision and date attributes to more sensible and consistent revnumber and revdate (old names deprecated but still recognized). * Moved backend specific attributes to Appendix H in User Guide. * Renamed and generalized the docbook backend revision history inclusion mechanism to docinfo to reflect the use of all article or book information elements. The old revision history names still work but have been deprecated. * Refactored docbook.conf headers. * Moved line break replacement from [replacements] to [replacements2] so the replacement occurs after the mailto macro. This fixes bug [2]http://groups.google.com/group/asciidoc/browse_thread/thread/4bd cdfb0af773e2 * The typewriter to punctuation apostrophe replacement can be escaped with a backslash. * Graphviz filter outputs images to imagesdir if it is defined. * Made the block image macro generic so that it can be used for filter outputs. As a result Music and Graphviz filters: + Have been greatly simplified. + Honor the data-uri attribute. + html4 outputs no longer generate W3C validation warning. * The iconsdir attribute no longer requires a trailing directory separator character. * Removed borders around linked html4 images. * Added html4 specific HTML output for music filter. * a2x: Added --unsafe option (shortcut for --asciidoc-opts=--unsafe). * a2x: The FOP executable can now be named fop (this is the default name in some distributions). * Attributes are now substituted in the system macro attribute list. * If the output is set to stdout (i.e. no output directory is defined) then Music and Graphviz filters will output included images to the source file directory. * Added name directive to testasciidoc. * Added lots of testasciidoc new tests. * Moved language specific configuration parameters into lang-en.conf file. * lang at
[ANNOUNCEMENT] [1.7] Updated: clamav-0.95.1-2
I've made a new version of 'clamav' available for installation. 0.95.2 just released yesterday is in the works. This update is only available for the Cygwin 1.7 beta. Project description: Clam AntiVirus is an anti-virus toolkit designed especially for email scanning on mail gateways. It provides a number of utilities, including a flexible and scalable multi-threaded daemon, a commandline scanner, and a tool for automatic database updates. The core of the package is an anti-virus engine available as a shared library. *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then 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. == Cygwin changes: - version 0.95.1-2 - libclamav6 * added -shared-libgcc * renamed DATADIR to CLAMAV_DATADIR because of clash with objidl.h * adapted libclamav6.hint dependencies * fixed dlopen "libclamunrar_iface" - version 0.95-1 - cygwin-1.7, gcc-4 Upstream changes: cygwin support silently dropped, so I have to carry along the src patches. This release introduces many bugfixes, improvements and additions. Key features include Google Safe Browsing support, a new clamav-milter, and clamd extensions. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Using emacs in a terminal window
> No, when Emacs is run in terminal (text-only, non-X-windows) > mode, it will use whatever terminal capability is in effect, > not only in `term-mode'. Yes, but nevertheless the TERM setting needs to fit the terminal that Emacs is actually running in, so "rxvt" (or some variation thereof) for rxvt and "xterm" for xterm or mintty. As Ken said, the "Eterm" setting is intended for programs that run inside emacs' builtin terminal. Using "Eterm*" outside that might appear to work because many of its capabilities will be the same as with other terminals, but there will also be things that don't fit. Andy -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Using emacs in a terminal window
Ken Brown writes: >- xterm: Invoke xterm with -xrm *backarrowKey:false or put > 'XTerm*backarrowKey: false' in your .Xdefaults file. Once xterm > is started, give the command 'stty erase ^?'. (These > suggestions are only relevant if you invoke emacs with the -nw > option in an xterm window or if you have not installed > emacs-X11.) I have used the following for a long time: XTerm*vt100.translations: #override BackSpace: string(0x7f) XTerm*ttyModes: erase ^? intr ^C I also have "stty erase ^?" in .bashrc -- Fredrik Stax\"ang | rot13: s...@hcqngr.hh.fr This is all you need to know about vi: ESC : q ! RET -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
