Balderdash Compile Error
Categories
(Firefox Build System :: General, defect, P3)
Tracking
(Not tracked)
People
(Reporter: jason.kaiser, Unassigned)
Details
(Keywords: in-triage)
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.163 Safari/537.36
Steps to reproduce:
Xubuntu 19.10 kernel 5.5.15
hg pull -u
./mach build
Actual results:
2:48.82 Compiling baldrdash v0.1.0 (/home/localhost/src/mzb/ffbld/js/src/wasm/cranelift)
2:49.18 error[E0599]: no variant or associated item named OptRef found for enum bindings::low_level::TypeCode in the current scope
2:49.18 --> js/src/wasm/cranelift/src/bindings/mod.rs:112:27
2:49.18 |
2:49.19 112 | TypeCode::OptRef | TypeCode::AnyRef | TypeCode::FuncRef | TypeCode::NullRef => {
2:49.19 | ^^^^^^ variant or associated item not found in bindings::low_level::TypeCode
2:49.19 |
2:49.19 ::: /home/localhost/src/mzb/ffbld/obj-x86_64-pc-linux-gnu/x86_64-unknown-linux-gnu/release/build/baldrdash-0a60df3f71f34c02/out/bindings.rs:9:1
2:49.19 |
2:49.19 9 | pub enum TypeCode {
2:49.19 | ----------------- variant or associated item OptRef not found here
2:49.22 error: aborting due to previous error
2:49.22 For more information about this error, try rustc --explain E0599.
2:49.24 error: could not compile baldrdash.
2:49.24 warning: build failed, waiting for other jobs to finish...
2:52.18 error: build failed
2:52.20 make[4]: *** [/home/localhost/src/mzb/ffbld/config/makefiles/rust.mk:294: force-cargo-library-build] Error 101
2:52.20 make[3]: *** [/home/localhost/src/mzb/ffbld/config/recurse.mk:74: toolkit/library/rust/target] Error 2
2:52.20 make[3]: *** Waiting for unfinished jobs....
2:55.58 /home/localhost/src/mzb/ffbld/intl/icu/source/common/localeprioritylist.cpp:143:25: warning: possible misuse of comma operator here [-Wcomma]
Expected results:
successful co
|
||
Updated•6 years ago
|
|
||
Comment 1•6 years ago
|
||
Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is P3 (Backlog,) indicating it has been triaged, the bug's Severity is being updated to S3 (normal.)
Description
•