The ghci bug goes away when you use a ghc head snapshot from late summer?
Great!
On Wednesday, September 18, 2013, Jan-Philip Loos wrote:
> Sadly I was not able to use your build directly, because ghc(i)
> searched libs in a invalid path (it seems to be wired to one of your
> directories). I tri
Christian,
Yes, ghc 7.7/7.8 *should* fix all the ghci linker related problems on
platforms that support dynamic linking!
If (or anyone else) finds problems with the ghci linker on 7.7, please
report them post haste!
I'm also glad to hear that someone's finally tested out the new ghci
functionalit
Here's a binary dist of my build:
https://www.dropbox.com/s/d37rij0dnvjiqqy/ghc-7.7.20130915-x86_64-apple-darwin.tar.bz2
In case someone wants to confirm my findings.
Cheers,
Christiaan
On Sep 16, 2013, at 2:24 PM, Christiaan Baaij
wrote:
> Hi,
>
> I saw the same issue/crash on my machine u
Hi,
I saw the same issue/crash on my machine using ghc 7.6.3.
I just build a "perf" build of GHC-head with
"85a9e2468dc74b9e5ccde0dd61be86219fd323a2" as the latest commit.
Now running, I get:
1) > cabal install bindings-glfw
2) > ghci
3) ghci> :m Bindings.GLFW
4) ghci> Bindings.GLFW.c'glfwInit
5
> What I do for GLFW is use a dylib, then you don't rely on GHCi's static-ish
> linker.
> The only wrinkle is figuring out where you want the dylib.
> I think homebrew will put one in /usr/local/lib, which works out nicely, but
> they don't have GLFW 3 yet.
> Another option is to build the dylib
relatedly: johnW has nightly builds of GHC head for OS X 10.8 available for
download for those who would be up for braving such experimentation
ghc.newartisans.com
On Sat, Jul 13, 2013 at 10:16 PM, Jason Dagit wrote:
> On Sat, Jul 13, 2013 at 6:44 PM, Carter Schonwald
> wrote:
> > has anyone t
On Sat, Jul 13, 2013 at 6:44 PM, Carter Schonwald
wrote:
> has anyone tried using ghci HEAD? If the problem is linker based... perhaps
> ghci that uses the system Dylinker might resolve it?
If someone gets brave and tries this I'd love to hear if it works.
Although, that's too new for something w
On Sat, Jul 13, 2013 at 5:32 PM, Anthony Cowley wrote:
> On Jul 13, 2013, at 8:04 PM, Jason Dagit wrote:
>
>> On Sat, Jul 13, 2013 at 4:39 PM, Mark Lentczner
>> wrote:
>>> Bizarre - this just happened to me today, too. Anyone? Did you figure out a
>>> work around? For the record, I'm trying to b
has anyone tried using ghci HEAD? If the problem is linker based... perhaps
ghci that uses the system Dylinker might resolve it?
-Carter
On Sat, Jul 13, 2013 at 8:32 PM, Anthony Cowley wrote:
> On Jul 13, 2013, at 8:04 PM, Jason Dagit wrote:
>
> > On Sat, Jul 13, 2013 at 4:39 PM, Mark Lentczn
On Jul 13, 2013, at 8:04 PM, Jason Dagit wrote:
> On Sat, Jul 13, 2013 at 4:39 PM, Mark Lentczner
> wrote:
>> Bizarre - this just happened to me today, too. Anyone? Did you figure out a
>> work around? For the record, I'm trying to bring Euterpea up.
>
> After some digging, experimenting, askin
On Sat, Jul 13, 2013 at 4:39 PM, Mark Lentczner
wrote:
> Bizarre - this just happened to me today, too. Anyone? Did you figure out a
> work around? For the record, I'm trying to bring Euterpea up.
After some digging, experimenting, asking around, and head scratching
my best guesses are:
* GHCi
Bizarre - this just happened to me today, too. Anyone? Did you figure out a
work around? For the record, I'm trying to bring Euterpea up.
My system is OS X 10.8.4, and I'm running HP 2013.2, so 7.6.3. And
GLFW-0.5.1.0.
- Mark
___
Haskell-Cafe mailing li
Here's a problem variations of which have been plaguing the Haskell
community for as long as I can remember.
To see it for yourself:
1.) Be running OS X
2.) install GLFW-b-1.0.0 (you may need to cabal update) [1]
3.) ghci -package GLFW-b
4.) import Graphics.UI.GLFW as GLFW
5.) GLFW.init
Security
13 matches
Mail list logo
