Re: OpenMPI installation bug: /usr/bin/mpif90 links to non-existent target
On 4/30/2015 3:32 AM, Mark Hadfield wrote: I have the current versions of openmpi and libopenmpi installed in Cygwin-64. The mpif90 command (MPI wrapper for Gfortran) does not execute, even though /usr/bin/mpif90 exists. The problem is that /usr/bin/mpif90 is a symbolic link to /usr/bin/mpifort.exe, which does not exist. However /usr/bin/mpifort does exist (and is itself a link to /usr/bin/opal_wrapper.exe). I have cured this by changing the target of /usr/bin/mpif90: $ ln -sf /usr/bin/mpifort /usr/bin/mpif90 Mark Hadfield 51 Volga St Wellington 6023, NZ Yes, I know. you can also use ln -sf usr/bin/opal_wrapper.exe /usr/bin/mpif90 ln -sf usr/bin/opal_wrapper.exe /usr/bin/mpif77 It is due to the interation of openmpi double link and cygport post-install rename of links. 1.8.5 will not have the issue, as I proposed a patch upstream https://github.com/open-mpi/ompi-release/commit/1147ddee73e84f80e27799e77391fc74033a6391 Regards Marco -- 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: phonon4qt5-4.8.3-2, phonon4qt5-backend-gstreamer-4.8.2-2
The following packages have been updated for the Cygwin distribution: * libphonon4qt5_4-4.8.3-2 * libphonon4qt5-devel-4.8.3-2 * phonon4qt5-backend-gstreamer-4.8.2-2 Phonon is a multimedia abstraction API for Qt and KDE applications. These updates were rebuilt for the dllimport change. -- 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
[ANNOUNCEMENT] Updated: poppler-0.30.0-2
The following packages have been updated for both arches: * poppler-0.30.0-2 * libpoppler49-0.30.0-2 * libpoppler-devel-0.30.0-2 * libpoppler-cpp0-0.30.0-2 * libpoppler-cpp-devel-0.30.0-2 * libpoppler-glib8-0.30.0-2 * libpoppler-glib-devel-0.30.0-2 * girepository-Poppler0.18-0.30.0-2 * libpoppler-qt4_4-0.30.0-2 * libpoppler-qt4-devel-0.30.0-2 * libpoppler-qt5_1-0.30.0-2 * libpoppler-qt5-devel-0.30.0-2 Poppler is a suite of PDF rendering libraries and utilities based on the xpdf-3.0 code base. This release is a rebuild for the Qt5 dllimport change. -- 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
[ANNOUNCEMENT] Updated: qscintilla2-2.8.4-3
The following packages have been updated in the Cygwin distribution: * libqscintilla2_11-2.8.4-3 * libqscintilla2-common-2.8.4-3 * libqscintilla2-devel-2.8.4-3 * libqscintilla2-qt5_11-2.8.4-3 * libqscintilla2-qt5-common-2.8.4-3 * libqscintilla2-qt5-devel-2.8.4-3 * python-pyqt4-qsci-2.8.4-3 * python-pyqt5-qsci-2.8.4-3 * python3-pyqt4-qsci-2.8.4-3 * python3-pyqt5-qsci-2.8.4-3 QScintilla is a port to Qt of Neil Hodgson's Scintilla C++ editor class. As well as features found in standard text editing components, QScintilla includes features especially useful when editing and debugging source code. These include support for syntax styling, error indicators, code completion and call tips. The selection margin can contain markers like those used in debuggers to indicate breakpoints and the current line. Styling choices are more open than with many editors, allowing the use of proportional fonts, bold and italics, multiple foreground/background colours and multiple fonts. This release is a rebuild for the Qt5 dllimport change. -- 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
[ANNOUNCEMENT] Updated: python*-pyqt5-5.4.1-2
The following packages have been updated in the Cygwin distribution * python-pyqt5-5.4.1-2 * python3-pyqt5-5.4.1-2 PyQt is a set of Python v2 and v3 bindings for Digia's Qt application framework and runs on all platforms supported by Qt. The bindings are implemented as a set of Python modules and contain over 620 classes. These releases have been rebuilt for the dllimport change. -- 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
[ANNOUNCEMENT] Updated: Qt 5.4.1, rebuilt
The following packages have been updated in the Cygwin distribution:
* libEnginio-devel-5.4.1-2
* libEnginio1-5.4.1-2
* libQt5Core-devel-5.4.1-3
* libQt5Core5-5.4.1-3
* libQt5Declarative-devel-5.4.1-2
* libQt5Declarative5-5.4.1-2
* libQt5Designer-devel-5.4.1-2
* libQt5Designer5-5.4.1-2
* libQt5Gui-devel-5.4.1-3
* libQt5Gui5-5.4.1-3
* libQt5Help-devel-5.4.1-2
* libQt5Help5-5.4.1-2
* libQt5Location-devel-5.4.1-2
* libQt5Location5-5.4.1-2
* libQt5Multimedia-devel-5.4.1-2
* libQt5Multimedia5-5.4.1-2
* libQt5Positioning-devel-5.4.1-2
* libQt5Positioning5-5.4.1-2
* libQt5Quick-devel-5.4.1-2
* libQt5Quick5-5.4.1-2
* libQt5Script-devel-5.4.1-2
* libQt5Script5-5.4.1-2
* libQt5ScriptTools-devel-5.4.1-2
* libQt5ScriptTools5-5.4.1-2
* libQt5SerialPort-devel-5.4.1-2
* libQt5SerialPort5-5.4.1-2
* libQt5Sql-devel-5.4.1-2
* libQt5Sql5-5.4.1-2
* libQt5Svg-devel-5.4.1-2
* libQt5Svg5-5.4.1-2
* libQt5UiTools-devel-5.4.1-2
* libQt5UiTools5-5.4.1-2
* libQt5WebChannel-devel-5.4.1-2
* libQt5WebChannel5-5.4.1-2
* libQt5WebKit-devel-5.4.1-2
* libQt5WebKit5-5.4.1-2
* libQt5WebSockets-devel-5.4.1-2
* libQt5WebSockets5-5.4.1-2
* libQt5X11Extras-devel-5.4.1-2
* libQt5X11Extras5-5.4.1-2
* libQt5XmlPatterns-devel-5.4.1-2
* libQt5XmlPatterns5-5.4.1-2
* qt5-base-doc-5.4.1-3
* qt5-base-examples-5.4.1-3
* qt5-declarative-doc-5.4.1-2
* qt5-declarative-examples-5.4.1-2
* qt5-declarative-tools-5.4.1-2
* qt5-devel-tools-5.4.1-2
* qt5-doc-tools-5.4.1-2
* qt5-enginio-doc-5.4.1-2
* qt5-imageformats-5.4.1-2
* qt5-imageformats-doc-5.4.1-2
* qt5-linguist-tools-5.4.1-2
* qt5-location-doc-5.4.1-2
* qt5-location-examples-5.4.1-2
* qt5-multimedia-doc-5.4.1-2
* qt5-multimedia-examples-5.4.1-2
* qt5-quick1-examples-5.4.1-2
* qt5-quick1-tools-5.4.1-2
* qt5-quickcontrols-5.4.1-2
* qt5-quickcontrols-doc-5.4.1-2
* qt5-quickcontrols-examples-5.4.1-2
* qt5-script-doc-5.4.1-2
* qt5-script-examples-5.4.1-2
* qt5-serialport-doc-5.4.1-2
* qt5-svg-doc-5.4.1-2
* qt5-svg-examples-5.4.1-2
* qt5-tools-doc-5.4.1-2
* qt5-tools-examples-5.4.1-2
* qt5-webchannel-doc-5.4.1-1
* qt5-webchannel-examples-5.4.1-1
* qt5-webkit-doc-5.4.1-2
* qt5-webkit-examples-5.4.1-2
* qt5-webkit-examples-doc-5.4.1-2
* qt5-websockets-doc-5.4.1-1
* qt5-x11extras-doc-5.4.1-2
* qt5-xmlpatterns-doc-5.4.1-2
* qt5-xmlpatterns-examples-5.4.1-2
Qt is a cross-platform C++ application framework for desktop and
embedded development. Qt enables programmers to create advanced GUI
applications once and deploy them to multiple platforms without
rewriting the source code.
It turns out there has been a change in signal/slot handling in Qt 5
which requires code to be compiled with correct dllexport/dllimport
attributes. While Qt 5 and code which uses it will *compile* fine by
simply relying on auto import as usual, resulting binaries end up with
numerous signals misfiring with the following warning on stderr:
QObject::connect: signal not found in [Class]
These warnings are *not* harmless; the problem is so bad that it caused
the new Qt5WebChannel and Qt5WebSockets APIs to be completely
non-functional at first. With dllexport/dllimport these are now working
correctly and therefore have been added to the distribution.
The existing Qt5 packages have been completely rebuilt to use
dllexport/dllimport (in the form of Q_DECL_EXPORT/Q_DECL_IMPORT). While
technically ABI compatible, I strongly recommend all self-compiled
Qt5-based code be rebuilt to assure proper operation.
Please note that you may occasionally encounter third-party Qt5-based
code (intended solely for *NIX systems) which incorrectly uses the
Q_DECL_{EX,IM}PORT macros, which will result in compile and/or link
errors. These cases will have to be patched.
This release also fixes QGtkStyle, which should be used automatically
within the GTK+ based desktops, and can be activated manually by setting
QT_STYLE_OVERRIDE=gtk in your environment or passing -style gtk as
command line arguments.
--
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
[ANNOUNCEMENT] Updated: curl-7.42.1-1
The following packages have been updated in the Cygwin distribution: * curl-7.42.1-1 * libcurl4-7.42.1-1 * libcurl-devel-7.42.1-1 * libcurl-doc-7.42.1-1 cURL is a library and command line tool for transferring data with URL syntax, supporting numerous protocols, SSL certificates, HTTP POST, HTTP PUT, FTP uploading, HTTP form based upload, proxies, cookies, user +password authentication, file transfer resume, proxy tunneling and more. This is an update to the latest upstream release, which includes a fix for CVE-2015-3153: http://curl.haxx.se/changes.html#7_42_1 http://curl.haxx.se/docs/adv_20150429.html -- 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
OpenMPI installation bug: /usr/bin/mpif90 links to non-existent target
I have the current versions of openmpi and libopenmpi installed in Cygwin-64. The mpif90 command (MPI wrapper for Gfortran) does not execute, even though /usr/bin/mpif90 exists. The problem is that /usr/bin/mpif90 is a symbolic link to /usr/bin/mpifort.exe, which does not exist. However /usr/bin/mpifort does exist (and is itself a link to /usr/bin/opal_wrapper.exe). I have cured this by changing the target of /usr/bin/mpif90: $ ln -sf /usr/bin/mpifort /usr/bin/mpif90 Mark Hadfield 51 Volga St Wellington 6023, NZ -- 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: From Microsoft: Windows 10 Console and Cygwin
Hi, see bottom post. On Wed, Apr 29, 2015 at 4:06 PM, Corinna Vinschen wrote: > Hi Rich, > > nice to read from you. > > On Apr 29 19:01, Rich Eizenhoefer wrote: >> Hi, >> >> I'm the Program Manager at Microsoft for the updated Windows 10 >> console. I searched the Cygwin FAQ and mailing list archives for >> issues related to Windows 10 and found an item about multiple windows >> which should already be fixed. We have received a couple reports about >> crashes when running on Windows 10 with the new console enabled. For >> example: >> >> "cygwin is dying when i run a bunch of the git tools. For example: >grep >> -rin log .\ 0 [main] us 0 init_cheap: VirtualAlloc pointer is null, Win32 >> error 487 AllocationBase 0x0, BaseAddress 0x6857, RegionSize 0x3A, >> State 0x1 C:\Program Files (x86)\Git\bin\grep.exe: *** Couldn't reserve >> space for cygwin's heap, Win32 error 0" > > This error message is a bit weird. For one thing, it would be nice if > you could give us a pointer to the message. I'm not aware of such a bug > report. > > Also, this is about a non-Cygwin version of git as the path to the git > tools suggests. On the other hand, if it's not a Cygwin version, the > error message itself only makes marginal sense. So maybe it's a Cygwin > DLL as part of some third party package which is often outdated in > relation to the official Cygwin distro version. > > As for the error message itself, it refers to the fact that, after a > Cygwin fork() call, the forked child can't reserve the space required > for the so-called "cygwin heap", a region used for internal usage > especially important for fork/exec related stuff. This usually points > to Cygwin DLLs which are not rebased, or a non-Cygwin DLL loaded into a > spot required for a Cygwin DLL after a fork. This is especially a > problem on 32 bit due to the restricted virtual memory. > > However, if I'm not completely off-track, the bug report does not really > have anything to do with a bad interaction between the W10 console and > Cygwin. While my own W10 virtual machine under Qemu/KVM fails to update > to versions after build 9926, I didn't encounter any unusual behaviour > of the W10 console in comparison with, say, the W8.1 console yet. I'm > usually running Cygwin tools in mintty, but I did test the W10 console, > too, of course. [...] Allow me to clarify. "C:\Program Files (x86)\Git\" is "Git for Windows", AKA "msysgit": https://msysgit.github.io/ As explained on README.md, it uses a MSys: https://github.com/msysgit/msysgit And as explained on that README.md, MSys is a fork of an old version of Cygwin. MSys's home page is here, it is part of the MinGW project: http://mingw.org/wiki/msys -Mike -- 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: From Microsoft: Windows 10 Console and Cygwin
Thanks Corinna. The info I sent on the bug below is all that I have. It's quite likely related to the stability of the version of Win 10 it was run against. My larger purpose is to reach out to you all and see what we can do to help Cygwin run with our new console, we don't want to break anybody if at all possible. Please send me the info on the Windows 7 issue and I'll review and get back to you about whether we are able to help. If we "can" (figure it out, understand and repro the issue, not several weeks worth of work) we'll get to it. Rich -Original Message- From: Corinna Vinschen [mailto:corinna-cyg...@cygwin.com] Sent: Wednesday, April 29, 2015 1:06 PM To: cygwin@cygwin.com; Rich Eizenhoefer Subject: Re: From Microsoft: Windows 10 Console and Cygwin Hi Rich, nice to read from you. On Apr 29 19:01, Rich Eizenhoefer wrote: > Hi, > > I'm the Program Manager at Microsoft for the updated Windows 10 > console. I searched the Cygwin FAQ and mailing list archives for > issues related to Windows 10 and found an item about multiple windows > which should already be fixed. We have received a couple reports about > crashes when running on Windows 10 with the new console enabled. For > example: > > "cygwin is dying when i run a bunch of the git tools. For example: >grep -rin > log .\ 0 [main] us 0 init_cheap: VirtualAlloc pointer is null, Win32 error > 487 AllocationBase 0x0, BaseAddress 0x6857, RegionSize 0x3A, State > 0x1 C:\Program Files (x86)\Git\bin\grep.exe: *** Couldn't reserve space > for cygwin's heap, Win32 error 0" This error message is a bit weird. For one thing, it would be nice if you could give us a pointer to the message. I'm not aware of such a bug report. Also, this is about a non-Cygwin version of git as the path to the git tools suggests. On the other hand, if it's not a Cygwin version, the error message itself only makes marginal sense. So maybe it's a Cygwin DLL as part of some third party package which is often outdated in relation to the official Cygwin distro version. As for the error message itself, it refers to the fact that, after a Cygwin fork() call, the forked child can't reserve the space required for the so-called "cygwin heap", a region used for internal usage especially important for fork/exec related stuff. This usually points to Cygwin DLLs which are not rebased, or a non-Cygwin DLL loaded into a spot required for a Cygwin DLL after a fork. This is especially a problem on 32 bit due to the restricted virtual memory. However, if I'm not completely off-track, the bug report does not really have anything to do with a bad interaction between the W10 console and Cygwin. While my own W10 virtual machine under Qemu/KVM fails to update to versions after build 9926, I didn't encounter any unusual behaviour of the W10 console in comparison with, say, the W8.1 console yet. I'm usually running Cygwin tools in mintty, but I did test the W10 console, too, of course. > Please let me know if there are other problems you are experiencing > with the W10 console that are a regression from previous versions. We > are a small team, but we want to help where possible to ensure that > Cygwin continues to run well in Windows 10. Thanks for the offer. We have a regression introduced with Windows 7 and never fixed in W8 or 8.1, albeit I reported it as part of the Windows 7 beta tests. Are you interested to give this a whirl as well? Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat
Re: sigfe.s: No such file or directory
On 4/29/2015 12:04 PM, Andrey Repin wrote: Greetings, Hans Horn! I'm trying to attach gdb to a running process (binary compiled with -g -ggdb -Og). I got: "sigfe.s: No such file or directory" What is sigfe.s and what do I make of this message? Thx. H Update: I upgraded cygwin to the latest (v2) version. Now I'm getting in addition the following warning: the debug information found in "/lib/debug//usr/bin/cyggfortran-3.dll.dbg" does not match "/usr/bin/cyggfortran-3.dll" (CRC mismatch). and warning: the debug information found in "/lib/debug//usr/bin/cygquadmath-0.dll.dbg" does not match "/usr/bin/cygquadmath-0.dll" (CRC mismatch). I should have also mentioned that the offending binary is fortran compiled with gfortran v4.9.3 Did you also install the relevant debug packages? Dear Andrey, I do think so! How else would I have these cyg*.dll.dbg? -rwx---r-x 1 hans hans 594632 Mar 3 10:07 /lib/debug//usr/bin/cygquadmath-0.dll.dbg -rwx---r-x 1 hans hans 3526482 Mar 3 10:07 /lib/debug//usr/bin/cyggfortran-3.dll.dbg -rwx---r-x 1 hans hans 497181 Feb 23 17:07 /usr/bin/cygquadmath-0.dll -rwx---r-x 1 hans hans 1023517 Feb 23 17:06 /usr/bin/cyggfortran-3.dll Anyhow, looking more closely, I noticed the different file dates. Manually removing the above and re-installing all gcc + gcc debuginfo packages solved the issue. The sigfe.s problem has gone as well as the CRC mismatches. thx. for making me look more closely! H. -- 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
Units requires Python3
I was using a little unit conversion program called "units". Today setup tells me that that little program requires Python3 == python3 (3.2.5-4) Py3K language interpreter Required by: units, python3-unidecode python3-unidecode (0.04.17-1) Python3 Unicode transliteration module Required by: units == so I'm uninstalling "units". Daniel -- 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: From Microsoft: Windows 10 Console and Cygwin
Hi Rich, nice to read from you. On Apr 29 19:01, Rich Eizenhoefer wrote: > Hi, > > I'm the Program Manager at Microsoft for the updated Windows 10 > console. I searched the Cygwin FAQ and mailing list archives for > issues related to Windows 10 and found an item about multiple windows > which should already be fixed. We have received a couple reports about > crashes when running on Windows 10 with the new console enabled. For > example: > > "cygwin is dying when i run a bunch of the git tools. For example: >grep -rin > log .\ 0 [main] us 0 init_cheap: VirtualAlloc pointer is null, Win32 error > 487 AllocationBase 0x0, BaseAddress 0x6857, RegionSize 0x3A, State > 0x1 C:\Program Files (x86)\Git\bin\grep.exe: *** Couldn't reserve space > for cygwin's heap, Win32 error 0" This error message is a bit weird. For one thing, it would be nice if you could give us a pointer to the message. I'm not aware of such a bug report. Also, this is about a non-Cygwin version of git as the path to the git tools suggests. On the other hand, if it's not a Cygwin version, the error message itself only makes marginal sense. So maybe it's a Cygwin DLL as part of some third party package which is often outdated in relation to the official Cygwin distro version. As for the error message itself, it refers to the fact that, after a Cygwin fork() call, the forked child can't reserve the space required for the so-called "cygwin heap", a region used for internal usage especially important for fork/exec related stuff. This usually points to Cygwin DLLs which are not rebased, or a non-Cygwin DLL loaded into a spot required for a Cygwin DLL after a fork. This is especially a problem on 32 bit due to the restricted virtual memory. However, if I'm not completely off-track, the bug report does not really have anything to do with a bad interaction between the W10 console and Cygwin. While my own W10 virtual machine under Qemu/KVM fails to update to versions after build 9926, I didn't encounter any unusual behaviour of the W10 console in comparison with, say, the W8.1 console yet. I'm usually running Cygwin tools in mintty, but I did test the W10 console, too, of course. > Please let me know if there are other problems you are experiencing > with the W10 console that are a regression from previous versions. We > are a small team, but we want to help where possible to ensure that > Cygwin continues to run well in Windows 10. Thanks for the offer. We have a regression introduced with Windows 7 and never fixed in W8 or 8.1, albeit I reported it as part of the Windows 7 beta tests. Are you interested to give this a whirl as well? Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpBOPaaZFpXz.pgp Description: PGP signature
Re: From Microsoft: Windows 10 Console and Cygwin
On 4/29/2015 3:01 PM, Rich Eizenhoefer wrote: > Hi, > > I'm the Program Manager at Microsoft for the updated Windows 10 console. I > searched the Cygwin FAQ and mailing list archives for issues related to > Windows 10 and found an item about multiple windows which should already be > fixed. We have received a couple reports about crashes when running on > Windows 10 with the new console enabled. For example: > > "cygwin is dying when i run a bunch of the git tools. For example: >grep -rin > log .\ 0 [main] us 0 init_cheap: VirtualAlloc pointer is null, Win32 error > 487 AllocationBase 0x0, BaseAddress 0x6857, RegionSize 0x3A, State > 0x1 C:\Program Files (x86)\Git\bin\grep.exe: *** Couldn't reserve space > for cygwin's heap, Win32 error 0" > > Please let me know if there are other problems you are experiencing with the > W10 console that are a regression from previous versions. We are a small > team, but we want to help where possible to ensure that Cygwin continues to > run well in Windows 10. > > Thanks, > > Rich > > -- > Windows 10 has given me satisfactory results with cygwin64 (although I'm more likely to run git under 8.1). This is a welcome change from the days when Microsoft personnel stated that bugs reported primarily by cygwin users would not be fixed even when they could be reproduced outside cygwin. -- Tim Prince -- 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: Updated: xorg-server-1.17.1-3
On 04/29/2015 01:19 PM, Robin Flynn wrote: > Could you please remove me from the Cygwin Mailing List ... > -- > 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 Even better, how about you remove yourself, by following the instructions in this link that appears in the footer? -- Eric Blake eblake redhat com+1-919-301-3266 Libvirt virtualization library http://libvirt.org signature.asc Description: OpenPGP digital signature
Re: Updated: xorg-server-1.17.1-3
Could you please remove me from the Cygwin Mailing List Regards Robin Flynn On 29/04/2015 18:26, Jon TURNEY wrote: The following packages have been updated in the Cygwin distribution: *** xorg-server-*1.17.1-3 These packages contain XWin and the other X.Org X11 servers. The following cygwin-specific changes have been made since 1.17.1-2: * Fix build with Cygwin 2.0.0 * Crash reporting improvements using new features of Cygwin 2.0.0 * Update builder email for cygwin-xfree list deprecation * Capture xkbcomp exit status, stderr and stout to log * Clarify authorization failure reason strings sent back to the client * Generic handling of Macintosh keyboard layouts * Correctly check if window title already contains hostname when WM_CLIENT_MACHINE is a FQDN NOTEWORTHY CHANGES IN 1.17 == The creation of indirect GLX contexts is now prohibited by default. The +iglx option is required to allow them. See [1] for more information on possible OpenGL configurations. '-nolisten tcp' is now the default, so the server only accepts local connections on a unix domain socket. A '-listen' option has been added which can be used to restore the previous behaviour. x86: 856d2256ee602adcd3ca6cb9627dafd1 *xorg-server-1.17.1-3-src.tar.xz 2b0e1edf6f30f92c505c9b4021c4e82c *xorg-server-1.17.1-3.tar.xz c64218679233d5a374ff1dfa9e02d641 *xorg-server-common-1.17.1-3.tar.xz cbd1a3679fd46d7db96a609db5fc128c *xorg-server-debuginfo-1.17.1-3.tar.xz ebb3a6bbf623554f280a8dc790d1aa10 *xorg-server-devel-1.17.1-3.tar.xz cf74071dd335fe281a7372715623db1f *xorg-server-dmx-1.17.1-3.tar.xz edf21a438200b0b0930c0773fc0fe916 *xorg-server-extra-1.17.1-3.tar.xz e263e0e2369b58c53e2d0790d9462024 *xwinclip-1.17.1-3.tar.xz x86_64: c4aff68cad7b26f7fd3eef7a6f049497 *xorg-server-1.17.1-3-src.tar.xz bcafcc0ee029dd33cf4e0d767e5794eb *xorg-server-1.17.1-3.tar.xz 61cea9fedcc587b3e61aaeb37939c151 *xorg-server-common-1.17.1-3.tar.xz 10689d58bd4bd48efb13162171780a9f *xorg-server-debuginfo-1.17.1-3.tar.xz d412d9964b18df65c085fc8c6999a691 *xorg-server-devel-1.17.1-3.tar.xz d3890d2e3bd7b84952eea6dd570853cb *xorg-server-dmx-1.17.1-3.tar.xz 06d2f80432173b1f2be1a762fe756c7b *xorg-server-extra-1.17.1-3.tar.xz 6abc178f7032a0b6a2fb2321741ff474 *xwinclip-1.17.1-3.tar.xz [1] http://x.cygwin.com/docs/ug/using-aiglx.html -- 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: sigfe.s: No such file or directory
Greetings, Hans Horn! >> I'm trying to attach gdb to a running process (binary compiled with -g >> -ggdb -Og). I got: "sigfe.s: No such file or directory" >> >> What is sigfe.s and what do I make of this message? >> >> Thx. >> H >> > Update: I upgraded cygwin to the latest (v2) version. > Now I'm getting in addition the following > warning: the debug information found in > "/lib/debug//usr/bin/cyggfortran-3.dll.dbg" does not match > "/usr/bin/cyggfortran-3.dll" (CRC mismatch). > and > warning: the debug information found in > "/lib/debug//usr/bin/cygquadmath-0.dll.dbg" does not match > "/usr/bin/cygquadmath-0.dll" (CRC mismatch). > I should have also mentioned that the offending binary is fortran > compiled with gfortran v4.9.3 Did you also install the relevant debug packages? -- With best regards, Andrey Repin Wednesday, April 29, 2015 22:03:43 Sorry for my terrible english... -- 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
From Microsoft: Windows 10 Console and Cygwin
Hi, I'm the Program Manager at Microsoft for the updated Windows 10 console. I searched the Cygwin FAQ and mailing list archives for issues related to Windows 10 and found an item about multiple windows which should already be fixed. We have received a couple reports about crashes when running on Windows 10 with the new console enabled. For example: "cygwin is dying when i run a bunch of the git tools. For example: >grep -rin log .\ 0 [main] us 0 init_cheap: VirtualAlloc pointer is null, Win32 error 487 AllocationBase 0x0, BaseAddress 0x6857, RegionSize 0x3A, State 0x1 C:\Program Files (x86)\Git\bin\grep.exe: *** Couldn't reserve space for cygwin's heap, Win32 error 0" Please let me know if there are other problems you are experiencing with the W10 console that are a regression from previous versions. We are a small team, but we want to help where possible to ensure that Cygwin continues to run well in Windows 10. Thanks, Rich -- 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: xorg-server-1.17.1-3
The following packages have been updated in the Cygwin distribution: *** xorg-server-*1.17.1-3 These packages contain XWin and the other X.Org X11 servers. The following cygwin-specific changes have been made since 1.17.1-2: * Fix build with Cygwin 2.0.0 * Crash reporting improvements using new features of Cygwin 2.0.0 * Update builder email for cygwin-xfree list deprecation * Capture xkbcomp exit status, stderr and stout to log * Clarify authorization failure reason strings sent back to the client * Generic handling of Macintosh keyboard layouts * Correctly check if window title already contains hostname when WM_CLIENT_MACHINE is a FQDN NOTEWORTHY CHANGES IN 1.17 == The creation of indirect GLX contexts is now prohibited by default. The +iglx option is required to allow them. See [1] for more information on possible OpenGL configurations. '-nolisten tcp' is now the default, so the server only accepts local connections on a unix domain socket. A '-listen' option has been added which can be used to restore the previous behaviour. x86: 856d2256ee602adcd3ca6cb9627dafd1 *xorg-server-1.17.1-3-src.tar.xz 2b0e1edf6f30f92c505c9b4021c4e82c *xorg-server-1.17.1-3.tar.xz c64218679233d5a374ff1dfa9e02d641 *xorg-server-common-1.17.1-3.tar.xz cbd1a3679fd46d7db96a609db5fc128c *xorg-server-debuginfo-1.17.1-3.tar.xz ebb3a6bbf623554f280a8dc790d1aa10 *xorg-server-devel-1.17.1-3.tar.xz cf74071dd335fe281a7372715623db1f *xorg-server-dmx-1.17.1-3.tar.xz edf21a438200b0b0930c0773fc0fe916 *xorg-server-extra-1.17.1-3.tar.xz e263e0e2369b58c53e2d0790d9462024 *xwinclip-1.17.1-3.tar.xz x86_64: c4aff68cad7b26f7fd3eef7a6f049497 *xorg-server-1.17.1-3-src.tar.xz bcafcc0ee029dd33cf4e0d767e5794eb *xorg-server-1.17.1-3.tar.xz 61cea9fedcc587b3e61aaeb37939c151 *xorg-server-common-1.17.1-3.tar.xz 10689d58bd4bd48efb13162171780a9f *xorg-server-debuginfo-1.17.1-3.tar.xz d412d9964b18df65c085fc8c6999a691 *xorg-server-devel-1.17.1-3.tar.xz d3890d2e3bd7b84952eea6dd570853cb *xorg-server-dmx-1.17.1-3.tar.xz 06d2f80432173b1f2be1a762fe756c7b *xorg-server-extra-1.17.1-3.tar.xz 6abc178f7032a0b6a2fb2321741ff474 *xwinclip-1.17.1-3.tar.xz [1] http://x.cygwin.com/docs/ug/using-aiglx.html -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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: Fork Failures
Anne Linden writes: > My machine started having fork failures, so I found the documentation > on fork failures and am trying to fix it. However the rebaseall -v > command will not run. I only ever get back the response "only ash or > dash processes are allowed during rebasing Exit all Cygwin processes > and stop all Cygwin services" Yes, you need to run this from a CMD window where you started dash. Besides, you really don't need to do this anymore, just run $ rebase-trigger fullrebase in a Cygwin shell, then shut down all Cygwin processes still running and run setup.exe again. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptation for Waldorf Blofeld V1.15B11: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada -- 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: sigfe.s: No such file or directory
On 4/29/2015 7:58 AM, Hans Horn wrote: Folks, I'm trying to attach gdb to a running process (binary compiled with -g -ggdb -Og). I got: "sigfe.s: No such file or directory" What is sigfe.s and what do I make of this message? Thx. H Update: I upgraded cygwin to the latest (v2) version. Now I'm getting in addition the following warning: the debug information found in "/lib/debug//usr/bin/cyggfortran-3.dll.dbg" does not match "/usr/bin/cyggfortran-3.dll" (CRC mismatch). and warning: the debug information found in "/lib/debug//usr/bin/cygquadmath-0.dll.dbg" does not match "/usr/bin/cygquadmath-0.dll" (CRC mismatch). I should have also mentioned that the offending binary is fortran compiled with gfortran v4.9.3 -- 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: Fork Failures
> > My machine started having fork failures, so I found the documentation on fork > failures and am trying to fix it. However the rebaseall -v command will not > run. > I only ever get back the response "only ash or dash processes are allowed > during > rebasing Exit all Cygwin processes and stop all Cygwin services" > > However when I run ps -a it only lists the bash process and the ps process, > so I'm > very confused as how to fix this. I've restarted the computer, but get the > same > results. > > I am running bash.exe as an admin for all of this, FYI > Bash is not ash or dash. The error message is specific enough for you to have figured this out on your own. >From a Windows CMD Console open the ash.exe program then execute the command. -- cyg Simple -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
RE: Fork Failures
>-Original Message- >From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On Behalf Of >Anne Linden >Sent: Wednesday, April 29, 2015 10:06 AM >To: cygwin@cygwin.com >Subject: Fork Failures > >However when I run ps -a it only lists the bash process and the ps process, >so I'm very confused as how to fix this. I've restarted the computer, but >get >the same results. >I am running bash.exe as an admin for all of this, FYI Bash is a Cygwin process. You need to stop *all* Cygwin processes. Run Windows task manager if you have to and kill all Cygwin processes. [OR reboot is often necessary for me.] Then run cmd and cd into c:/Cygwin, then cd into bin to run ash. At the ash prompt run /usr/bin/rebaseall -v.
Fork Failures
Hi, My machine started having fork failures, so I found the documentation on fork failures and am trying to fix it. However the rebaseall -v command will not run. I only ever get back the response "only ash or dash processes are allowed during rebasing Exit all Cygwin processes and stop all Cygwin services" However when I run ps -a it only lists the bash process and the ps process, so I'm very confused as how to fix this. I've restarted the computer, but get the same results. I am running bash.exe as an admin for all of this, FYI Thanks, Anne -- 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
sigfe.s: No such file or directory
Folks, I'm trying to attach gdb to a running process (binary compiled with -g -ggdb -Og). I got: "sigfe.s: No such file or directory" What is sigfe.s and what do I make of this message? Thx. H -- 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
Group Permissions on root folders problem (Windows 10 TP build 10061)
I did a fresh cygwin-64 (setup-x86_64 version 2.870) install under build 10061 of Windows 10 Technical Preview. The group permissions in the root look wrong. $ ls -lA / total 321 drwx---r-x+ 1 Brian Brian 0 Apr 29 10:31 bin dr-xr-xr-x 1 Brian Brian 0 Apr 29 10:31 cygdrive -rwxr-xr-x 1 Brian Administrators 59 Apr 29 10:31 Cygwin.bat -rw-r--r-- 1 Brian Administrators 157097 Apr 29 10:31 Cygwin.ico -rw-r--r-- 1 Brian Administrators 53342 Apr 29 10:31 Cygwin-Terminal.ico drwx---r-x+ 1 Brian Brian 0 Apr 29 10:31 dev drwx---r-x+ 1 Brian Brian 0 Apr 29 10:31 etc drwx---rwt+ 1 Brian Brian 0 Apr 29 10:31 home drwx---r-x+ 1 Brian Brian 0 Apr 29 10:31 lib dr-xr-xr-x 9 Brian Brian 0 Apr 29 10:31 proc drwx---r-x+ 1 Brian Brian 0 Apr 29 10:31 sbin drwx---rwt+ 1 Brian Brian 0 Apr 29 10:31 tmp drwx---r-x+ 1 Brian Brian 0 Apr 29 10:30 usr drwx---r-x+ 1 Brian Brian 0 Apr 29 10:30 var I'm logged on with a Microsoft account and ran the installer as an Administrator. This is a particular problem running ssh-host-config -y $ ssh-host-config -y *** Info: Generating missing SSH host keys ssh-keygen: generating new host keys: RSA1 RSA DSA ECDSA ED25519 *** Info: Creating default /etc/ssh_config file *** Info: Creating default /etc/sshd_config file *** Info: StrictModes is set to 'yes' by default. *** Info: This is the recommended setting, but it requires that the POSIX *** Info: permissions of the user's home directory, the user's .ssh *** Info: directory, and the user's ssh key files are tight so that *** Info: only the user has write permissions. *** Info: On the other hand, StrictModes don't work well with default *** Info: Windows permissions of a home directory mounted with the *** Info: 'noacl' option, and they don't work at all if the home *** Info: directory is on a FAT or FAT32 partition. *** Query: Should StrictModes be used? (yes/no) yes *** Info: Privilege separation is set to 'sandbox' by default since *** Info: OpenSSH 6.1. This is unsupported by Cygwin and has to be set *** Info: to 'yes' or 'no'. *** Info: However, using privilege separation requires a non-privileged account *** Info: called 'sshd'. *** Info: For more info on privilege separation read /usr/share/doc/openssh/README.privsep. *** Query: Should privilege separation be used? (yes/no) yes *** Warning: The permissions on the directory /var are not correct. *** Warning: They must match the regexp d..x..x..[xt] *** ERROR: Problem with /var directory. Exiting. $ id uid=197608(Brian) gid=197608(Brian) groups=197608(Brian),405504(High Mandatory Level),114(Local account and member of Administrators group),197611(HomeUsers),544(Administrators),545(Users),4(INTERACTIVE),66049(CONSOLE LOGON),11(Authenticated Users),15(This Organization),68521(microsoftaccount+br...@buchananworldcorp.com),113(Local account),66048(LOCAL),262180(Cloud Account Authentication) Am I doing something wrong? Is there a way to fix the permissions or a workaround for installation? Thanks, Brian -- 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
