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

2013-01-23 Thread Kai Tietz
problem? At least a few have been fixed. > >> Thanks, >> Grant. >> >> >> -Original Message- >> From: mingw-w64-public-boun...@lists.sourceforge.net >> [mailto:mingw-w64-public-boun...@lists.sourceforge.net] On Behalf Of Grant >> Pedersen >> Se

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

2013-01-23 Thread NightStrike
t. > > > -Original Message- > From: mingw-w64-public-boun...@lists.sourceforge.net > [mailto:mingw-w64-public-boun...@lists.sourceforge.net] On Behalf Of Grant > Pedersen > Sent: 15 May 2008 01:06 > To: mingw-w64-public@lists.sourceforge.net > Subject: [Mingw-w64-public]

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

2008-06-11 Thread Grant Pedersen
blic@lists.sourceforge.net Subject: [Mingw-w64-public] Several GCC issues I'm using mingw-w64 (i686 20080420) for the first time and have noticed some differences in its behaviour compared to MinGW. If anyone can help me with the following issues it would be greatly appreciated! 1. The following code w

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] Several GCC issues

2008-05-17 Thread NightStrike
On 5/14/08, Grant Pedersen <[EMAIL PROTECTED]> wrote: > I'm using mingw-w64 (i686 20080420) for the first time and have noticed some > differences in its behaviour compared to MinGW. If anyone can help me with > the following issues it would be greatly appreciated! Sure, np. Welcome! > 1. The f

[Mingw-w64-public] Several GCC issues

2008-05-14 Thread Grant Pedersen
I'm using mingw-w64 (i686 20080420) for the first time and have noticed some differences in its behaviour compared to MinGW. If anyone can help me with the following issues it would be greatly appreciated! 1. The following code works with MinGW: #include int main(int argc, char