> In your attachment I see DISK FULL errors being reported by
> CreateFile. It would not surprise me if the code that checks for "I
> can't create this because it's in use" was getting confused by a "I
> can't create this because there's no room" return value. If that's
> the case it would defini
I just downloaded cygwin 1.5.24-2 (just a couple of hours ago) and
compiled the following program with "gcc -ansi fred.c"
(NOTE the "-ansi" keyword):
#define pid_t fred was here
#include
int main(void)
{
printf("hello, world\n");
return (0);
}
And got the following result:
In file inc
On 10 November 2007 06:49, Peter Keller wrote:
> Ok, here's another chance. I'd been having this problem too, which was
> fixed by deleting the bash.lst.gz. I've attached it.
Great, thanks!
/tmp/setup $ od -tx1 -Ax bash.lst.gz
00 1f 8b 08 00 00 00 00 00 00 0b
0a
Looks like it got
Roberto Bagnara wrote:
>
> Where can I find it? (From the installer it seems that
> the latest available version is 3.4.4, but this is really
> unusable for serious C++ development.)
There's too much on this subject in the archives to be summarized. Why
not look yourself?
--
Unsubscribe info:
Where can I find it? (From the installer it seems that
the latest available version is 3.4.4, but this is really
unusable for serious C++ development.)
All the best,
Roberto
--
Prof. Roberto Bagnara
Computer Science Group
Department of Mathematics, University of Parma, Italy
http://www.cs.u
When I modify files with cygwin's vim, they become inaccessible. It seems the
permissions are getting changed when I save the file. Any idea why this is
happening? This does not happen from a bash shell, only when I directly
launch vim from a windows cmd.exe window. See below.
D:\ver
Microsoft Win
6 matches
Mail list logo
