bug#51928: GHC 8.10 occupies 1.6 GiB

Hi, > still current. I’m not so sure about that. We link (most/all?) Haskell binaries (pandoc for example) statically, so none of them should pull in GHC any more. If they do, that’s a bug. It’s almost impossible to untangle GHC libraries (and also GHC itself), since there are circular reference

bug#51213: ghci missing reference to gcc

Hi Simon, Thanks for caring for this old issue. On Fri, 22 Sep 2023, Simon Tournier wrote: Hi, On Thu, 14 Oct 2021 at 16:00, Jack Hill wrote: $ guix environment --ad-hoc ghc -- ghci GHCi, version 8.10.7: https://www.haskell.org/ghc/ :? for help ghc: could not execute: gcc This is curren

bug#47543: “Repeated allocation of very large block” during ‘guix pull’

Ludovic Courtès writes: > If you experience it, please share the command line and command output! Never seen this before, but here it is... --8<---cut here---start->8--- 18:55:29 janneke@dundal:~/src/guix/master $ guix pull --commit=6bd17a0806 Updating channe

bug#34850: ghc compiling error

Re, On Fri, 22 Sep 2023 at 18:09, Simon Tournier wrote: > Can we close this bug report? I get back: --8<---cut here---start->8--- Address not found Your message wasn't delivered to mikadoz...@yandex.com because the address couldn't be found or is unable to

bug#51928: GHC 8.10 occupies 1.6 GiB

Hi, Old bug#51928: https://issues.guix.gnu.org/issue/51928 still current. On Wed, 17 Nov 2021 at 22:15, Ludovic Courtès wrote: > $ guix describe > Generacio 194 Nov 07 2021 23:40:30(nuna) > guix bd41e59 > repository URL: https://git.savannah.gnu.org/git/guix.git > branch: ma

bug#55178: ghc cannot find libraries of ghc-comonad

Hi Christoph, On Sat, 21 Jan 2023 at 13:49, Lars-Dominik Braun wrote: >> guix shell --pure ghc ghc-comonad gcc-toolchain -- ghc LinkMe.hs >> [1 of 1] Compiling Main ( LinkMe.hs, LinkMe.o ) >> Linking LinkMe ... >> ld: cannot find -lHScomonad-5.0.8-KDPzf2kORSz9Qeif8nQH6d >> ld: cannot

bug#51213: ghci missing reference to gcc

Hi, On Thu, 14 Oct 2021 at 16:00, Jack Hill wrote: > $ guix environment --ad-hoc ghc -- ghci > GHCi, version 8.10.7: https://www.haskell.org/ghc/ :? for help > ghc: could not execute: gcc This is currently expected. > but if gcc-toolchain is included, it can: One option is to have a package

bug#42480: cabal-install/GHC fails to find libraries

Hi I think this old bug#42480, https://issues.guix.gnu.org/issue/42480 can be closed. On Wed, 22 Jul 2020 at 16:43, John Soo wrote: > I do have gcc-toolchain installed and I just realized that my project > compiles fine if I do not try to statically link. I believe this can be > closed a

bug#34850: ghc compiling error

Hi, It is about this old bug #34850 [1]. 1: https://issues.guix.gnu.org/issue/34850 On Wed, 13 Mar 2019 at 21:27, mikadoZero wrote: >>> `guix describe` >>> guix fd4c7a0 >>> repository URL: https://git.savannah.gnu.org/git/guix.git >>> branch: master >>> commit: fd4c7a098a508c1

bug#32131: ghc fails to compile packages when installed into profile

Hi, This old bug #32131, https://issues.guix.gnu.org/issue/32131 is not a bug. It is because gcc-toolchain is missing. On Wed, 11 Jul 2018 at 22:12, Anonymous wrote: > This bug can be reproduced by doing > >     guix package -i ghc >     echo 'main=return()' > test.hs >     ghc test.hs >

bug#66059: [cuirass] [feature] Mention which builder machine was used

Hi Maxim, Maxim Cournoyer skribis: > When investigating a build failure, it can be useful to see the logs of > the machine that built the package (to determine whether it ran out of > memory, say), but currently the build logs or even the derivation page > on Cuirass doesn't track such informati