Re: 64-bit setup: not a valid win32 application
On Tue, Jul 23, 2013 at 12:10 PM, Ryan Johnson wrote: > > I tried to install 64-bit cygwin today, but I keep encountering the error > message "setup-x86_64.exe is not a valid Win32 application." I had the same problem today on Windows 8. The solution was to download the 64-bit setup program from a mirror instead of the cygwin.com site. Try here: * http://mirror.mcs.anl.gov/cygwin/64bit/setup64.exe -- Darik Horn -- 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: Question about rxvt and the TERM variable
On Thu, Sep 4, 2014 at 9:25 PM, Brandon Huber wrote: > > are there any instances where using "xterm" would cause incorrect or > unexpected behavior? Compatibility commentary is available at: * http://en.wikipedia.org/wiki/Rxvt * The top of the /usr/share/doc/rxvt/etc/rxvt.terminfo file. * The "Xterm features not supported" section in the /usr/share/doc/rxvt/README.xvt file. The primary difference seems to be that rxvt emulates a VT102 whereas xterm emulates a VT220. > I can see a list of differences in terminfo settings by using the > infocmp utility, but I'm not sure how to interpret the results. That is exactly why you should ask the person who wants to change system defaults to explain how the infocmp differences are inconsequential. -- 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: vim can't write /etc/hosts
On Thu, Sep 4, 2014 at 4:33 PM, Frank Fesevur wrote: > > Why can't vim write the file, or even better the symlinked file? I'm > quite sure editing the symlink works in Win7, but can try tomorrow. Starting "C:\Cygwin\bin\mintty.exe" through a "Run As Administrator" context doesn't produce an elevated bash prompt on my Windows 8 workstation. Starting the "Command Prompt (Admin)" shortcut instead and running "C:\Cygwin\bin\bash.exe --login" inside should give you the expected behavior. -- 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 website uses http: (not https:) for .exe downloads, allowing man-in-the-middle attack
Note that GPG signatures are published for the Cygwin setup binaries: * http://cygwin.com/setup-x86.exe.sig * http://cygwin.com/setup-x86_64.exe.sig -- 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
bzr: Value "/etc/ssl/certs/ca-certificates.crt" is not valid for "ssl.ca_certs"
The bzr package in Cygwin uses an incorrect default path for the system certificate list, which causes this error: $ bzr clone lp:~foo/bar Value "/etc/ssl/certs/ca-certificates.crt" is not valid for "ssl.ca_certs" No valid trusted SSL CA certificates file set. See 'bzr help ssl.ca_certs' for more information on setting trusted CAs. See `bzr help ssl.ca_certs` for how to specify trusted CAcertificates. Pass -Ossl.cert_reqs=none to disable certificate verification entirely. bzr: ERROR: _ssl.c:323: No root certificates specified for verification of other-side certificates. The problem can be resolved on Cygwin by creating a configuration file like this: # $HOME/.bazaar/bazaar.conf [DEFAULT] ssl.ca_certs=/usr/ssl/certs/ca-bundle.crt Or by overriding the default path on the command line like this: $ bzr clone -Ossl.ca_certs=/usr/ssl/certs/ca-bundle.crt lp:~foo/bar -- Darik Horn -- 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: why no gpg-agent for Cygwin?
On Thu, Sep 3, 2015 at 3:20 PM, Andrew Schulman wrote: > > So, why isn't there a gpg-agent for Cygwin? Pageant does the same thing as gpg-agent, but works on both sides of the Cygwin environment. Install the ssh-pageant package through setup.exe and put something like this into the default shell configuration: # .bashrc eval $(ssh-pageant -ra /tmp/.ssh-pageant) -- 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: why no gpg-agent for Cygwin?
On Fri, Sep 4, 2015 at 1:08 PM, Darik Horn wrote: > > Pageant does the same thing as gpg-agent, but works on both sides of > the Cygwin environment. Oops, GPG: This suggestion won't work in something that looks like a normal Cygwin environment. -- 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: compile ncurses "hello world" to run independent of cygwin?
On Sun, Nov 1, 2015 at 10:04 PM, Daniel Goldman wrote: > > What am I doing wrong? How do I use cygwin to compile the test ncurses > program so it can run in a dos terminal, independent of cygwin? I looked > around the docs and archives and could not figure out. Was libncurses built for the MinGW target on the Cygwin host? Keep in mind that this job is a cross compile, so ncurses and every other dependency must be built for the MinGW runtime. The mingw-* and mingw64-* packages for Cygwin are just the toolchain plus some essentials; there is no mingw-libncurses-devel package in distribution. Unless there is a specific reason to cross through Cygwin, it could be easier to use the native MinGW environment directly: * http://www.mingw.org/wiki/Getting_Started And link against the ncurses redistributable: * http://invisible-mirror.net/ncurses/ncurses.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: compile ncurses "hello world" to run independent of cygwin?
On Mon, Nov 2, 2015 at 10:14 AM, Greg Freemyer wrote: > > The last time I checked (a few years ago), my understanding was the > cygwin dll's were licensed such that any programs using them had to be > GPL (or equivalent). > > Is that wrong? No, that is still the case: * https://cygwin.com/licensing.html > If so, anyone wanting to write a commercial tool has to avoid the > cygwin's core dll's. Or buy a license. > Does using mingw do so? No, it is easier to avoid GPL obligations by using the MinGW runtime: * http://www.mingw.org/license -- 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 Win-stall on 98, SSH to Mandrake won't run GUI
The easiest solution is to install the rxvt package and use it instead of "Cygwin Bash Shell" in the start menu. You'll need to create a shortcut to rxvt. I use this as my shortcut target: C:\Cygwin\bin\rxvt.exe -rv -geometry 80x40 -fn "Lucida Console" +sb -sl 1024 -e /usr/bin/bash --login -i An alternative solution is to configure the termcap or terminfo on the remote host to recognize the cygwin terminal type. Botl J. Rokit wrote: I will be apologizing to Cygwin-XFree list, because I sent a message to you by accident. I apologize for spamming. Everyone, I hate to ask you this, but I'm just too green. Before we get into the rightful rattletrap about GUI crutches, my end users are all Win-dependent, and anything that I can remotely kick off and force their hand at is more beautiful than you'd ever know. I have installed Cygwin on a Windows 98 and 2000 computer (twice over, two different boxes), and have been able to command-prompt over to my new Mandrake Linux 9.1 computers. I can even get to root, of course! I simply can't get the GUI to come up, when I attempt to run things like MCC (Mandrake Control Center). I get this message: Unknown terminal: cygwin Check the TERM environment variable. Also make sure that the terminal is defined in the terminfo database. Alternatively, set the TERMCAP environment variable to the desired termcap entry. tset: unknown terminal type cygwin Terminal type? Now at this point, I get to enter either "cygwin" (which ends up saying, again, "Unknown terminal: cygwin") or "vt100" (just to shut it up). At that point, I get a remark that says Erase is backspace. And that's that. Being incredibly new, I'm not even certain *where* to look. I can say, however, that I *suspect* that it's because I haven't defined something on either of my linux b0x3n. And that I'm a total newbie. Thanks for the help. Seriously. Eric Geater Botl J. Rokit -- 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/
