Hi,
So, from the Cygwin FAQ:
*4.45.* Why doesn't Cygwin tcl/tk understand Cygwin paths?
The versions of Tcl/Tk distributed with Cygwin (e.g. cygtclsh80.exe,
cygwish80.exe) are not actually "Cygwin versions" of those tools. They
are built with the |-mno-cygwin| option to |gcc|, which means they
On 07/18/2009, Ulf Lindgren wrote:
before I reinstall my computer, I'd like to get your advice to what may
cause a strange behavior in cygwin bash. I have not found any hints in the
archives so as a last resort perhaps someone reading this knows what is going
on. I run a computer with Vista Ul
On Fri, Jul 17, 2009 at 11:19 PM, Larry Hall
(Cygwin) wrote:
> İsmail Dönmez wrote:
>>
>> Hi,
>>
>> I got a weird problem with Cygwin. I am using Cygwin 1.7 on Windows 7
>> RC (x64) and noticed that configure scripts are real slow and tried
>> some simple tests and to my surprise
>>
>> mkdir /foo
>
The mingw-xz package provides a version of the xz compression
library and tools built using the standard windows runtime library
and NOT cygwin. It is (or will be) used by setup.exe and is provided
specifically for that purpose. No other uses are supported. However,
for testing purposes it does pr
The xz package is the successor to lzma. Its command-line tools
support both .lzma files and the new .xz format, and it ships with
compatibility links so you don't even need to retrain your fingers:
'lzma', 'lzcat', etc, are all still present. However, you probably
should: .xz files are already be
The xz package is the successor to lzma. Its command-line tools
support both .lzma files and the new .xz format, and it ships with
compatibility links so you don't even need to retrain your fingers:
'lzma', 'lzcat', etc, are all still present. However, you probably
should: .xz files are already be
On Sat, Jul 18, 2009 at 02:55:29AM +0200, Thomas Steinbach wrote:
>Hello,
>
>since a few weeks I can't comp?ile my (native mingw) projet
>which was no problem until the gcc was renamed to gcc-3
>
>I get now this error and don't know what's wrong with my makefile.
>I renamed all executables to *-3,
Hello,
since a few weeks I can't compüile my (native mingw) projet
which was no problem until the gcc was renamed to gcc-3
I get now this error and don't know what's wrong with my makefile.
I renamed all executables to *-3, except as.exe but as.exe exist.
[...]
/usr/lib/gcc/i686-pc-cygwin/3.4.4
Hi all,
before I reinstall my computer, I'd like to get your advice to what may
cause
a strange behavior in cygwin bash. I have not found any hints in the
archives
so as a last resort perhaps someone reading this knows what is going on.
I run a computer with Vista Ultimate x64 and I have succe
On Sat, Jul 18, 2009 at 05:16:51AM -0600, Eric Blake wrote:
>So I see several possibilities:
>[snip]
My point, which I don't think you addressed in your long explanation, is
that there doesn't seem to be any "alternate stack" stuff going on in
the Windows code. Therefore, it seems like you could
MinTTY is a terminal emulator for Cygwin with a native Windows user
interface and minimalist design. Among its features are Unicode
support and a graphical options dialog. Its terminal emulation is
largely compatible with xterm, but it does not require an X server.
MinTTY is based on code from PuTT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Corinna Vinschen on 7/18/2009 3:45 AM:
>> AFAICT, the libsigsegv handler is overriding the "myfault" stuff in
>> Cygwin and is causing a fault for something that should be ignored. The
>> "fault" in this case is coming from our old friend
On Jul 17 23:15, Eric Blake wrote:
> Eric Blake byu.net> writes:
>
> > > As I said above, I assume that MVFS has a problem similar to what we
> > > have for remote HPFS. It's not sufficient to set only the minimal
> > > set of access flags in calls to NtCreateFile/NtOpenFile in some
> > > circum
On Jul 18 00:20, Christopher Faylor wrote:
> On Fri, Jul 17, 2009 at 10:55:13PM +, Eric Blake wrote:
> >Eric Blake byu.net> writes:
> >>Of course, given the code, that meant I wasn't using libsigsegv like I
> >>thought I was. So, with my typo corrected, I'm (unfortunately) still
> >>seeing li
14 matches
Mail list logo
