Description of the problem / feature request:

Setting --incompatible_disallow_empty_glob fails on an empty blob in the local_jdk BAZEL.build file:

ERROR: Traceback (most recent call last):
--
  | File "/private/var/tmp/_bazel_user/757d2abf201e5b6570ee61ba6989ac5c/external/local_jdk/BUILD.bazel", line 177, column 16, in <toplevel>
  | srcs = glob(["include/**"]),
  | Error in glob: glob pattern 'include/**' didn't match anything, but allow_empty is set to False (the default value of allow_empty can be set with --incompatible_disallow_empty_glob).

Feature requests: what underlying problem are you trying to solve with this feature?

Use --incompatible_disallow_empty_glob

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

I believe have a local JDK installed and attempt to build with --incompatible_disallow_empty_glob

What operating system are you running Bazel on?

macOS 15.2

What's the output of bazel info release?

release 5.0.0

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

N/A

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

N/A

Have you found anything relevant by searching the web?

I have not

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

Replace this line with your answer.