Re: [Mingw-w64-public] Cannot #include

2008-05-18 Thread Sisyphus
- 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

Re: [Mingw-w64-public] Cannot #include

2008-05-18 Thread NightStrike
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. F

Re: [Mingw-w64-public] Cannot #include

2008-05-18 Thread Sisyphus
- Original Message - From: "NightStrike" <[EMAIL PROTECTED]> . . >> C:\_64>gcc -o try.exe try.c -v >> Using built-in specs. >> Target: x86_64-pc-mingw32 >> Configured with: >> ../build/gcc-svn/gcc/configure --target=x86_64-pc-mingw32 >> --pre >> fix=/var/tmp/w64 --with-sysroot=/var/tmp/w

Re: [Mingw-w64-public] Cannot #include

2008-05-18 Thread J. Little
On 5/18/08, Sisyphus <[EMAIL PROTECTED]> wrote: > Hi, > > C:\>type try.c > #include > > 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\c>more a.c #in

Re: [Mingw-w64-public] Several GCC issues

2008-05-18 Thread Kai Tietz
2008/5/18 Grant Pedersen <[EMAIL PROTECTED]>: > NightStrike wrote: >> The toolchain you are using is the cross compiler that runs on >> i686-pc-mingw and generates binaries for x86_64-pc-mingw. Now, the >> same Win64 operating system can run 32-bit and 64-bit code, so you can >> easily use the Win

Re: [Mingw-w64-public] Several GCC issues

2008-05-18 Thread Grant Pedersen
NightStrike wrote: > The toolchain you are using is the cross compiler that runs on > i686-pc-mingw and generates binaries for x86_64-pc-mingw. Now, the > same Win64 operating system can run 32-bit and 64-bit code, so you can > easily use the Win32>Win64 cross compiler on a native Win64 system (in

Re: [Mingw-w64-public] Several GCC issues

2008-05-18 Thread NightStrike
On 5/18/08, Grant Pedersen <[EMAIL PROTECTED]> wrote: > NightStrike wrote: > > On 5/14/08, Grant Pedersen <[EMAIL PROTECTED]> wrote: > >> 1. The following code works with MinGW: > >> > >>#include > >>int main(int argc, char **argv) {} > >> > >> but causes the following error with m

Re: [Mingw-w64-public] Several GCC issues

2008-05-18 Thread Grant Pedersen
NightStrike wrote: > On 5/14/08, Grant Pedersen <[EMAIL PROTECTED]> wrote: >> 1. The following code works with MinGW: >> >>#include >>int main(int argc, char **argv) {} >> >> but causes the following error with mingw-w64: > What is the full command that you are executing, and did

Re: [Mingw-w64-public] Cannot #include

2008-05-18 Thread NightStrike
On 5/18/08, Sisyphus <[EMAIL PROTECTED]> wrote: > > - Original Message - From: "NightStrike" <[EMAIL PROTECTED]> > To: "Sisyphus" <[EMAIL PROTECTED]> > Cc: > Sent: Sunday, May 18, 2008 4:47 PM > Subject: Re: [Mingw-w64-public] Cannot #include > > > > On 5/18/08, Sisyphus <[EMAIL PROTECTED

Re: [Mingw-w64-public] Cannot #include

2008-05-18 Thread Sisyphus
- Original Message - From: "NightStrike" <[EMAIL PROTECTED]> To: "Sisyphus" <[EMAIL PROTECTED]> Cc: Sent: Sunday, May 18, 2008 4:47 PM Subject: Re: [Mingw-w64-public] Cannot #include > On 5/18/08, Sisyphus <[EMAIL PROTECTED]> wrote: >> Hi, >> >> C:\>type try.c >> #include >> >> int m