Re: Resolving Windows 64-bit linker issues

To expand on that (let's see if I can do this without accidentally sending again, oops!): Roman, I will get in touch with you on a separate email thread to see if we can find an optimal way to coordinate, something that satisfies our schedules and needs. Others please feel free to bug me any time by email ( dedgrant@gmail.com) or on freenode #ghc as dedgrant, PST hours. In the meantime I'll be auditing some of the related backlogged tickets on trac. If there's something I can do to help further the goal of a Windows Task Force page, please let me know. Pleased to meet everyone! Cheers, Darren On Mon, Feb 16, 2015 at 8:48 PM, Darren Grant wrote:

Thank you kindly for the great introduction. I hope I can be helpful here.

On Feb 16, 2015 7:47 AM, "Mikolaj Konarski" wrote:

...

Resending, since Roman's and Kyril's email addresses were mangled/missing.

...

Darren

Excellent! We have a Windows Task Force, consisting roughly of the folk in cc. So they would be the first group to ask.

(I think it would be very helpful to have a Windows Task Force home

...

that it’s easier to find the group.)

thanks for helping with Windows.

Simon

From: ghc-devs [mailto:ghc-devs-bounces@haskell.org] On Behalf Of Darren Grant Sent: 15 February 2015 07:36 To: ghc-devs@haskell.org Subject: Resolving Windows 64-bit linker issues

Hi all,

I notice there are a series of related long-standing issues subject to particular cygwin64 quirks, and I'd like to offer time to help resolve

On Mon, Feb 16, 2015 at 3:43 PM, Simon Peyton Jones wrote: page, so these

...

if possible

At this point I've had some exposure to the GHC build process (7.8.3), and have poked around the GHC linker to gain some low level insight.

Would anyone be available to fill me in on the current state of affairs with mingw64 GHCi linking? For instance, is there ongoing work, or perhaps a preferred direction but no available developer bandwidth to proceed?

Thank you.

Cheers,

Darren