Mark, On 11.11.2010, at 08:27, Mark Spezzano wrote:
Hi Axel,
The error "file was build for unsupported file format which is not the architecture being linked (i386)" comes up soon after starting to install gtk via cabal.
gtk is "installed" (at least, it comes up in ghc-pkg as installed) but then when linking threadscope or another gtk-reliant tool it fails during the final linking phase.
It spits out a long list of functions that it can't link to.
Before we move this discussion to gtk2hs-devel@lists.sourceforge.net , I'd like to confirm that this is our problem. - what version of Gtk+ do you have? (run "pkg-config --modversion gtk +-2.0") - are the functions that cannot be linked to part of Gtk+ or of the Haskell gtk package (i.e. send us some of the error messages containing the function names) - what ghc are you using ("ghc --version") I suspect that the Gtk+ libraries and ghc do not agree on the architecture. Cheers, Axel
Mark
On 11/11/2010, at 5:40 PM, Axel Simon wrote:
Hi Mark,
On 11.11.2010, at 03:13, Mark Spezzano wrote:
Hi,
I'm running Mac OS X Snow Leopard. I've done a "sudo cabal install gtk --global" on my system, and it warns me that "file was built for unsupported file format which is not the architecture being linked (i386)". What does this refer to?
Subsequently, nothing else _links_ properly with gtk.
This might be a gtk problem. Does this happen very early or only during linking? Could you check what
cabal build -v
throws up? (Also: Did you install gtk2hs-buildtools first?)
Cheers, Axel
For example, hp2any-manager (or other tools) all fail during linking with gtk.
Am I doing something wrong?
Thanks,
Mark _______________________________________________ Libraries mailing list Libraries@haskell.org http://www.haskell.org/mailman/listinfo/libraries