1403001 - stylo: build error in bindings::write_binding_file: 'wchar.h' file not found after updating to macOS 10.13 and Xcode 9

Status: RESOLVED DUPLICATE of bug 1366564

(Firefox Build System :: General, defect)

Description

[Chris Peterson [:cpeterson]]

After updating from macOS 10.12 to 10.13 High Sierra and Xcode 9, I am no longer able to build mozilla-central.

@ Nathan and Emilio: I hit the following build errors. It looks like rust-bindgen is not able to llvm's header files. This might be a duplicate of bug 1366564, but everything built for me until I updated to macOS 10.13 and Xcode 9.

error: failed to run custom build command for `style v0.0.1 (servo/components/style)`
process didn't exit successfully: `obj-x86_64-apple-darwin17.0.0-debug/toolkit/library/debug/build/style-5bae866266aa3907/build-script-build` (exit code: 101)
...
/Users/chris/.mozbuild/clang/include/c++/v1/wchar.h:119:15: fatal error: 'wchar.h' file not found, err: true
/Users/chris/.mozbuild/clang/include/c++/v1/stdlib.h:94:15: fatal error: 'stdlib.h' file not found, err: true
/Users/chris/.mozbuild/clang/include/c++/v1/stdlib.h:94:15: fatal error: 'stdlib.h' file not found, err: true
...
stack backtrace:
   0:        0x10bace693 - std::sys::imp::backtrace::tracing::imp::unwind_backtrace::h5d6b821bcccc8af3
   1:        0x10bad393a - std::panicking::default_hook::{{closure}}::haca53f8b96e15b81
   2:        0x10bad3602 - std::panicking::default_hook::h0029f59c1ec97ffc
   3:        0x10bad5c02 - std::panicking::rust_panic_with_hook::hb8eae939c3fcaf9c
   4:        0x10bad5a64 - std::panicking::begin_panic_new::h3c5f9a0be81106be
   5:        0x10bad59b2 - std::panicking::begin_panic_fmt::hf585b6224c51a06c
   6:        0x10b6704e4 - build_script_build::build_gecko::bindings::write_binding_file::h108daf1eae920715
   7:        0x10b676547 - build_script_build::build_gecko::bindings::generate_bindings::h8f82b8739ed8c19b
   8:        0x10bad6d5c - __rust_maybe_catch_panic
   9:        0x10b6515c3 - std::panicking::try::hb05e18b0e556c283
  10:        0x10b63eccd - std::panic::catch_unwind::hfcaf6e5980adbbe2
  11: g       0x10b651109 - std::thread::Builder::spawn::{{closure}}::h93915fd1af5b7fd3
  12:        0x10b65a8a5 - <F as alloc::boxed::++FnBox -<Astd=gnu+>>+1::1 call_box::h4e76c6fa4025e608
  13:        0x10bad2f3b - std::sys::imp::thread::Thread::new::thread_start::h823686b907c11c46
  14:     0x7fff738de6c0 - _pthread_body
  15:     0x7fff738de56c - _pthread_start

Comment 1

[J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow)]

Does re-running `xcode-select --install` fix this?  It's possible this needs to be repeated after upgrading Xcode.

Comment 2

[Stephen A Pohl [:spohl]]

(In reply to J. Ryan Stinnett [:jryans] (use ni?) from comment #1)
> Does re-running `xcode-select --install` fix this?  It's possible this needs
> to be repeated after upgrading Xcode.

I just noticed this bug and was going to comment the same. I have upgraded to macOS 10.13 from the latest 10.13 beta and had to rerun `xcode-select --install` before I could successfully build again. Note that the App Store did not offer an update to XCode, command line tools or any other app.

Comment 3

[Emilio Cobos Álvarez (:emilio)]

(In reply to J. Ryan Stinnett [:jryans] (use ni?) from comment #1)
> Does re-running `xcode-select --install` fix this?  It's possible this needs
> to be repeated after upgrading Xcode.

I don't immediately have any better idea than this, and seems to work so...

Comment 4

[Jonathan Watt [:jwatt]]

(In reply to J. Ryan Stinnett [:jryans] (use ni?) from comment #1)
> Does re-running `xcode-select --install` fix this?

It did for me.

Comment 5

[Gregory Szorc [:gps]]

Bleh. Configure should detect when xcode tools aren't in a happy state and present an actionable error message that tells users how to correct the problem.

I haven't upgraded to High Sierra yet. I may do that over lunch in ~2 hours. If I can repro and others don't beat me to it, I'll try to piece together a patch.

Comment 6

[Stephen A Pohl [:spohl]]

(In reply to Gregory Szorc [:gps] from comment #5)
> Bleh. Configure should detect when xcode tools aren't in a happy state and
> present an actionable error message that tells users how to correct the
> problem.
> 
> I haven't upgraded to High Sierra yet. I may do that over lunch in ~2 hours.
> If I can repro and others don't beat me to it, I'll try to piece together a
> patch.

There may be another way to trigger this, without upgrading to High Sierra. I just tried deleting /Library/Developer/CommandLineTools and doing a clobber build. However, this did not seem to be enough to cause the issue despite the fact that `xcode-select --install` detects that the command line tools are no longer installed.

Not sure how configure works, but calling `xcode-select --install` will either open a prompt to install the command line tools if they're not installed, or return an error stating that the command line tools are already installed. Maybe calling `xcode-select --install` can be incorporated?

Comment 7

[Gregory Szorc [:gps]]

Let's take discussion over to the original report of this bug, which has a bit more useful technical info.