Steve Smith

> Is there an alternate approach by simply ripping out the version requirements in [cabal-bootstrap-gen.cabal](https://github.com/haskell/cabal/blob/master/bootstrap/cabal-bootstrap-gen.cabal)? Any suggestion on which requirements to relax, or simply remove all of them? That apparently...

> linux-9.2.1.json > BTW, I think there is a linux-9.2.1.json somewhere in the repo history, half a year ago perhaps. Thanks, but no such luck: ```bash git log --all --full-history...

I've updated to `ghc-9.4.1`. All approaches discussed to bootstrap `cabal` appear to fail: Using [linux-9.2.3.json](https://github.com/haskell/cabal/blob/master/bootstrap/linux-9.2.3.json): ```bash :debug:build system -W /opt/local/var/macports/build/_opt_local_ports_lang_cabal /cabal/work/cabal-install-3.8.1.0: ./bootstrap/bootstrap.py -d ./bootstrap/darwi n-9.4.1.json -w /opt/local/bin/ghc :info:build ghc-pkg-9.4.1: cannot...

> BTW, I forgot the backlog, but don't you have any old `cabal` binary lying around? Is it the first time you bootstrap for that architecture? That should really be...

> And the binary works for you? Forgive my clueless questions, I'm trying to understand the "what for" to be able to help with "how". I’m the maintainer of the...

I’m simply following the bootstrap instructions provided in this repo. If there are other methods that work that would be great. Would you please post `cabal` bootstrap instructions? > Thank...

Here's the error message for `cabal install cabal-install`: ```bash sudo -u macports bash -c 'export CABAL_CONFIG=/opt/local/var/macports/build/_opt_local_ports_lang_cabal/cabal/work/.home/.cabal/config ; \ cd /opt/local/var/macports/build/_opt_local_ports_lang_cabal/cabal/work/cabal-install-3.8.1.0/ ; \ /opt/local/var/macports/build/_opt_local_ports_lang_cabal/cabal/work/bin/cabal update ; \ /opt/local/var/macports/build/_opt_local_ports_lang_cabal/cabal/work/bin/cabal install cabal-install' Downloading...

> It always worked only for a selection of GHC version. I hope the selection we have now works. Is it advisable to use `stack` to get reliable builds of...

Thanks for the advice. I’ll refactor to use `stack`.

> Out of curiosity, is your stack package bootstrapped from ghc alone? I've set things up so that each Haskell thing bootstraps itself: `stack` bootstraps `stack`, and so forth. Thinking...