-
Notifications
You must be signed in to change notification settings - Fork 841
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
Problem with stack upgrade #1477
Comments
hmm I don't think there is support for that but I always build my stack unpack stack-0.1.10.0
cd stack-0.1.10.0
stack install --flag cryptonite:-support_aesni you wouldn't have to use package version to have it always download latest (ala stack upgrade) but currenlty stack would pick up deprecated versions #1391 |
It wouldn't be too strange to add the I'm thinking that for this (hopefully) rare case, @luigy's solution is sufficient. So, closing as wontfix. |
Yeah, this is a rare case. I've been building from source this whole time so it's not a showstopper that |
For reference, in case anyone needs a bootstrapped |
I am using an ancient Mac OS X laptop where the Stack dependency
cryptonite
requires me to pass a custom flag to Cabal haskell-crypto/cryptonite#21 but I don't know how to pass this flag tostack upgrade
. (Note that this laptop is sufficiently old that I cannot just download and use the prebuilt binary for Stack for more modern OS X, but have to build Stack from source.) Without the flag, I cannot dostack upgrade
.How do I hook in the config into
stack upgrade
?The text was updated successfully, but these errors were encountered: