Summary: | app-misc/zellij-0.40.1 fails to compile: error: couldnt read compact-bar.wasm: No such file or directory (os error 2) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Agostino Sarubbo <ago> |
Component: | Current packages | Assignee: | Patrick McLean <chutzpah> |
Status: | CONFIRMED --- | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | build.log |
Description
Agostino Sarubbo
![]() Created attachment 857545 [details]
build.log
build log and emerge --info
Error(s) that match a know pattern in addition to what has been reported in the summary: error: couldn't read /var/tmp/portage/app-misc/zellij-0.35.2/work/zellij-0.35.2/zellij-utils/../target/wasm32-wasi/debug/compact-bar.wasm: No such file or directory (os error 2) error: couldn't read /var/tmp/portage/app-misc/zellij-0.35.2/work/zellij-0.35.2/zellij-utils/../target/wasm32-wasi/debug/status-bar.wasm: No such file or directory (os error 2) error: couldn't read /var/tmp/portage/app-misc/zellij-0.35.2/work/zellij-0.35.2/zellij-utils/../target/wasm32-wasi/debug/strider.wasm: No such file or directory (os error 2) error: couldn't read /var/tmp/portage/app-misc/zellij-0.35.2/work/zellij-0.35.2/zellij-utils/../target/wasm32-wasi/debug/tab-bar.wasm: No such file or directory (os error 2) error: couldn't read /var/tmp/portage/app-misc/zellij-0.35.2/work/zellij-0.35.2/zellij-utils/../target/wasm32-wasi/debug/compact-bar.wasm: No such file or directory (os error 2) ci has reproduced this issue with version 0.36.0 - Updating summary. ci has reproduced this issue with version 0.37.2 - Updating summary. ci has reproduced this issue with version 0.38.1 - Updating summary. ci has reproduced this issue with version 0.38.2 - Updating summary. tinderbox_musl has reproduced this issue with version 0.39.1 - Updating summary. glibc-2.39_tinderbox has reproduced this issue with version 0.39.2 - Updating summary. ci has reproduced this issue with version 0.40.1 - Updating summary. |