On 5/23/08, Matthew Bentham [EMAIL PROTECTED] wrote:
My experience with the binary builds from mingw64 SourceForge has also been
that they suffer from the Vista access() problem, as we discussed on this
mailing list on Feb 24th 2008. I've included my notes from the time
(discussing the
- Original Message -
From: Sisyphus [EMAIL PROTECTED]
.
.
C:\_64\Cgcc -o try.exe try.c
gcc: CreateProcess: No such file or directory
Hmmm ... this is slightly different to what happens when I try to build
try.c using a mingw32 that *doesn't* have the access() fix:
- Original Message -
From: NightStrike [EMAIL PROTECTED]
To: Sisyphus [EMAIL PROTECTED]
Cc: mingw-w64-public@lists.sourceforge.net
Sent: Sunday, May 18, 2008 4:47 PM
Subject: Re: [Mingw-w64-public] Cannot #include windows.h
On 5/18/08, Sisyphus [EMAIL PROTECTED] wrote:
Hi,
C:\type
On 5/18/08, Sisyphus [EMAIL PROTECTED] wrote:
Hi,
C:\type try.c
#include windows.h
int main(void) {
return 1;
}
This should be no problem. Maybe you did not properly set the
environments. I use different source that already has mthread
(openmp). For example,
C:\temp\cmore a.c
On 5/18/08, Sisyphus [EMAIL PROTECTED] wrote:
As to what the problem *was* is now a little unclear to me. Perhaps it was
because I originally unzipped into C:\_64\mingw64 instead of a top level
folder. Or perhaps it was something to do with the way I had jumped through
all those hoops.
First,
- Original Message -
From: NightStrike [EMAIL PROTECTED]
.
.
I will spin a completely new fresh version of the toolchain (maybe
there was an error in there somewhere), run it on my Vista64 machine,
compile Hello World, and if it works, I'll upload it.
Let me know when that's done
