Re: libMagickCore6_2-6.9.0.0-4 (x86) in wrong compression format
On 7/9/2015 12:06 AM, Peng He wrote: In the ImageMagick-6.9.0.0-4 (x86) package updated on Sun, 31 May 2015, /x86/release/ImageMagick/libMagickCore6_2/libMagickCore6_2-6.9.0.0-4.tar.xz seems to be a bzip2 archive instead of an xz archive, as indicated by the file extension. I found this problem when installing babun (http://babun.github.io/), curios our hippo as a baboon as stepson where the downstream installation was broken by this package. I noticed this problem on several mirrors. All other .xz files in this package seems to be consistent with the extension. Please help to solve this. Thanks! Regards, Peng re-uploaded in the right format. Give some time to the mirrors to propagate. by the way libMagickCore6_2-6.9.0.0-4 is not anymore the current version curr: 6.9.1.3-2 prev: 6.9.0.0-4 so the real format of libMagickCore6_2-6.9.0.0-4.tar.xz should have been irrelevant. Cygwin setup seems to no care, as it is not using the extension to determine the real file nature. 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
Re: Looking for 64-bit proxy
Greetings, Marco Atzeri! >>> Currently I am using connect-proxy on WinXP (32 bit). I would like to use >>> connect-proxy on a Win7 PC but there is no 64-bit version. Is there an >>> alternative to connect-proxy for 64-bit, or would I need to revert to the >>> 32-bit cygwin just to get this connect-proxy? >> >> 3proxy.ru >> >> > Andrey > I assume Denis was talking about: > connect-proxy 32 bitORPHANED (Kostya Altukhov) I assumed he was looking for a proxy server. 3proxy offers everything proxy you could possibly imagine. HTTP including CONNECT, FTP, SOCKS4 and 5, POP3 proxy. -- With best regards, Andrey Repin Thursday, July 9, 2015 10:19:16 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
Re: Cygwin date displays only GMT on Win7
On Jul 8 20:41, Nellis, Kenneth wrote: > Siv wrote: > > > > date --date='TZ="ANYTHING" isn't working as expected > > Thanx. Anyway the last 2 cmds worked : > > > > date Wed, Jul 08, 2015 2:03:12 PM > > date -u Wed, Jul 08, 2015 2:03:13 PM > > date --date='TZ="Asia/Delhi"' Wed, Jul 08, 2015 12:00:00 AM > > date --date='TZ="Asia/Calcutta"' Tue, Jul 07, 2015 6:30:00 PM > > date --date='TZ="Asia/Kolkata"' Tue, Jul 07, 2015 6:30:00 PM > > TZ=Asia/Delhi dateWed, Jul 08, 2015 2:03:14 PM > > TZ=Asia/Kolkata date Wed, Jul 08, 2015 7:33:15 PM > > TZ=Asia/Calcutta date Wed, Jul 08, 2015 7:33:15 PM > > > > As expected?? > Where did you get this --date='TZ=..." syntax?? Not anywhere I could find. > > --date=STRING > > Read the man page. > > STRING works like this: > > $ date > Wed Jul 8 16:38:44 EDT 2015 > $ date --date=Thursday > Thu Jul 9 00:00:00 EDT 2015 > $ date --date="last Monday" > Mon Jul 6 00:00:00 EDT 2015 > $ date --date="25 dec 2016" > Sun Dec 25 00:00:00 EST 2016 > $ > > --Ken Nellis Also, Asia/Delhi is not a valid timezone. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpWt0cVsJ2nX.pgp Description: PGP signature
Pandoc, Haskell and Matplotlib?
Hi, Would it be possible to integrate Pandoc, Haskell and Python Matplotlib in the next Cygwin Release? Yves -- 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: TEST RELEASE: Cygwin 2.1.0-0.4
On Jul 8 13:39, Warren Young wrote: > On Jul 5, 2015, at 3:34 PM, Corinna Vinschen > wrote: > > ...RLIMIT_STACK...RLIM_INFINITY. > > This should fix the Emacs crash you reference later in this message > without rebuilding Emacs, right? > > I’m not an Emacs user, as you know, but is there an STC for the > Emacsizens to try on their systems? As Ken wrote. > > - New API sigaltstack, plus definitions for SA_ONSTACK, SS_ONSTACK, > > SS_DISABLE, > > MINSIGSTKSZ, SIGSTKSZ. > > Since these were entirely missing before, this can’t be tested without > rebuilding software, right? When rebuilt, existing Cygwin packages > may discover the new APIs via autoconf or similar. > [...] > So, is it simply the case that the only people who will care to test > this are those who already know they’re trying to call this, and need > it to work? Kind of, yes. The relevant snippet from the announcements: 2.1.0-0.1 - 2.1.0-0.3: This test release is mostly for interested *developers*. 2.1.0-0.4 - 2.1.0-0.5: While the changes are still mostly interesting for developers, the under-the-hood changes will potentially impact existing applications. But note the latter. These under-the-hood changes which affect existing applications are: - Changes to how getrlimit(RLIMIT_STACK) works and how pthread stacks are set up now. The general effect is that pthreads will have bigger default stacks now, 2 rather than 1 Meg, unless the application developer or maintainer handled the pthread stacksizes explicitely. - Child stack allocation after fork has been rearranged and partially rewritten. This is new code at the core of how fork works. This, of course, affects all existing applications using the fork call. > > - New API: sethostname. > > For what it’s worth, that gave a pretty similar result set: lots of > OSes and low-level infrastructure, few user-space packages. Yes, but it was easy to implemement and another API which may help building packages without having to tweak them for Cygwin: https://cygwin.com/ml/cygwin-patches/2015-q2/msg00076.html > > > - Enable non-SA_RESTART behaviour on threads other than main thread. > > Addresses: https://cygwin.com/ml/cygwin/2015-06/msg00260.html > > Nice fix for an obscure problem. > > And thanks for providing references, so that those like me who didn’t > pay attention to the original thread can catch up and see why we care > about these fixes. :) No worries, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpKtzuZQxJPx.pgp Description: PGP signature
Re: Pandoc, Haskell and Matplotlib?
On Jul 9 09:35, Chevallier Yves wrote: > Hi, > > Would it be possible to integrate Pandoc, Haskell and Python > Matplotlib in the next Cygwin Release? Only if we get volunteers porting and maintainer them. Have a look at https://sourceware.org/cygwin/setup.html if you're interested. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpmt5QZSFDlv.pgp Description: PGP signature
Re: Isuse with xwin-xdg-menu "View logfile"
On Wed, Jul 8, 2015 at 10:43 AM, Jon TURNEY wrote: > On 07/07/2015 04:13, Michael DePaulo wrote: >> >> First of all, let me say how much I like xwin-xdg-menu. Thumbs up to >> Jon Turney, and to all the other developers like Yaakov Selkowitz who >> work on related components/package for Cygwin/X. >> >> Anyway, when I do the following: >> >> $ xinit -- -multiwindow >> >> From the xterm that automatically launches: >> $ xwin-xdg-menu >> >> XDG Menu > View logfile >> >> I then see this: >> >> executing 'xterm -title '/dev/pty1' -e less +F /dev/pty1', pid 1292 >> (pid 1292 stderr) Warning: Missing charsets in String to FontSet >> conversion >> (pid 1292 stderr) Warning: Unable to load any usable fontset >> pid 1292 exited with status 0 >> >> (The xterm window flashes briefly, and then disappears.) >> >> Is /dev/pty1 the log file we should be trying to open? >> >> I am not even sure what log file should be opened. Personally, I would >> have assumed it is the X Server's log file. > > > That's hard to do with full generality, as we would need to know or discover > what -logfile option the server was given. > >> I see that this is the relevant code: >> >> https://github.com/jon-turney/xwin-xdg-menu/blob/51ae0ec7f225b8257ba64ce5318b857bf9ce8450/execute.c#L236 > > > I made a small update to today, which includes a change to remove the "View > logfile" menu item if stdout is a tty, which should avoid this problem > scenario. > > -- > Jon TURNEY > Volunteer Cygwin/X X Server maintainer Thanks. I tested it successfully. And Yaakov, thanks for explaining that. (In a split email thread, Yaakov explained that I should use the "XWin Server" shortcut, which uses startxwin). -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: Looking for 64-bit proxy
Andrey Repin wrote: >Greetings, Marco Atzeri! > Currently I am using connect-proxy on WinXP (32 bit). I would like to use connect-proxy on a Win7 PC but there is no 64-bit version. Is there an alternative to connect-proxy for 64-bit, or would I need to revert to the 32-bit cygwin just to get this connect-proxy? >>> >>> 3proxy.ru >>> >>> > >> Andrey >> I assume Denis was talking about: > >> connect-proxy 32 bit ORPHANED (Kostya Altukhov) > >I assumed he was looking for a proxy server. >3proxy offers everything proxy you could possibly imagine. >HTTP including CONNECT, FTP, SOCKS4 and 5, POP3 proxy. My terminology may be confusing but I'm looking for a 64-bit alternative for the 32-bit connect-proxy. I didn't see anything that looked like an alternative under cygwin/net. Denis -- 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: Looking for 64-bit proxy
On 7/9/2015 4:33 PM, Kertz, Denis (D)** CTR ** wrote: Andrey Repin wrote: Greetings, Marco Atzeri! Currently I am using connect-proxy on WinXP (32 bit). I would like to use connect-proxy on a Win7 PC but there is no 64-bit version. Is there an alternative to connect-proxy for 64-bit, or would I need to revert to the 32-bit cygwin just to get this connect-proxy? 3proxy.ru Andrey I assume Denis was talking about: connect-proxy 32 bitORPHANED (Kostya Altukhov) I assumed he was looking for a proxy server. 3proxy offers everything proxy you could possibly imagine. HTTP including CONNECT, FTP, SOCKS4 and 5, POP3 proxy. My terminology may be confusing but I'm looking for a 64-bit alternative for the 32-bit connect-proxy. I didn't see anything that looked like an alternative under cygwin/net. Denis Hi Denis, No problem, the request was clear. The package is very simple, I already built a 64bit version of 1.104 version. Give me some time for polishing the package I will release it 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: xorg-server-1.17.2-1 (TEST)
The following packages have been updated in the Cygwin distribution: *** xorg-server-*1.17.2-1 These packages contain XWin and the other X.Org X11 servers. In addition to upstream fixes [1], the following cygwin-specific changes have been made since 1.17.1-5: * Only apply MINIMIZE or MAXIMIZE styles from XWinrc when mapping a window * Ensure WM_TRANSIENT_FOR windows are always parented * Downgrade a warning when the experimental crashreporter isn't present to debug * When a SEGV occurs checking WGL, disable WGL and continue, rather than exiting * Report invalid options in combination with -nodecoration * Add support for a SKIPTASKBAR style in XWinrc These packages are currently marked as a test release because they contain changes to code critical to the correct functioning of multiwindow mode, so there is a higher than normal risk of regressions. They will be made stable in approximately two weeks if no major regressions are reported. 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 [2] 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. [1] http://lists.x.org/archives/xorg-announce/2015-June/002614.html [2] http://x.cygwin.com/docs/ug/using-aiglx.html x86: a35fd0165419d41f8893f8e74f073c1c9c028d190ee300ddd3cc33e7a613515693cb0b0b5cab9e2dc78cc50ca8075aba221301a091341f4bafde168cf64136e7 *xorg-server-1.17.2-1-src.tar.xz 9ef95564b4e020350578463c6203b6faa38932f7a3718ad5ea54f257a1c567ff3447fbc3c1631b3e4ca065f68c2e9ce2e43ab8ab028c9428b43e45c2b6188d44 *xorg-server-1.17.2-1.tar.xz 0135fd17269f572b31a83af7f78c4f2fdda77921f1cb6088bcfc043a26faa6bf3010af6bb2dfbd251c527e990f6903da4e31b025b6edf4fd6836a8efdd44b624 *xorg-server-common-1.17.2-1.tar.xz c20ee81eff3b68d21f796a809664bc1ca9fbaeeaf800f8bd658a1e3d1622812cdea0e9f38a239313c6e90d3d12d18cfee4e4f03130033000caaec2ffb772af33 *xorg-server-debuginfo-1.17.2-1.tar.xz 3f7d9875dd3bb0faa614414eb31328269b16385f87a4ae78b03e5becbe8ad3065dde30ad9aed6ba88a388be6dc9ad108c1f2d45450784dec8a839cef0b97e787 *xorg-server-devel-1.17.2-1.tar.xz 819f3145fbaac0f69c9831994126496a780322b372e68930da18703a79154910c9bacaf2ca74e1f32d8176ea0297e1b4af492169d759ac8b1c24deb501fc5b9e *xorg-server-dmx-1.17.2-1.tar.xz 292092b8b356deb5fa9041da5e5762f0c1bfc1f9b89db80f4726ac8db7d44d70e8a850e461c19c6ccd51e03438cd6a1b6d6b890663346823413217a546a98e30 *xorg-server-extra-1.17.2-1.tar.xz b167ac79ae59b6c26d7f1574aa6a3ba4ecc45af5220513ade78df9c1eebf5ea8d1fdc67c133746b9801d65cc948ee0fed495bfc9e4a9d647295d76965bee2620 *xwinclip-1.17.2-1.tar.xz x86_64: 182f03fcea11387475d4eea09eb455b250a9560d243711fc3560a063a96e4db7e54ff2e9b5ef6cf32e543b6274e6df08aba33d78cea48b1be8aa15087cb436f6 *xorg-server-1.17.2-1-src.tar.xz fe035389c6608e4ecfae1b1e5c2651e395d39ad960c36796a1be39dac75737a10244cb50b87a133084626deaedfdc0d1b1e74e484021f9aa1a455673b39631d9 *xorg-server-1.17.2-1.tar.xz 64e9d0c87a983dd87fd1696e19a116f96646a04c4fb3c6f3f7a00bd76dce52a980660a608a1dcc99f57bfe37f66dbcddf1117838684206a338d9a482a0a0153f *xorg-server-common-1.17.2-1.tar.xz f347f71fe6037650779843761fed114a6ef83c3281c746f6fbd7ff18b653c53ccea7fe24e9411ad08623a08dfc42944be5080be6474bb10be0c1e0515d4e29a4 *xorg-server-debuginfo-1.17.2-1.tar.xz 035ca63b49fc1dbe44af6122f647f253cdfe3f974612722c6b3933c84f2e08c707405c2a49739040f552905bdf9400e168d1567bbdd55a4c024d3f09be9490a9 *xorg-server-devel-1.17.2-1.tar.xz c34c43a6bd0f8df78af4e84eeb91d1d9c78183ef97e7453e30d1336ca819f7f5de065bce6127f628479316d0e56936ffbf260cc9f1ab8db9a91e7de92c01da83 *xorg-server-dmx-1.17.2-1.tar.xz 504ec7b7f83ac9c808e2724b6fed0206edd188e6ef368396f512deec08174ea86ff60115128ebb9ff48983fc41027ee144e1cfabdc60d185c26bbc796f55a123 *xorg-server-extra-1.17.2-1.tar.xz 688485df2d81614115f34948b51ce10b899e0382d8e9a642c8cb33277b413f80b6c2c9b513517d9f657f8eec9648ad43526ed6b432285165f36d7531a0b963f8 *xwinclip-1.17.2-1.tar.xz -- 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: Looking for 64-bit proxy
On 7/9/2015 4:33 PM, Kertz, Denis (D)** CTR ** wrote: connect-proxy 32 bitORPHANED (Kostya Altukhov) My terminology may be confusing but I'm looking for a 64-bit alternative for the 32-bit connect-proxy. I didn't see anything that looked like an alternative under cygwin/net. Denis Hi Denis, I uploaded on http://matzeri.altervista.org/x86_64/connect-proxy/ can you test it ? To install setup-x86_64.exe -X -O -s http://matzeri.altervista.org -q -P connect-proxy 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
Qt5: QDir::mkpath() fails for /cygdrive/ paths
QDir::mkpath() fails when creating paths that start '/cygdrive/'. This
problem is only shown with Qt5 (not Qt4), and only with paths that start
'/cygdrive/' (so running from my home directory '~' is fine). This is
not a permissions problem, as it works fine with Qt4.
Sample programme is below. Compile for Qt5 as per the comments. 'cd
/cygdrive/X' where X is a local drive where you have permissions to
create a directory. Run './create_directory new_dir' and it fails to
create the directory. Programme works fine when compiled with Qt4.
I am using libQt5Core5-5.4.1-4 and libQt4-4.8.7-1 under cygwin-2.0.4-1.
I haven't had chance to try with Qt 5.4.2 (announced yesterday), so
apologies in advance if this is fixed already.
Dave.
// Programme to create a directory.
// Works with Qt4:
// g++ -I/usr/include/qt4 -o create_directory create_directory.cpp -lQtCore
//
// Fails with Qt5 if run from a path starting '/cygdrive/', otherwise OK:
// g++ -I/usr/include/qt5 -o create_directory create_directory.cpp -lQt5Core
#include
#include
int main(int argc, char** argv)
{
if (argc != 2)
std::cerr << "Syntax: create_directory ";
else
{
QDir dir(QDir::currentPath());
if (!dir.mkpath(argv[1]))
std::cerr << "Failed to create directory '"
<< argv[1] << "'." << std::endl;
}
return 0;
}
--
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] New: xwin-xdg-menu-20150706-1 [GOLDSTAR]
> On Mon, 2015-07-06 at 22:16 +0100, Jon TURNEY wrote: > > The following packages have been added to the Cygwin distribution: > > > > * xwin-xdg-menu > > > > xwin-xdg-menu is an XDG Desktop Menu Specification [1] menu for the X > > Window System running in the Cygwin environment. > > > > xwin-xdg-menu reads the menu specification and desktop entries, and > > constructs a menu which is accessed from a notification area icon. > > I really hope that users who didn't like the fbpanel solution (and it > seems there are many) will give this a fair shot. In appreciation of > the work Jon put into addressing both users' input as well as the many > technical requirements of a modern, spec-compliant solution, could we > please have a gold star polished for Jon? Awarded! https://cygwin.com/goldstars/#JTy -- 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: [GOLDSTAR] Re: [ANNOUNCEMENT] Release: mintty 2.0.1
> On Jul 3 23:18, Thomas Wolff wrote: > > After closing half of the open issues, I thought its a good time to release > > mintty. > > Ive bumped the major version number to 2 to reflect the change of > > repository and maintainer and somehow catch up with cygwin... > > This certainly deserves a goldstar. Andrew, are you going to do > the honors, please? Awarded! https://cygwin.com/goldstars/#TW -- 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: [GOLDSTAR] Re: [ANNOUNCEMENT] Release: mintty 2.0.1
Am 09.07.2015 um 22:25 schrieb Andrew Schulman: On Jul 3 23:18, Thomas Wolff wrote: After closing half of the open issues, I thought it’s a good time to release mintty. I’ve bumped the major version number to 2 to reflect the change of repository and maintainer and somehow catch up with cygwin... This certainly deserves a goldstar. Andrew, are you going to do the honors, please? Awarded! https://cygwin.com/goldstars/#TW Thank you, this is truely appreciated. Thomas -- 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
Return codes over 1 byte
mark06 mentioned this on IRC today and then left the channel about 1 hour later:
has anyone ever discussed exit codes above one byte? they are
valid on modern windows, but cygwin's bash will mess them
I was curious, so I googled it (I could not find an answer) and then
tried it out. I can confirm the what he said.
Cygwin Bash:
mike@executor ~
$ uname -a
CYGWIN_NT-10.0 executor 2.0.4(0.287/5/3) 2015-06-09 12:22 x86_64 Cygwin
mike@executor ~
$ cat return.c
int main (){ return 512; }
mike@executor ~
$ x86_64-w64-mingw32-gcc return.c -o return.exe
mike@executor ~
$ ./return.exe
mike@executor ~
$ echo $?
0
cmd.exe:
C:\cygwin64\home\mike>return.exe
C:\cygwin64\home\mike>echo %errorlevel%
512
-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: Return codes over 1 byte
On Thu, 2015-07-09 at 19:30 -0400, Michael DePaulo wrote: > mark06 mentioned this on IRC today and then left the channel about 1 hour > later: > > has anyone ever discussed exit codes above one byte? they are > valid on modern windows, but cygwin's bash will mess them > > I was curious, so I googled it (I could not find an answer) and then > tried it out. I can confirm the what he said. http://pubs.opengroup.org/onlinepubs/9699919799/functions/exit.html https://www.gnu.org/software/libc/manual/html_node/Exit-Status.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
Re: Return codes over 1 byte
On Thu, Jul 9, 2015 at 7:42 PM, Yaakov Selkowitz wrote: > On Thu, 2015-07-09 at 19:30 -0400, Michael DePaulo wrote: >> mark06 mentioned this on IRC today and then left the channel about 1 hour >> later: >> >> has anyone ever discussed exit codes above one byte? they are >> valid on modern windows, but cygwin's bash will mess them >> >> I was curious, so I googled it (I could not find an answer) and then >> tried it out. I can confirm the what he said. > > http://pubs.opengroup.org/onlinepubs/9699919799/functions/exit.html > https://www.gnu.org/software/libc/manual/html_node/Exit-Status.html > > -- > Yaakov Right, only the least significant 8 bits are outputted. So "257" becomes "1". I thought I read somewhere that the Cygwin mintty terminal + bash shell is supposed to be suitable for running native windows apps. Maybe I was thinking of the 1st paragraph on this page after the list of features: https://code.google.com/p/mintty/ Or maybe I was thinking about this reply: https://cygwin.com/ml/cygwin/2007-03/msg00758.html Either way, I feel like this should be documented somewhere. Perhaps I should submit a patch to add a section like "return codes" to to this page? https://cygwin.com/cygwin-ug-net/using-effectively.html https://cygwin.com/git/gitweb.cgi?p=newlib-cygwin.git;a=blob;f=winsup/doc/effectively.xml -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: Looking for 64-bit proxy
Marco Atzen wrote: > Hi Denis, > I uploaded on > http://matzeri.altervista.org/x86_64/connect-proxy/ > can you test it ? > > To install > setup-x86_64.exe -X -O -s http://matzeri.altervista.org -q -P connect-proxy I installed and tested this on two different Win7 PCs and, unfortunately, neither one worked. When I tried doing ssh login to a server via a proxy that works with the 32-bit connect-proxy, I got: On the first PC tried: ssh_exchange_identification: Connection closed by remote host On the second PC tried: 1 [main] ssh 1092 child_info_fork::abort: C:\cygwin64\bin\cygiconv-2.dll: Loaded to different address: parent(0x46) != child(0x2D) fork failed: Resource temporarily unavailable When I did the install I did get this: Note: Hand installation over to elevated child process. I don't know if that means anything. I did see from the /etc/setup install list that this is a single connect-proxy.exe executable. It showed the same size on both PCs in /usr/bin so doesn't look like an install problem. Is there anything else I can try, any debugging options/data? Denis -- 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
