- Glasgow-haskell-users

Mac OS X: compiling for 10.5 under 10.6
by Soenke Hahn 07 Jun '12

07 Jun '12

Hi! I was trying to use the ghc on a system with OS X 10.6 to compile for both 10.6 and 10.5 (and hopefully 10.7). In the past (with ghc-7.2.2 IIRC) I had luck with if os(darwin) cc-options: -isysroot /Developer/SDKs/MacOSX10.5.sdk -mmacosx-version-min=10.5 ld-options: -isysroot /Developer/SDKs/MacOSX10.5.sdk -mmacosx-version-min=10.5 in the cabal file, but with ghc-7.4.1 (from Haskell-Platform-2012.2.0.0) I get linker errors: Undefined symbols: "_fopen$DARWIN_EXTSN", referenced from: _procRtsOpts in libHSrts.a(RtsFlags.o) _initProfiling2 in libHSrts.a(ProfHeap.o) _exitHpc in libHSrts.a(Hpc.o) _startupHpc in libHSrts.a(Hpc.o) "_fopen$UNIX2003", referenced from: _loadArchive in libHSrts.a(Linker.o) _addDLL in libHSrts.a(Linker.o) "_kevent64", referenced from: _s3VN_info in libHSbase-4.5.0.0.a(KQueue__166.o) ld: symbol(s) not found If I remove the backward-compatibility flags from the cabal file, everything works fine. (I assume it won't run on OS X 10.5 then, of course.) If I understand correctly the RTS and the base library in ghc-7.4.1 depend on a newer version of the OS X SDK (>= 10.6). Is there an easy way to work around this version constraint? If not, does that mean, ghc-7.4.1 does not support OS X 10.5? Thanks, Sönke

3 2

Re: [Haskell-beginners] GHC7.4.1 -> LLVM ->W64
by Antoine Latter 05 Jun '12

05 Jun '12

On Tue, Jun 5, 2012 at 1:49 AM, Alexander.Vladislav.Popov <alexander.vladislav.popov(a)gmail.com> wrote: > Hi Haskellers, > > I want to build 64-bit Windows application. > Will 64-bit mingw and compilation via LLVM help me? > Who will shed light on it and lead me through darkened forest of my search? > If you're talking about using GHC to do this you might be better off asking on the GHC-Users list (which I've CC'd, so I guess you've already asked them!). I know that folks were spending time on making GHC work for Win-64, but I don't remember if it has shipped. Antoine

2 1

Source Location of DataCon objects in GHC 7.4.1 API
by JP Moresmau 05 Jun '12

05 Jun '12

Hello I have a failing test in BuildWrapper when moving from GHC 7.0.4 to 7.4.1. As far I can tell, in the TypecheckedSource I get DataCon objects that have no location info, and hence I can't retrieve them by location... Which is useful in a IDE (tell me what's under my mouse cursor, tell me where else it's used). Given the simple data declaration: data DataT=MkData {name :: String} In 7.0.4 I obtain a hierarchy that ends in FunBind (on a Var called "name")/MatchGroup/Match/ConPatOut and the contained DataCon named "MkData" has a SrcSpan associated with it, and so do the Var, MatchGroup and Match. In 7.4.1 I have the same hierarchy but the DataCon tells me "no location info". The Var "name" has a location, but the MatchGroup and Match don't either. Is it a normal change? Do I need to change something in the way I load the module? Is it a regression? Thanks! -- JP Moresmau http://jpmoresmau.blogspot.com/

4 8

Prelude for type-level programming
by Etienne Laurin 04 Jun '12

04 Jun '12

Hello, To experiment with some of GHC's new features in HEAD, I have started ported part of the Prelude from values and functions to types and constraints. For example: comparing lists. instance Compare '[] '[] EQ instance Compare '[] (x ': xs) LT instance Compare (x ': xs) '[] GT instance (Compare x y o, Case o [ EQ --> Compare xs ys r, o --> o ~ r ]) => Compare (x ': xs) (y ': ys) r Prelude.Type> T :: (Compare '[I 1, I 2] '[I 1, I 3] a) => T a LT Sometimes I get nice error messages. Prelude.Type> T :: If (I 1 == I 2) (a ~ "hello") (a ~ 3) => T a Kind mis-match The left argument of the equality predicate had kind `Symbol', but `3' has kind `Nat' But often GHC refuses to type large constraints when there are too many constraint kinds and free variables. It also gets confused if I pretend to use higher-order kinds. instance ((a >>= Const b) c) => (a >> b) c Kind mis-match The first argument of `>>' should have kind `k0 k1', but `a' has kind `k0 k1' In the instance declaration for `(a >> b) c' I'm not sure yet how this is useful this, but I hope it can at least entertain a few people and stress-test the typechecker. http://code.atnnn.com/projects/type-prelude/repository/entry/Prelude/Type.hs darcs get http://code.atnnn.com/darcs/type-prelude/ Etienne Laurin

2 2

Understanding ghc-pkg dependencies when not using cabal
by Tim Cuthbertson 02 Jun '12

02 Jun '12

Hi all, I'm very interested in distributing ghc packages via zero-install [0]. I'm excited about ghc 7.4's ${pkgroot} support, since it means that many packages could now be made relocatable (as long as they don't need to know about paths to resources, etc). But I'm having some trouble understanding exactly what relationships exist between packages and when packages are needed / used. I have a lot of questions. Answering all of them would be wonderful, but even just some at least would be handy too ;) For an example, lets use ansi-terminal [1] (and assume we're building it on a unix host) ansi-terminal depends on `base` and `unix` packages. Do these need to be present in source form, or just in "compiled package" form? I'm assuming the latter. (by "compiled package", I mean the stuff that ends up in e.g ~/.cabal/lib/PACKAGENAME) When I built ansi-terminal, the package.conf I got out of `cabal register` had the following field: depends: base-4.5.0.0-6db966b4cf8c1a91188e66d354ba065e unix-2.5.1.0-c004d6a0692bba682bbf2ac7b61d8322 So presumably this is the exact version that was used for compilation. Obviously the first part is the version, but what is the second part? Is it the abi-hash of the library that was used at compile time? If I want to use ansi-terminal in a program that I'm compiling, how strict are these dependencies? Will a `unix` package of a different version and the same abi-hash be acceptable? Does it need to be strictly _newer_ than 2.5.1.0 (and still have the same abi-hash)? Or is this an exact dependency? If I distribute the `unix` library in compiled form, how likely is it that a given compiled version of `unix` will satisfy the requirement? If I have compiled two libraries that both depend on `unix`, but they ended up referencing a different abi-hash of `unix` (maybe I compiled them on a different computer, or on slightly different versions of the source), what happens when I try to compile an application that depends on these two libraries? I presume it couldn't work, even if I had registered both versions of `unix` simultaneously (is this even possible to do?). Under what circumstances will the same package source code (e.g "unix-2.5.1.0") have two different abi-hashes? From [2], it sounds like only major GHC version changes should affect it. Is the abi-hash consistent on different platforms (assuming the same major GHC version is used)? Can the output of `ghc --abi-hash` (with no arguments) be used as a "linkage" restriction? (i.e if I have the exact same source and two versions of ghc with the same abi-hash, will the compiled library necessarily end up with the same abi-hash in both cases?). If the `unix` package releases a new version that is compatible with ansi-terminal, what would I have to do to get this updated code into my application (that depends on ansi-terminal)? - install new version of `unix`, and recompile my application - as above, but also rebuilding the current version of `ansi-terminal` before I rebuild my application (despite ansi-terminal not actually changing itself) Perhaps the above question could be rephrased as "if a new version of `unix` is source-compatible with the previous, what recompilation (if any) of downstream libraries is / could be required? I know that ghc compiles applications statically by default. Given this, I'm a little confused by the lifetime of packages in ghc. Are packages (in the sense of "the stuff that is listed by `ghc-pkg list`") only required at compilation time? If I run a precompiled program that depends on another haskell package which has been compiled as a shared library, does this mean I need the ghc package to be registered, or is it sufficient to just have the compiled .so on my $LD_LIBRARY_PATH? Apologies for the large number of questions, and thanks for your time. - Tim. [0]: http://0install.net/ [1]: http://hackage.haskell.org/package/ansi-terminal-0.5.5 [2]: http://hackage.haskell.org/trac/ghc/wiki/Commentary/Packages

2 2

can't compile ghc-7.4.1: No rule to make target `libraries/process/ghc.mk'
by Tim Cuthbertson 30 May '12

30 May '12

I've rm -rf'd my ~/.cabal to ensure old stuff doesn't get in the way, installed all the dependencies (on fedora 17, bootstrapping with ghc-7.0.4), unpacked the ghc-7.4.1 tarball, and run: ./configure --prefix=`pwd`/installed && make && make install and here's the log: https://gist.github.com/20dd47cfac4c8bbe498c (sorry I missed the top, `tee` didn't work right and my scrollback buffer wasn't big enough. I think I got the important stuff though). there seems to be a lot of "*/*.hi is missing (ignoring)" messages, culminating in: Configuring hsc2hs-0.67... make[1]: *** No rule to make target `libraries/process/ghc.mk'. Stop. make: *** [all] Error 2 Any hints? Cheers, - Tim.

2 2

ghc trac not sending verification emails?
by Tim Cuthbertson 29 May '12

29 May '12

I signed up for an account on http://hackage.haskell.org/trac/ghc/ to report a couple of bugs, but can't file them until my email address is verified. I've tried two different email addresses, waited more than 24 hours, and checked my spam folder but sill don't see anything. Is email sending busted? I know that the cabal trac is migrating to github, does that affect GHC's trac as well? Cheers, - Tim.

2 2

relocatable packages: GHC_PACKAGE_PATH and package.conf
by Tim Cuthbertson 29 May '12

29 May '12

Hi all, I'm trying to build a relocatable package using cabal, and running into some difficulties. I've created / used the following script to attempt to create a relocatable package: https://github.com/gfxmonk/0compile-cabal-build/blob/2cf4a08b146333d9292f6f… When this is done I have something that looks like it should work, and has an inline package.conf. But when I run the following: ----------------------------------------------- $ export GHC_PACKAGE_PATH="/home/tim/dev/haskell/third-party/haskell-ansi-terminal/haskell-ansi-terminal-linux-x86_64/package.conf:" $ ghc-pkg check There are problems in package ansi-terminal-0.5.5: import-dirs: ${pkgroot}/lib is a relative path library-dirs: ${pkgroot}/lib is a relative path file System/Console/ANSI.hi is missing file System/Console/ANSI/Unix.hi is missing file System/Console/ANSI/Common.hi is missing cannot find libHSansi-terminal-0.5.5.a on library path The following packages are broken, either because they have a problem listed above, or because they depend on a broken package. ansi-terminal-0.5.5 ----------------------------------------------- So it looks like: - I need to set more environment variabes so that ghc can find the parts of the package (e.g libHSansi-terminal-0.5.5.a). Unfortunately, I don't know what "library path" refers to in the above message (I tried $LD_LIBRARY_PATH and $LIB_PATH to no avail). - ghc doesn't seem to support ${pkgroot} prefixes. I thought it did, but I'm new to this so I may be misunderstanding where they can be used. Can anyone suggest what I might need to fix (either in the package.conf or in my environment variables) to get this working? I've uploaded my package.conf here, apologies for the lack of formatting: https://gist.github.com/59a0d3e69751c3932579 Additionally, the paths that come out of cabal build have the compiler name and version hard coded, e.g lib/packagename/ghc-7.0.4/*. Is there any way to configure how this path is constructed to get rid of the ghd-7.0.4 part? If I need to add $DISTDIR/ansi-terminal-0.5.5/ghc-7.0.4/ to a library path, it would be much easier to declare that if it didn't depend on the version of GHC used. Assume that since I'm building a standalone package, there is no problem with collisions (packages for other versions of GHC or other compilers would have a different $PREFIX). I'd really like to get relocatable packages working, so any help or guidance would be appreciated. Cheers, - Tim.

2 2

Strange behavior in GHC-compiled code
by Mark Conway Wirt 27 May '12

27 May '12

Hi folks. I have a piece of Haskell code that's been laying around on my computer for about a year, and I recently decided to dust it off. The problem is that it used to work fine, but in the interim (in which I both upgraded OS versions/GHC versions and went from 32 bit to 64 bit) the code stopped working reliably. It tends to work OK for small data sets, but with larger data sets it exhibits one of three bad behaviors: 1) A segfault, 2) An "Error in array index" error, or 3) The following runtime error: internal error: evacuate: strange closure type 5060208 (GHC version 7.0.3 for x86_64_unknown_linux) Please report this as a GHC bug: http://www.haskell.org/ghc/reportabug Aborted It complies OK, although with optimization turned on it gives me a "has one call pattern, but the limit is 0" error, but my understanding is that this shouldn't really be an issue. I'd like to figure out what this issue is, but while I understand a bit about the language itself, with my knowledge of GHC and the way it works I don't really know where to begin. (The strange non-deterministic nature of the problem makes me wonder if it could be something not related to Haskell, such as a hardware or memory error. Is this possible or likely?) Any guidance/pointers would be very much appreciated. Thanks. -Mark

3 4

Potential GSoC proposal: Reduce the speed gap between 'ghc -c' and 'ghc --make'
by Mikhail Glushenkov 24 May '12

24 May '12

Hi all, [Hoping it's not too late.] During my work on parallelising 'ghc --make' [1] I encountered a stumbling block: running 'ghc --make' can be often much faster than using separate compile ('ghc -c') and link stages, which means that any parallel build tool built on top of 'ghc -c' will be significantly handicapped [2]. As far as I understand, this is mainly due to the effects of interface file caching - 'ghc --make' only needs to parse and load them once. One potential improvement (suggested by Duncan Coutts [3]) is to produce whole-package interface files and load them in using mmap(). Questions: Would implementing this optimisation be a worthwhile/realistic GSoC project? What are other potential ways to bring 'ghc -c' performance up to par with 'ghc --make'? [1] https://github.com/23Skidoo/ghc-parmake [2] https://gist.github.com/1360470 [3] http://www.reddit.com/r/haskell/comments/qwj5j/the_cabal_of_my_dreams/c41a5… -- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments

5 14