Hi Axis,

I'm looking at my notes from my (brief) attempt to try sandboxes with ghc-ios, and it looks like one major issue is that the --builddir flag isn't paid attention to when installing into a sandbox, thus the object files from different architectures get mixed up. That will likely need a patch to cabal (I don't think many of the cabal devs are using multiple architectures/cross compilation) — filing a bug would be great.

Best
Luke


On Wed, Oct 15, 2014 at 1:57 PM, Axis Sivitz <axis@asivitz.com> wrote:
Is anyone using ghc-ios with cabal sandbox? I am having trouble with it.

I can 'cabal-ios install’ fine. That installs the packages properly in the sandbox for arm and x86.

But the ghc-ios script doesn’t use the sandbox environment. And running a simple 'cabal exec ghc-ios …’ clobbers the package-db path:

I get...
"Using binary package database: /…/sandbox/x86_64-osx-ghc-7.8.3-packages.conf.d/package.cache”
and then a bunch of errors like:
Bad interface file: /usr/local/lib/ghc-7.8.3/base-4.7.0.1/Prelude.hi
        magic number mismatch: old/corrupt interface file? (wanted 129742, got 33214052)

I guess the best solution is for cabal’s exec command to respect the arguments that cabal-ios provides. But maybe in the meantime perhaps I can tweak the ghc-ios script to add an argument to look for the presence of sandboxing, unless anyone else has a better idea.

Thanks,
Axis

_______________________________________________
iPhone mailing list
iPhone@haskell.org
http://www.haskell.org/mailman/listinfo/iphone