This is great. Adding /opt/local/lib by hand to package.conf did it. I didn’t see the problems that you report, perhaps you didn’t launch ghci with “-L/opt/local/lib”?

Don’t forget to include this change in the next release!

yes, I can reproduce this. The reason seems to be that we don’t include /opt/local/lib in the package file. Fixing that by hand, I now get a segmentation fault after calling “main” in ghci. GDB says:

linking … done.

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0×83f87795
[Switching to process 16916 thread 0×1f03]
0×90002fe0 in strcmp ()
(gdb) bt
#0 0×90002fe0 in strcmp ()
#1 0×00fa5aa1 in FcPatternPosition ()
Cannot access memory at address 0×3

I don’t know if we’re at fault here or ghc. The program I tested this with compiles and runs with no problems (even without adding the /opt/local/lib path to the package.conf file). The function names suggest that some arguments passed to Gtk are incorrect. Any thoughts, Duncan?

I also have the libgthread problem here. Os X Intel with a hand built version of Gtk2hs and a hand built GHC 6.7. GTK installed via MacPorts

The file libgthread-2.0.dylib is found at /opt/local/lib, and I launched ghci with “-L/opt/local/lib” to make sure it can find it, but still the same.