Matthew Pickering comments

Results 272 comments of


                                            Matthew Pickering

Something seems wrong with ghcup installing bindist for i386 on debian 12

GHC issue: https://gitlab.haskell.org/ghc/ghc/-/issues/25095

Disable GHCs aggressive selection of `ld.gold`

It seems that 2a7f32ec8caf638a9c14c6ba223e2a489db9620c reverts the change to use `--disable-ld-override` "for now". Is the plan to enable `--disable-ld-override` in future, is there an issue which is block it being used...

Disable GHCs aggressive selection of `ld.gold`

Thanks sounds good, just wanted to check in about what the status was there.

How to delete a pin?

I am not the owner of the cachix, so I can't see the `delete` button (I was sent an auth token by the owner so I can use the CLI...

docs: Explain how to build only .dyn_o.

Indeed, the default is to build vanilla libraries, and if you have a dynamically linked compiler that implies dynamic libraries as well.

cabal-install seems to pass new implicit flags to the compiler by default, which breaks doctest.

It seems that `doctest` is being invoked with the `--interactive` flag, so at a glance, seems everything is working on the cabal side there and it's `doctest` which has potentially...

cabal-install seems to pass new implicit flags to the compiler by default, which breaks doctest.

The way that `cabal` starts the repl is by invoking `ghc`, or the command you say is `ghc` with the `--interactive` flag. For example: ``` cabal repl -w/path/to/ghc ... /path/to/ghc...

cabal-install seems to pass new implicit flags to the compiler by default, which breaks doctest.

In that command you are using `doctest-9.10.1` rather than `doctest`, are those the same thing? Yes, it has always worked like this.

cabal-install seems to pass new implicit flags to the compiler by default, which breaks doctest.

Ah thanks, @andreabedini for the investigation. Yes this is due to a change I made recently. (https://github.com/haskell/cabal/pull/10828) It seems that ``` ghc -package-env=- --interactive ``` works as expected, so the...

cabal-install seems to pass new implicit flags to the compiler by default, which breaks doctest.

Ah, I think the problem may actually in this bit of logic in the `Cabal` library ``` 658 runGHCWithResponseFile fileNameTemplate encoding tempFileOptions verbosity ghcProg comp platform maybeWorkDir opts = do...