Oleg Grenrus <oleg.gren...@iki.fi> writes: > Hi, > first some background: there is an issue with having Haskell on the > next OS X “El Capitan”: [1] caused by security updates in the > operating system. The cause is too old `unix` package, the same issue > as in [2]
I would like to understand the root-cause of the issue. It seems that OS X will now raise EPERM instead of EACCES when certain files are accessed. That being said, it's not at all clear to me which system call is failing or why. Could someone familiar with El Capitan describe what exactly is going on here? > Could someone verify that my understanding of the issue is correct, > i.e. how Cabal-the-tool and Cabal-the-library interoperate. > > For me it seems, that one of the easiest ways to fix the issue (for > the users), is to have a new release in 7.8 branch, with updated > `unix` dependency. Or is it there too might hassle to be possible? I will bring this up in next week's GHC meeting. Cheers, - Ben
signature.asc
Description: PGP signature
_______________________________________________ cabal-devel mailing list cabal-devel@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/cabal-devel
