
Yay! Thanks Paul! It's always good to have more folks confirm the problems are solved than not! Another cool direction 7.8 will allow is using the various llvm ffi bindings from ghci! On Wednesday, October 2, 2013, Paul Liu wrote:
Thanks. I've just built GHC HEAD on Mac OS X Lion, and tested by installing libraries with --enable-shared and loading a GLFW program into GHCi. Using ghci -fno-ghci-sandbox, everything works great including closing and restarting GL window multiple times. Can't wait for the official release of GHC 7.8!
thats the linker bug.
the glfw stuff has been tested on ghc HEAD / 7.7 by folks on #haskell-game in recent memory. GHCI + foreign libs should work fine now (modulo thread local storage related thing).
the historical element doesn't matter any more.
To the best of my knowledge, all such issues should be gone. Anyone who cares about making sure GHCI+ gui libs play nice, PLEASE test with HEAD.
the better this issue is properly tested (which i believe it has been),
more we can actually prevent it from happening. This requires people to test with HEAD GHCi now, rather than doing archaeology.
anyone who cares, please play with GHCI in HEAD. If your lib doesn't work with ghci, please report a bug. It would be a new bug because it wont' be the previous reasons it hasnt' worked.
tl;dr to the best of my knowledge this issue is resolved in HEAD. Test HEAD. Help us make sure it stays resolved by testing HEAD.
thanks -Carter
On Tue, Oct 1, 2013 at 1:20 PM, Paul Liu
wrote: I reported a problem with statically linked GLFW library on Mac OS X Lion in this thread:
http://www.haskell.org/pipermail/haskell-cafe/2012-January/097355.html
I do not know why this is broken on Mac OS X Lion, but not on Linux or Windows. There was an EnableGUI hack for GHC 7.2 (and previous versions) and OS X version before Lion, but it no longer works. So I'm not sure if it is OS X Lion, or GLFW, or GHC, or a combination of them that caused this problem.
Regards, Paul Liu
On Tue, Oct 1, 2013 at 7:04 AM, Carter Schonwald
wrote: Hey simon, the two issues that have recurrently bit ghci interaction with foreign GUI libs are 1) the ghci linker. This is fixed in head by now having ghci use the system linker 2) some GUI libs require thread local state, and ghci has a flag for that 3) I'm not aware of anyone reporting newly broken libs wrt GUI
bindings
when 7.6 rolled out. The only fix that's relevant to 7.8 is the dylinker bit, but that would have been a problem historically too.
I believe a number of folks in #haskell-game have recently tested
On Tue, Oct 1, 2013 at 12:09 PM, Carter Schonwald
wrote: the point one. (Though I should ask to double check)
At the very least, I'm not aware of hearing of such a 7.6 specific ghci breakage before.
On Tuesday, October 1, 2013, Simon Peyton-Jones wrote:
Dear GHC devs
See below (in red). I do not know the details of this, but it sounds like a pretty serious problem, and it used to work. Is whatever-it-is confirmed fixed in 7.8? Do we have a test that’ll trip if it breaks again?
(I’m
guessing that the latter might be hard.)
Thanks
Simon
-----Original Message----- From: Haskell-Cafe [mailto:haskell-cafe-bounces@haskell.org] On Behalf Of Paul Liu Sent: 30 September 2013 07:18 To: Conal Elliott Cc: Haskell Cafe Subject: Re: [Haskell-ca-- Regards, Paul Liu