Open ProofOfKeags opened 4 years ago
@CaptJakk Is it possible that your system's GHC doesn't match the resolver's one?
I just stumbled upon this issue and it's working for me on (on ubuntu 19.10 arm64) with ghc 8.6.5
and resolver 14.16
I just issued stack install --system-ghc
and my project started building
have you tried on ARM? this ONLY happens if it can't find the installation keys for the arch-os combo. I ran into this when doing some work on Arch on a RPi 4.
I have experienced this issue on 64bit Ubuntu Server installed on Raspberry Pi 4 and on 32bit Raspbian on Raspberry Pi 4. Stack seems broken on the Pi.
We are having a lot of success running it on Raspbian Buster Lite, in general. Arch on the Pi doesn't seem to work with stack though, even though GHC binaries for 8.6.1 are available, which is why we said "use system ghc", but it still was hung up on not being able to find installation keys
General summary/comments (optional)
I am trying to build a project on Arch Linux on ARMv7 (Raspberry Pi 4), and it cannot find the OS Key for
linux-armv7-tinfo6
. This is expected behavior. However, I managed to install ghc 8.6.1 via pacman. I figured I would be able to use this resolver with the flagsystem-ghc: true
to at least get a build started if not fully finished. This is not the case.Steps to reproduce
The full steps are not needed to understand the gist of this issue (I think). But for completeness:
pacman -S stack
stack upgrade
pacman -S ghc
resolver: nightly-2018-09-29
system-ghc: true
Expected
The build should start with the system-ghc
Actual
Stack version
Method of installation
stack upgrade . pacman -S stack