On 2011-11-25, at 2:29 PM, Brandon Allbery wrote:

On Fri, Nov 25, 2011 at 14:08, Philippe Sismondi <psismondi@arqux.com> wrote:
I don't see why the architecture of macports stuff would make a difference. I should perhaps have said in the original post that I have no macports haskell software installed. I am not using the macports haskell-platform port. I am using the OS X Haskell Platform package downloaded from the web: Haskell Platform 2011.2.0.1-i386.pkg. To answer your question, though, here is the gtk2 macports info:

So, where did you get the gtk2hs stuff then?  Your SOE is clearly the gtk2hs version, and gtk2hs was evidently built against MacPorts.


I got everything using cabal-install. It did not work smoothly at first. I did:

cabal install soegtk

but this reported errors and suggested that I must first do

cabal install gtk2hs-buildtools

I did this. The above delivered some utility executables. I made these available on my PATH, and then did

cabal install soegtk

Your suggestion reminds me that installing soegtk caused an outpouring of messages about "ignoring libraries". So the problem may well have arisen at that point. I should probably look at the cabal packages for gtk2hs, or maybe contact the guys who put it together.

Actually, it is high time that I bite the bullet and learn about cabal internals anyway. I just HATE that kind of thing. I can hardly estimate the amount of time I have spent fighting with package management and library stuff in Common Lisp and other languages that live in a less than robust online echosystem.

Thanks for your help. I'll dig into the cabal side of gtk2hs.

- Phil -

--
brandon s allbery                                      allbery.b@gmail.com
wandering unix systems administrator (available)     (412) 475-9364 vm/sms