I'm trying to do a first build of Thunderbird on MacOS Mojave. Have followed 
all available advice for establishing prerequisites. But "mach build" fails 
thus:

 6:16.42 js/src/frontend
 6:26.48 js/src/gc
 6:57.67    Compiling serde_json v1.0.26
 7:03.34    Compiling baldrdash v0.1.0 
(/Users/greg/moz-source/js/src/wasm/cranelift)
 7:05.55    Compiling failure v0.1.3
 7:05.85    Compiling target-lexicon v0.2.0
 7:09.31 error: failed to run custom build command for `baldrdash v0.1.0 
(/Users/greg/moz-source/js/src/wasm/cranelift)`
 7:09.31 process didn't exit successfully: 
`/Users/greg/moz-source/obj-x86_64-apple-darwin18.5.0/release/build/baldrdash-d88a7a2557f030b4/build-script-build`
 (exit code: 101)
 7:09.31 --- stdout
 7:09.31 cargo:rerun-if-changed=baldrapi.h
 7:09.31 
cargo:rerun-if-changed=/Users/greg/moz-source/obj-x86_64-apple-darwin18.5.0/js/src/rust/extra-bindgen-flags
 7:09.31 --- stderr
 7:09.31 /usr/local/Cellar/llvm/7.0.1/lib/clang/7.0.1/include/inttypes.h:30:15: 
fatal error: 'inttypes.h' file not found
 7:09.31 /usr/local/Cellar/llvm/7.0.1/lib/clang/7.0.1/include/inttypes.h:30:15: 
fatal error: 'inttypes.h' file not found, err: true
 7:09.31 thread 'main' panicked at 'Unable to generate baldrapi.h bindings: 
()', src/libcore/result.rs:1009:5
 7:09.31 stack backtrace:
 7:09.31    0:        0x11013a8c3 - 
std::sys::unix::backtrace::tracing::imp::unwind_backtrace::h16b82ef029078385
 7:09.32    1:        0x11013545c - 
std::sys_common::backtrace::_print::hc39c8623f5320a3a

The unsuccessful #include statement is actually an #include_next, and not 
knowing the #include search path sequence for the current compile, I don't know 
were the compiler is *expecting* to find the subsidiary inttypes.h; there isn't 
one in the (Homebrew-installed) llvm instance shown here, though there is on in 
a couple other places on my machine, including my installation of Xcode.
_______________________________________________
dev-builds mailing list
dev-builds@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-builds

Reply via email to