-
Notifications
You must be signed in to change notification settings - Fork 843
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
stack update gives "fdLock: invalid argument (Invalid argument)" #5589
Comments
And I guess that's why stack on this machine is an "unsupported version":
I think this started with 2.7.x. |
@simonmichael how did you even manage to get a 32bit stack? |
Built it on that machine with an existing stack executable, I think. |
@simonmichael well, there are no 32bit release binaries, so I'm not surprised it doesn't work. You could try |
Fantastic, thanks! Your suggestion to add
I guess on this system it was auto-selecting the 32 bit binary, which worked less well. Perhaps there's room for improvement in that choice ? If not, this can be closed. |
- Pinned ghcup to version 0.1.17.8 since by default it auto-updates and 0.1.18.0 is broken on ARM: https://gitlab.haskell.org/haskell/ghcup-hs/-/issues/405 - Investigated complex "fdlock: invalid argument" bug (commercialhaskell/stack#5589) but couldn't reliably eliminate it. Updating to stack 2.9.1 may help, but seems to be okay now with the original 2.7.5 so leaving it be. - Made reason for ENV commands for ghcup more explicit for future maintainers. - Split prerequisite installs from ghcup installs for better caching and easier maintenance. - Renamed ARGs for more self-documentation, and moved them closer to where they're used since they're applied at each RUN and therefore affect caching. - Removed redundant `--copy-bins` flag. - Removed stack.yaml.lock because it's not used and at the moment does not provide any useful locking. - Changed "Cabal-version" requirement to >=1.8 from >1.2 to remove warning about unsupported version range syntax feature, since we have no reason to support the very outdated <1.8. Change-type: patch Signed-off-by: Heath Raftery (@hraftery) <[email protected]>
On a VPS I notice current stack giving this error for update and other commands (build, install). Even wiping ~/.stack didn't help:
Is it just me ? This machine is unusual, after upgrades it is a mixture of 32 bit libs/64 bit kernel, or vice versa.
Possibly related discussion at:
haskell/cabal#6602
haskellari/lukko#15
haskell/cabal#7442
haskell/cabal#7313
Indeed, it seems like it might be 32-bit related.
The text was updated successfully, but these errors were encountered: