>> mingw-w32-1.0-bin_i686-cygwin-1.5.25-15_20091228.tar.bz2 and
>> mingw-w64-1.0-bin_i686-cygwin-1.5.25-15_20091228.tar.bz2 builds under
>> 1.7.1 with no issues, so it's not a big deal. I'd be happy to test
>> out 1.7 based builds for you if you like.
>
> Could you run the testsuite on a 1.7 build
On Tue, Dec 29, 2009 at 7:39 PM, Chris Sutcliffe wrote:
> mingw-w32-1.0-bin_i686-cygwin-1.5.25-15_20091228.tar.bz2 and
> mingw-w64-1.0-bin_i686-cygwin-1.5.25-15_20091228.tar.bz2 builds under
> 1.7.1 with no issues, so it's not a big deal. I'd be happy to test
> out 1.7 based builds for you if you
Hi NightStrike,
>> Excellent, I will work on packaging GDB 7.0.1 for mingw-w32 initially.
>> Is there going to be an updated 1222(/23) build of mingw-w32 for
>> mingw or cygwin? Once I have a working mingw-w32 build, I'll see what
>> I can do to produce a mingw-w64 build.
>
> Chris, this is fant
Hi Kai,
>> I will create a simple test case over the holidays for this and send it to
>> you.
>
> Thanks
I'm having a heck of a time recreating the issue in a simple test
case. What I see happening with Emerge is that the C++ mangled name
seems to be mismatched between the export and the import
NightStrike, Mook: Let me know if Cliff needs a logon for the SSH server.
James K Beard
-Original Message-
From: NightStrike [mailto:nightstr...@gmail.com]
Sent: Tuesday, December 29, 2009 11:26 AM
To: Chris Sutcliffe
Cc: mingw-w64-public@lists.sourceforge.net
Subject: Re: [Mingw-w64-pu
On Thu, Dec 24, 2009 at 7:28 AM, Chris Sutcliffe wrote:
> Excellent, I will work on packaging GDB 7.0.1 for mingw-w32 initially.
> Is there going to be an updated 1222(/23) build of mingw-w32 for
> mingw or cygwin? Once I have a working mingw-w32 build, I'll see what
> I can do to produce a ming
