plutus-starter cabal build failed to build playground-common-0.1.0.0

trafficstars

I use the devcontainer 1.0.14 to build the plutus starter.

Here are my commands to create the container and to do the cabal build :

docker run -u root --name plutusdev -ti inputoutput/plutus-starter-devcontainer:v1.0.14

...
mkdir /root
touch /root/.gitconfig
git config --global http.proxy http://my-company-proxy:8080
git config --global https.proxy http://my-company-proxy:8080
cd /root
git clone https://github.com/input-output-hk/plutus-starter.git
mv /home/plutus/.cabal /root
mv /home/plutus/.bashrc /root
bash
export http_proxy=http://my-company-proxy:8080/
export https_proxy=http://my-company-proxy:8080/
cd plutus-starter
cabal update
cabal build

The build fails when building the playground-common-0.1.0.0 : plutusdev-error.txt

Next I tried with the devcontainer 1.0.15 and the build fails when linking happy : plutusdev1.0.15-error.txt

Apr 13 '22 13:04 bcoste

I'm having this issue with playground-common-0.1.0.0 too

I'm trying to build using a VS Code docker devcontainer, so it's using the provided nix environment. Screen Shot 2022-04-25 at 12 57 48 PM

Apr 25 '22 05:04 maguldemond

I'm also getting the same issue:

with v1.0.14 image:

src/Auth.hs:130:41: error:
    Not in scope: type constructor or class ‘JWT.EncodeSigner’
    Module ‘Web.JWT’ does not export ‘EncodeSigner’.
    |
130 |         { _configJWTSignature       :: !JWT.EncodeSigner
    |                                         ^^^^^^^^^^^^^^^^

with v1.0.15 image:

Linking dist/build/alex/alex ...
/nix/store/hy3lz2vfv9qq2v5jz9nzlx6mmiaq79rj-binutils-2.35.1/bin/ld: cannot find -lnuma
collect2: error: ld returned 1 exit status
`cc' failed in phase `Linker'. (Exit code: 1)
cabal: Failed to build exe:alex from alex-3.2.7.1 (which is required by
test:plutus-example-projects-test from plutus-starter-0.1.0.0 and
exe:plutus-starter-pab from plutus-starter-0.1.0.0). See the build log above
for details.

Update: Using the 2nd method (Cabal+Nix build) I can get cabal build ran successfully on my machine, so you might want to try that instead