Re: Segfault when using integer-simple
On 2013-06-16 22:33, Stephen Paul Weber wrote: Somebody claiming to be Carter Schonwald wrote: Could you open a ticket on trac for this issue? Also have you tried to reproduce it on other architectures? Done: http://hackage.haskell.org/trac/ghc/ticket/7988 I have just now tested on native linux-i486, but nothing else yet. I tried to build a cross-compiler for arm-linux just now and it complained that I don't have curses for terminfo :P If anyone with an Android or other cross-compiler could test it out, that would be awesome too, but I will keep poking. I don’t use integer-simple in my Android cross-compiler builds because I ran into problems. Possibly the same problem as you. I never did investigate any further though because it seemed like integer-gmp was the way to go for acceptable performance anyway and the switch was not difficult. -- CJ van den Berg mailto:c...@vdbonline.com xmpp:neuroc...@gmail.com ___ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs
Re: how to checkout proper submodules
Hi, We misunderstood that the new IO manager was not working properly. This is our fault. We confirmed that it is working well. Sorry for bothering you, guys. Anyway, I believe we need a way to check out proper submodules as many others said. --Kazu Hi, Andreas and I found that the new IO manager is not working properly in the current GHC head. I'm sure that it worked well at least on May 7. We need to narrow the range of commits, so I did: % git checkout bb2795db36b36966697c228315ae20767c4a8753 % git submodule update But this does not checkout proper submodules. For instance, libraries/base has newer commits. And of cource, building fails. Please tell us how to checkout proper submodules against a specific GHC tree. --Kazu ___ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs
RE: How to build statically linking GHC?
Interesting. Why super-annoying? Simon | -Original Message- | From: ghc-devs-boun...@haskell.org [mailto:ghc-devs-boun...@haskell.org] | On Behalf Of Stephen Paul Weber | Sent: 16 June 2013 21:05 | To: ghc-devs@haskell.org | Subject: How to build statically linking GHC? | | What's the correct way, on GHC head, to get it to build libraries in the | way | GHC does now (so that they are statically linked into binaries) instead | of | the new-but-super-annoying dynamic linking? Do I just | DYNAMIC_BY_DEFAULT=NO | in my build.mk? | | -- | Stephen Paul Weber, @singpolyma | See http://singpolyma.net for how I prefer to be contacted | edition right joseph | | ___ | ghc-devs mailing list | ghc-devs@haskell.org | http://www.haskell.org/mailman/listinfo/ghc-devs ___ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs
shared libraries for profiling
Hi, I seems to me that shared libraries for profiling are not installed. For example, let's see the base library: % cd lib/ghc-7.7.20130616/base-4.7.0.0 % ls -1 libHSbase* libHSbase-4.7.0.0.a libHSbase-4.7.0.0-ghc7.7.20130616.so* libHSbase-4.7.0.0_p.a A static library for profiling is installed, but there is not a corresponding dynamic library. I'm suffering from this because I cannot take profiling for my program with GHC head. Is this a bug? --Kazu ___ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs
Re: Segfault when using integer-simple
Somebody claiming to be CJ van den Berg wrote: I don’t use integer-simple in my Android cross-compiler builds because I ran into problems. Possibly the same problem as you. I never did investigate any further though because it seemed like integer-gmp was the way to go for acceptable performance anyway and the switch was not difficult. Did you have to seperately cross-compile libgmp first, or does android have it by default? -- Stephen Paul Weber, @singpolyma See http://singpolyma.net for how I prefer to be contacted edition right joseph ___ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs
Windows failures
Ian This is 'sh validate on 64bit Windows. Rather a lot of failures. Might you look? The perf tests seem to fail because it's comparing with the *32* bit numbers, even though this is definitely a *64* bit laptop. Whether the entire build system thinks it's a 32 bit machine, or just the testsuite, I can't tell. Thanks Simon Unexpected failures: cabal/cabal01cabal01 [bad exit code] (normal) cabal/cabal04cabal04 [bad exit code] (normal) driver dynHelloWorld [exit code non-0] (dyn) driver/dynamicToodynamicToo002 [bad stdout] (normal) driver/dynamicToodynamicToo003 [bad exit code] (normal) dynlibs T4464 [bad exit code] (normal) dynlibs T5373 [bad exit code] (normal) ghc-api/T7478T7478 [bad exit code] (normal) ghci.debugger/scriptsbreak008 [bad exit code] (ghci) ghci.debugger/scriptsdynbrk009 [bad exit code] (ghci) ghci/scripts T5975a [bad stderr] (ghci) llvm/should_compile T5486 [exit code non-0] (optllvm) llvm/should_compile T5681 [exit code non-0] (optllvm) llvm/should_compile T6158 [exit code non-0] (optllvm) llvm/should_compile T7571 [exit code non-0] (optllvm) llvm/should_compile T7575 [exit code non-0] (optllvm) perf/compilerT1969 [stat not good enough] (normal) perf/compilerT3294 [stat not good enough] (normal) perf/compilerT4801 [stat too good] (normal) perf/haddock haddock.Cabal [stat not good enough] (normal) perf/haddock haddock.base [stat not good enough] (normal) perf/haddock haddock.compiler [stat not good enough] (normal) perf/should_run T7797 [stat too good] (normal) rts T4850 [bad stdout] (normal) rts derefnull [bad exit code] (normal) rts divbyzero [bad exit code] (normal) runghc T7859 [bad stderr] (normal) safeHaskell/check/pkg01 ImpSafeOnly01 [exit code non-0] (normal) safeHaskell/check/pkg01 ImpSafeOnly02 [exit code non-0] (normal) safeHaskell/check/pkg01 ImpSafeOnly03 [stderr mismatch] (normal) safeHaskell/check/pkg01 ImpSafeOnly04 [exit code non-0] (normal) safeHaskell/check/pkg01 ImpSafeOnly05 [stderr mismatch] (normal) safeHaskell/check/pkg01 ImpSafeOnly06 [exit code non-0] (normal) safeHaskell/check/pkg01 ImpSafeOnly07 [stderr mismatch] (normal) safeHaskell/check/pkg01 ImpSafeOnly08 [stderr mismatch] (normal) safeHaskell/check/pkg01 ImpSafeOnly09 [stderr mismatch] (normal) safeHaskell/check/pkg01 ImpSafeOnly10 [exit code non-0] (normal) safeHaskell/check/pkg01 safePkg01 [bad exit code] (normal) ___ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs
