On 02/20/2012 10:46 AM, Evan Laforge wrote:
> Is there something that changed in 7.4.1 that would cause it to decide
> to interpret .hs files instead of loading their .o files? E.g.:
I don't *know* but could this have anything to do with this?
http://hackage.haskell.org/trac/ghc/ticket/5878
Eug
I don't know enough to understand if the "hard" troubles described by John
Meacham are real, but I think that even if they are not, the current situation
violates the "principle of least surprise" for the author of a module.
Such author may be unaware of the need to take special steps to make his
Hello Simon, thanks for your attention :)
On 02/16/2012 04:25 PM, Simon Marlow wrote:
>> I found that earlier versions of hsc2hs included HsFFI.h into the
[...]
>> As I understand, this situation means that while the ghc itself and
>> haskell programs compiled by it are largefile-capable, any thi
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 ru
Hello all,
I am new here, but I want to report what I suspect may be a problem.
I ran into it while using some third-party package from hackage on a
32bit Linux with ghc 7.4.1. I discovered that off_t fields in the .hsc
files in the package where interpreted as 32bit words. I suspected that
64bit
