Xcode 16 incompatibility

[lgalfaso]

Description of the bug:

After updating to XCode 16, got the following error

ERROR: XXX/BUILD:7:11: Compiling xxx.cpp failed: absolute path inclusion(s) found in rule '//XXX':
the source file 'xxx.cpp' includes the following non-builtin files with absolute paths (if these are builtin files, make sure these paths are in your toolchain):
'/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/16/include/stdint.h'

Which category does this issue belong to?

C++ Rules

What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

Update to Xcode 16, and compile anything that uses 'stdint.h' (I would expect that this issue is not limited to stdint.h)

Which operating system are you running Bazel on?

MacOS 14.6.1

What is the output of bazel info release?

release 7.3.1

If bazel info release returns development version or (@non-git), tell us how you built Bazel.

No response

What's the output of git remote get-url origin; git rev-parse HEAD ?

No response

If this is a regression, please try to identify the Bazel commit where the bug was introduced with bazelisk --bisect.

No response

Have you found anything relevant by searching the web?

No response

Any other information, logs, or outputs that you want to share?

No response

[tjgq]

cc @keith

[fmeum]

Can you run bazel fetch --configure and see whether that fixes your build?

You may have to rerun this command if something non-hermetic (such as Xcode) changes on your machine.

[lgalfaso]

After running

% bazel fetch --configure   
INFO: All external dependencies fetched successfully.
Computing main repo mapping: 

I'm still seeing the same error.

[lgalfaso]

Running bazel fetch --force --configure did work :)

Thanks!

[fmeum]

@meteorcloudy The behavior of bazel fetch --configure doesn't match that of bazel sync --configure. Requiring the additional --force seems unnecessary, what do you think?

I also noticed that --configure seems to be ignored if the command has a residue. That seems confusing, how about we make this case an error?

[meteorcloudy]

@fmeum All sounds good to me! I can send a fix later this week.