On Tue, Feb 28, 2012 at 2:16 AM, Simon Marlow marlo...@gmail.com wrote:
Ok, I buy that it's useful to be able to do this. I suggest you make a
ticket and describe the problem. Is it possible you'd be able to make a
patch to fix it too?
So I finally got around to taking a look at this. Sorry
On 18/02/2012 05:22, Evan Laforge wrote:
On Thu, Feb 16, 2012 at 4:27 AM, Simon Marlowmarlo...@gmail.com wrote:
I'm not sure why you're using the C++ compiler from hsc2hs, and I don't
think that is guaranteed to work. But maybe we can fix it if there's a
legitimate reason to want it.
Well,
On Thu, Feb 16, 2012 at 4:27 AM, Simon Marlow marlo...@gmail.com wrote:
I'm not sure why you're using the C++ compiler from hsc2hs, and I don't
think that is guaranteed to work. But maybe we can fix it if there's a
legitimate reason to want it.
Well, consider if you're writing c++ along with
On 15/02/2012 19:51, Evan Laforge wrote:
On Wed, Feb 15, 2012 at 11:17 AM, Eugene Crossercros...@average.org wrote:
On 02/15/2012 09:59 PM, Evan Laforge wrote:
Unfortunately, the result is I (apparently) can't use it now. Here's
how that happens: The change was to remove the dependency on
Recently a change was made to hsc2hs to fix this ticket:
http://hackage.haskell.org/trac/ghc/ticket/2897
Unfortunately, the result is I (apparently) can't use it now. Here's
how that happens: The change was to remove the dependency on HsFFI.h.
However, the solution is to create a little
On 02/15/2012 09:59 PM, Evan Laforge wrote:
Unfortunately, the result is I (apparently) can't use it now. Here's
how that happens: The change was to remove the dependency on HsFFI.h.
Evan, *if* including HsFFI.h is the only thing you need, you might try to add
-i HsFFI.h to your hsc2hs rule.
On Wed, Feb 15, 2012 at 11:17 AM, Eugene Crosser cros...@average.org wrote:
On 02/15/2012 09:59 PM, Evan Laforge wrote:
Unfortunately, the result is I (apparently) can't use it now. Here's
how that happens: The change was to remove the dependency on HsFFI.h.
Evan, *if* including HsFFI.h is
