You've got an object file compiled with 32-bit code, hence the relocation
error. fPIC won't help you much (the linker error isn't helpful.) It's a matter
of sifting through the make output to find the file or files that aren't
compiled in 64-bit mode.
Sent from my Verizon Wireless BlackBerry
Llvm is also a good reference for compiler plugin design; it would appear that
Scala borrowed from their approach.
-scooter
Sent from my Verizon Wireless BlackBerry
-Original Message-
From: austin seipp a...@hacks.yi.org
Sender: glasgow-haskell-users-boun...@haskell.org
Date: Fri, 21
I'm not sure if your statement regarding the decoupling between contributors
and VCSes holds water. The VCS is definitely a factor, but certainly not the
only one. I've been demotivated by VCSes before and it has directly impacted
whether I continued my involvement. Granted that the VCS was
Depends on what your kernel supports. But that's just infrastructure, so
(theoretically) it should just be invisible to the Haskell runtime user.
Surprised that the RT wasn't using the more advanced interfaces. Web servers
have been using them for years; that's why they exist.
Sent from my
Claus:
Respectfully, No duh! as schoolkids here in the US like to say when someone
points out the obvious to them.
And impossible is the right word since the predicate evaluates to a boolean.
Since false is the outcome, impossible refers correctly to the status of
fetching the documentation.
Claus:
scion-server mimics a GHCi command line, of sorts. scion-server is used very
successfully to syntax-highlight the Eclipse editor, show a source's outline,
provide type information when hovering over a name, and provide completions.
That's not the problem, per se. Let's say I'm hovering
This is indicative of a 32-bit object being linked into the shared library,
FWIW.
Sent from my Verizon Wireless BlackBerry
-Original Message-
From: Vivian McPhail haskell.vivian.mcph...@gmail.com
Sender: glasgow-haskell-users-boun...@haskell.org
Date: Wed, 29 Sep 2010 19:25:10
To:
Christian:
Is it possible that you might have code compiled with an older version of ghc
lying around in an odd place in your build hierarchy? I would imagine that you
upgraded cabal-installed packages. If for some reason you copied or used rsync
to replicate a directory tree onto the older
C++ template instantiations are exported as weak linker symbols. It's just that
the linker elides all of the implementations.
Sent from my Verizon Wireless BlackBerry
-Original Message-
From: Johan Tibell johan.tib...@gmail.com
Sender: glasgow-haskell-users-boun...@haskell.org
Date: Thu,
It seems to me that the documentation could be further refined:
An acquisition operation cannot be interrupted when the requested resource is
available; the resource is successfully acquired and the subsequent computation
can proceed. On the other hand, if the resource is unavailable, then the
It seems to me, in the absence of any other fallback, that the C backend should
stay around. Assume that one is porting to a new platform, the C backend at
least gives one code from which to bootstrap.
Calling convention handling: weak argument IMHO for ditching. Sounds like
refactoring is
Before the Pile on Scooter fest starts, bear in mind that LLVM effectively
restricts you to its current backends. As the guy who started CellSPU in LLVM
and who needs a good couple of research months off to finish it, think this
through. Carefully.
FWIW: I lead a computer systems research
I'm personally pessimistic about the STI Cell, but it's a reasonable example
wrt the difficulty of writing the backends. Barring the data and message
orchestration, which also aflicts GPUs, there's the decision function as to
when to migrate a computation to the accelerator (GPU, SPU, ...) Not
Do we have a native LLVM bitcode writer or is it still FFI?
--Original Message--
From: Thomas DuBuisson
Sender: glasgow-haskell-users-boun...@haskell.org
To: han
Cc: glasgow-haskell-users@haskell.org
Subject: Re: Compiling to ANSI C
Sent: Nov 7, 2009 09:56
If I were you, I'd look at
Believe it when it shows up in GHC pristine.
--Original Message--
From: Thomas DuBuisson
To: scooter@gmail.com
Cc: han
Cc: glasgow-haskell-users@haskell.org
Subject: Re: Compiling to ANSI C
Sent: Nov 7, 2009 11:28
On Sat, Nov 7, 2009 at 11:16 AM, scooter@gmail.com wrote:
Do we
Is there a good motivating example for recursive do? So far, I haven't grokked
the various use cases, which are pretty terse. Maybe the syntax sugar gets in
the way (dangling lets are a good case in point).
It's a bit like grokking a Monad: it's the way to alter state, through a chain
of
16 matches
Mail list logo
