Re: [ANNOUNCEMENT] Updated: cygcheck-dep-1.1-1
On Fri, 15 Nov 2013 11:28:34 +1100 Luke Kendall <...> wrote: > On 11/15/2013 09:06 AM, Mikhail Usenko wrote: > >* A warning is printed out if an installed package denotes a required > > package which is not installed. > I assume this means: a warning is printed if an installed package > depends on a required package that is not installed. > > I assumed setup installed required packages for all the packages you'd > selected, so I'm curious. -- Yep. This is just an internal checking, since this silently was skipped earlier. -- 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: cygport-0.14.1-1
I have just released cygport-0.14.1 for the Cygwin distributions and the Fedora Cygwin repository. Notable changes in this release include: * $PAGER (e.g. less) is now used to display 'list', 'listdebug', and 'info' information on the console. This variable can be set in your environment (as it is used by other programs as well) or in your cygport.conf. * Added -Wimplicit-function-declaration to CFLAGS/OBJCFLAGS to help detect potential crashers on x86_64-cygwin. * setup.hint auto-generation no longer requires [PKG_]REQUIRES on Linux. * Generated patches now preserve original line endings. * Various bugfixes. Changes in this release (14): doc: clarify --exclude in PKG_CONTENTS pkg_diff: preserve line endings in generated diffs autotools: pass --htmldir in cygconf autotools: assure automake-1.9 with libtool pkg_info: use pager for displaying information perl: fix compatibility with Module::Build::Tiny autotools: fix for multiple calls of cygautoreconf Do not replace symlinks with copies for MinGW/MSYS/DJGPP qt4-qconf: call cygqmake4 to respect CXX/CXXFLAGS/etc. Guard textual greps from l10n apache2: fix postinstall for x86_64 Add -Wimplicit-function-declaration to CFLAGS/OBJCFLAGS Do not require REQUIRES for setup.hint generation on Linux cygport 0.14.1 -- Yaakov Cygwin/X 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. -- 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: build library libmad
Thanks for the helpful information. >honeycomb (2013/11/15 1:01), > > Building libmad > > > > I download an attempted to build libmad-0.15.1b. with the build shared > > option set. > > > > Options to --force-mem and addr were deleted as unneccessary anymore. > > > > The configure and make process proceed without any errors. > > > > But, no dll is made. I can only see .lo files and one libmad.la > > > > > > Has anyone there had experience with getting a dll available for use? > > You have to add -no-undefined to libmad_la_LDFLAGS in Makefile.am. > Alternatively, you can try this: > https://github.com/nu774/libmad > > -- -- 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: Intermittent failures retrieving process exit codes
On 2013-11-14 05:01, Tom Honermann wrote: > On 12/21/2012 01:30 AM, Tom Honermann wrote: >> >> The workaround I implemented within Cygwin was simple and sloppy. I >> added a call to Sleep(1000) immediately before the call to ExitThread() >> in wait_sig() in winsup/cygwin/sigproc.cc. Since this thread (probably) >> doesn't exit until the process is exiting anyway, the call to Sleep() >> does not adversely affect shutdown. The thread just gets terminated >> while in the call to Sleep() instead of exiting before the process is >> terminated or getting terminated while still in the call to >> ExitThread(). A better solution might be to avoid the thread exiting at >> all (so long as it can't get terminated while holding critical >> resources), or to have the process exiting thread wait on it. Neither >> of these is ideal. Orderly shutdown of multi-threaded processes is >> really hard to do correctly on Windows. I experience on Windows 7 (not on XP) some problems that may be related. I would like to test your workaround, but sigproc.cc has much changed since then, there is now an exit_thead function with the comment "Exit the current thread very carefully.". I tried to insert Sleep(1000) at the end of exit_thread, immediately before "ExitThread (0)", but this yielded no change at all. Could someone be kind enough to update the workaround for modern sigproc.cc? Very briefly, my problem is that when i "tar xf —use-compress-program=xz", i get: tar: Unexpected EOF in archive tar: Unexpected EOF in archive tar: Error is not recoverable: exiting now and the last file of the archive is truncated at some 512bytes block. This occurs on Windows 7 (not on XP); with xz-5.1.3alpha (not with xz-5.1.2alpha or xz-5.0.5); never on most tar.xz files; almost always on some (rare) tar.xz files (one notable example is bc-1.06.95.tar.bz2 bunzip2’ed and then xz’ed); depends on the .tar file itself, not on the option (like -9e, -0) used to create the .tar.xz; never with "tar tf"; and with all tar’s i have tested. The return code of all the involved xz -d commands is always zero though. Perhaps after all, this is unrelated? Thank you. Regards, Denis Excoffier. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Intermittent failures retrieving process exit codes
On Fri, Nov 15, 2013 at 07:53:26PM +0100, Denis Excoffier wrote: >On 2013-11-14 05:01, Tom Honermann wrote: >> On 12/21/2012 01:30 AM, Tom Honermann wrote: >>> >>> The workaround I implemented within Cygwin was simple and sloppy. I >>> added a call to Sleep(1000) immediately before the call to ExitThread() >>> in wait_sig() in winsup/cygwin/sigproc.cc. Since this thread (probably) >>> doesn't exit until the process is exiting anyway, the call to Sleep() >>> does not adversely affect shutdown. The thread just gets terminated >>> while in the call to Sleep() instead of exiting before the process is >>> terminated or getting terminated while still in the call to >>> ExitThread(). A better solution might be to avoid the thread exiting at >>> all (so long as it can't get terminated while holding critical >>> resources), or to have the process exiting thread wait on it. Neither >>> of these is ideal. Orderly shutdown of multi-threaded processes is >>> really hard to do correctly on Windows. > >I experience on Windows 7 (not on XP) some problems that may be related. >I would like to test your workaround, but sigproc.cc has much changed since >then, there is now an exit_thead function with the comment "Exit the current >thread very carefully.". I tried to insert Sleep(1000) at the end of >exit_thread, immediately before "ExitThread (0)", but this yielded no >change at all. > >Could someone be kind enough to update the workaround for modern sigproc.cc? You apparently are misunderstanding the whole point of the changes to sigproc.cc. They were to work around this very problem. 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
[ANNOUNCEMENT] Updated: {tcp_wrappers/libwrap0/libwrap-devel}-7.6-22
tcp_wrappers provides host-based access restrictions on tcp services: facilities for monitoring and filtering incoming requests for the SSHD, SYSTAT, FINGER, FTP, TELNET, RLOGIN, RSH, EXEC, TFTP, TALK, and other network services. The package provides a tiny daemon wrapper program that can be installed without any changes to existing software or to existing configuration files. The wrappers report the name of the client host and of the requested service; the wrappers do not exchange information with the client or server applications, and impose no overhead on the actual conversation between the client and server applications. This is a routine update that adds a debuginfo package, and supports cygwin64. CHANGES (since 7.6-21) o Rely on cygport to autogenerate setup.hints o Added debuginfo package o First cygwin64 release A reminder for package maintainers and developers: STRONGSYMS: the cygwin versions of cygwrap-0.dll AND libwrap.a (that is, both the DLL and static library) explicitly provide int deny_severity int allow_severity symbols. This means that clients must NOT define their own versions of these symbols, as is the practice on *nix systems. Instead, clients should rely on the /declaration/ provided in tcpd.h: extern int deny_severity; extern int allow_severity; This may require code changes in clients that link against libwrap, but it was a necessary API change to enable DLL builds on cygwin. -- Charles Wilson volunteer tcp_wrappers maintainer for cygwin To update your installation, click on the "Install Cygwin now" link on the http://cygwin.com/ web page. This downloads setup.exe to your system. Then, run setup and answer all of the questions. *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated: inetutils-1.9.1-1; NEW: inetutils-server-1.9.1-1
inetutils provides common networking clients and servers, including the inetd super-server, telnetd and telnet, ftpd and ftp, talkd and talk, tftpd and tftp, uucpd (but no uucp client), and syslogd. This an update to the latest upstream release. It also adds a debuginfo package and support for cygwin64. CHANGES (since 1.7-2) o Updated to latest upstream release o Rely on cygport to autogenerate setup.hints o Split package into client and server components. o Added debuginfo package o First cygwin64 release -- Charles Wilson volunteer inetutils maintainer for cygwin To update your installation, click on the "Install Cygwin now" link on the http://cygwin.com/ web page. This downloads setup.exe to your system. Then, run setup and answer all of the questions. *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at 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: Intermittent failures retrieving process exit codes
On 11/15/2013 01:53 PM, Denis Excoffier wrote: On 2013-11-14 05:01, Tom Honermann wrote: On 12/21/2012 01:30 AM, Tom Honermann wrote: The workaround I implemented within Cygwin was simple and sloppy. I added a call to Sleep(1000) immediately before the call to ExitThread() in wait_sig() in winsup/cygwin/sigproc.cc. Since this thread (probably) doesn't exit until the process is exiting anyway, the call to Sleep() does not adversely affect shutdown. The thread just gets terminated while in the call to Sleep() instead of exiting before the process is terminated or getting terminated while still in the call to ExitThread(). A better solution might be to avoid the thread exiting at all (so long as it can't get terminated while holding critical resources), or to have the process exiting thread wait on it. Neither of these is ideal. Orderly shutdown of multi-threaded processes is really hard to do correctly on Windows. I experience on Windows 7 (not on XP) some problems that may be related. I would like to test your workaround, but sigproc.cc has much changed since then, there is now an exit_thead function with the comment "Exit the current thread very carefully.". I tried to insert Sleep(1000) at the end of exit_thread, immediately before "ExitThread (0)", but this yielded no change at all. Could someone be kind enough to update the workaround for modern sigproc.cc? Hi Denis. Cygwin versions 1.7.18 and later contain a workaround for this issue. If you are running something older than that, I highly encourage you to upgrade. Many stability related fixes have been made in more recent versions. Very briefly, my problem is that when i "tar xf —use-compress-program=xz", i get: tar: Unexpected EOF in archive tar: Unexpected EOF in archive tar: Error is not recoverable: exiting now and the last file of the archive is truncated at some 512bytes block. This occurs on Windows 7 (not on XP); with xz-5.1.3alpha (not with xz-5.1.2alpha or xz-5.0.5); never on most tar.xz files; almost always on some (rare) tar.xz files (one notable example is bc-1.06.95.tar.bz2 bunzip2’ed and then xz’ed); depends on the .tar file itself, not on the option (like -9e, -0) used to create the .tar.xz; never with "tar tf"; and with all tar’s i have tested. The return code of all the involved xz -d commands is always zero though. Perhaps after all, this is unrelated? This doesn't sound related to the intermittent incorrect exit code defect to me. I'm afraid I don't have other explanations for what you are experiencing though. Tom. -- 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
Audio Related
I want to add audio output volume control to an application. But, I don't know how to go about it yet. If you know anything about controlling volume from within cygwin applications or have done so, I would appreciate your telling me about it. Regards -- 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
