Re: [Mingw-w64-public] Custom toolchain build with gcc-4.4.3 (2009-12-24)

2009-12-27 Thread Grant Pedersen
> -Original Message- > From: Ozkan Sezer [mailto:seze...@gmail.com] > Sent: 25 December 2009 15:13 > To: mingw-w64-public@lists.sourceforge.net > Subject: [Mingw-w64-public] Custom toolchain build with gcc-4.4.3 > (2009-12-24) > > To anyone who might be interested: I updated my custom > w3

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

2008-06-11 Thread Grant Pedersen
Hi NightStrike & Kai, Have you had any luck with issues 2 - 5 below? Issue 5 is a showstopper for me at the moment. Thanks, Grant. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Grant Pedersen Sent: 15 May 2008 01:06 To: mingw-w64-pu

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 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

[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