Build error with wasm32-wasi: system `wasi' not recognized #271

Activity

1. Bodigrim commented on Jan 30, 2023

   

   Bodigrim

   on Jan 30, 2023

   Contributor

   More actions

   Does the CI configuration we use shed any light? Can you run it in your environment?
   

   unix/.github/workflows/ci-wasm32-wasi.yml

   Lines 12 to 29 in 98adc73

   	- name: setup-ghc-wasm32-wasi
   	run: |
   	pushd $(mktemp -d)
   	curl -L https://gitlab.haskell.org/ghc/ghc-wasm-meta/-/archive/master/ghc-wasm-meta-master.tar.gz | tar xz --strip-components=1
   	./setup.sh
   	~/.ghc-wasm/add_to_github_path.sh
   	popd
   	- uses: actions/checkout@v3
   	- name: test
   	run: |
   	cp ~/.ghc-wasm/wasi-sdk/share/misc/config.* .
   	autoreconf -i
   	wasm32-wasi-cabal --project-file=cabal.project.wasm32-wasi build
   	./test-wasm32-wasi.mjs

   CC @TerrorJack
2. brandonchinn178 commented on Jan 30, 2023

   

   brandonchinn178

   on Jan 30, 2023

   Author

   More actions

   I saw that, but I don't think it does. Because I'm on aarch64, I can't use setup.sh, but I followed the manual instructions in ghc-wasm-meta to create the Dockerfile; I linked it above, feel free to audit.

   I get the error whether or not I source ~/.ghc-wasm/env, which is the only thing I can think of.

   I didn't do these steps though:
   

   unix/.github/workflows/ci-wasm32-wasi.yml

   Lines 24 to 25 in 98adc73

   	cp ~/.ghc-wasm/wasi-sdk/share/misc/config.* .
   	autoreconf -i

   I'm not sure how I would do it manually, since I'm not configuring unix myself; Cabal should be doing that
3. Bodigrim commented on Jan 30, 2023

   

   Bodigrim

   on Jan 30, 2023

   Contributor

   More actions

   Could you try and build unix alone from the source code, same as our CI does? That might be a helpful data point, proving that your setup is correct and that unix itself has not been broken by recent changes.

   Another question is why your build is reinstalling unix at all? It's a boot package and it should come preinstalled with GHC. Could you be more precise with allow-newer?
4. brandonchinn178 commented on Jan 30, 2023

   

   brandonchinn178

   on Jan 30, 2023

   Author

   More actions

   I tried, but wasm32-wasi-cabal install --lib unix exits immediately with "Up to date", which is probably what you're alluding to in the second point.

   I was also curious about that. Maybe I need to point to some package db? Let me investigate more when I'm back at my computer
5. Bodigrim commented on Jan 30, 2023

   

   Bodigrim

   on Jan 30, 2023

   Contributor

   More actions

   Try wasm32-wasi-cabal install ormolu -w ghc-9.6 --dry-run --allow-newer='template-haskell' --allow-newer=base --allow-newer=ghc-prim --allow-newer=unix --constraint 'unix installed' --allow-newer='ghc-lib-parser:transformers' or similar. The key point is to pass --constraint 'unix installed'.
6. bgamari commented on Jan 30, 2023

   

   bgamari

   on Jan 30, 2023

   Contributor

   More actions

   checking host system type... Invalid configuration `wasm32-wasi': system `wasi' not recognized
   

   I am nearly certain that this is an autoconf error; specifically the configure script does not recognize the host system triple. I would guess that this is because the configure script currently in the tree is too old to have wasi support.=

   I didn't do these steps though: ...

   My guess is that one of these two steps will fix your issue. @TerrorJack, I'm a bit unclear on why these manual steps are necessary; can't we simply update to autoconf 2.70, which should already have wasi support?
7. hasufell commented on Jan 30, 2023

   

   hasufell

   on Jan 30, 2023

   Member

   More actions

   can't we simply update to autoconf 2.70, which should already have wasi support?

   Note that there were several issues with autoconf 2.70 in the network package. Although they seem to be mostly windows related, I'd be careful with bumping either way: haskell/network#508
8. brandonchinn178 commented on Jan 30, 2023

   

   brandonchinn178

   on Jan 30, 2023

   Author

   More actions

   I think I got it working with both --allow-newer='ghc-lib-parser:transformers' and --constraints='unix installed'. Why isn't the solver using unix installed by default? I would expect that if CMD --constraints='PKG installed' works, CMD by itself would use PKG installed.
9. TerrorJack commented on Jan 30, 2023

   

   TerrorJack

   on Jan 30, 2023

   Contributor

   More actions

   I do believe we need to bump the autoconf scripts in this repo. Or land a wasi-specific patch, but that's much less ideal..
10. bgamari commented on Jan 30, 2023

    

    bgamari

    on Jan 30, 2023

    Last edited by bgamari

    Contributor

    More actions

    I think I got it working with both --allow-newer='ghc-lib-parser:transformers' and --constraints='unix installed'. Why isn't the solver using unix installed by default?

    @brandonchinn178, my understanding is that the solver should use the pre-existing package by default if the plan's constraints will allow it. I would try looking at cabal-install's -v3 output to see why the pre-existing package is ruled out
11. brandonchinn178 commented on Jan 30, 2023

    

    brandonchinn178

    on Jan 30, 2023

    Author

    More actions

    Ok got it working with

    --allow-newer=Cabal-syntax
    --constraint='transformers installed'
    --allow-newer=ghc-lib-parser:transformers
    

    Firstly, Cabal-syntax currently pins unix < 2.8 on Hackage, so --allow-newer=Cabal-syntax is needed to allow using the installed unix-2.8.0.0.

    Secondly, we need to explicitly constraint transformers installed because apparently GHC is using transformers-0.6.0.4 as a boot library, but 0.6.0.4 is a deprecated version, so Cabal doesn't include it in the constraint solver.

    Lastly, ghc-lib-parser currently has transformers < 0.6, so --allow-newer=ghc-lib-parser:transformers is necessary

    ---

    But it also sounds like there's an issue with the autoconf script in this repo, so I'll leave this issue open. Feel free to close when appropriate