Matthew Pickering
Matthew Pickering
I can't reproduce this on NixOS. To reproduce I entered the `shell.nix` using `nix-shell shell.nix` after setting up the [binary cache](https://input-output-hk.github.io/haskell.nix/tutorials/getting-started.html#setting-up-the-binary-cache). Then ` cabal build -O1 -w $(which ghc-9.8.2) --semaphore...
Results from the repo that @jasagredo tried the flag on: ``` Benchmark 1: cabal build -w /nix/store/kyh03hm4ni2d5rhydlsgcv88c1vdlylg-ghc-9.8.2/bin/ghc-9.8.2 -O1 -j all Time (mean ± σ): 186.922 s ± 5.796 s [User:...
@jasagredo Does this happen when building other projects as well? If I can reproduce in a docker container that would be good.
@wz1000 investigated this issue and the problem appears to be that the binaries are built and linked against musl but used on a system which uses glibc. * `cabal-install` is...
If GHC had a command line mode to create the semaphore and managed them itself then this coupling wouldn't exist. I can't think of any other options immediately.
Similar to #2910
Perhaps a good first step in this issue is to give a warning to the user if they only specify selectors which resolve to non-benchmark components? Perhaps there should be...
This failure is currently manifested in the way that if you write `--disable-shared` then `--enable-shared` is still passed to `./Setup`. If you pass both `--disable-shared` and `--disable-executable-dynamic` then you don't...
Now fixed.
No, it's still broken inheriting that variable.