process-tools-darwin: EXIT_FAILURE comes from stdlib.h

No idea why this is failing only in our builds (and not, say, Bazel CI), but I
ran into the following when bootstrapping Bazel 3.3.0 on macOS:

```
src/main/tools/process-tools-darwin.cc:48:5: error: use of undeclared identifier 'EXIT_FAILURE'
    DIE("Expected only one event from the kevent call; got %d", nev);
```

In response, let's pull in stdlib.h.

Resolves #11640.

Testing Done:
- bootstrapped Bazel 3.3.0 on macOS 10.15 (Catalina) w/ Xcode 10.

Closes #11641.

PiperOrigin-RevId: 319384680
1 file changed
tree: 3dd932d2a0aa907aa9a7c0fce94066b0b5258301
  1. .bazelci/
  2. examples/
  3. scripts/
  4. site/
  5. src/
  6. third_party/
  7. tools/
  8. .bazelrc
  9. .gitattributes
  10. .gitignore
  11. AUTHORS
  12. BUILD
  13. CHANGELOG.md
  14. CODEOWNERS
  15. combine_distfiles.py
  16. combine_distfiles_to_tar.sh
  17. compile.sh
  18. CONTRIBUTING.md
  19. CONTRIBUTORS
  20. distdir.bzl
  21. ISSUE_TEMPLATE.md
  22. LICENSE
  23. README.md
  24. WORKSPACE
README.md

Bazel

{Fast, Correct} - Choose two

Build and test software of any size, quickly and reliably.

  • Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.

  • One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.

  • Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.

  • Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.

Getting Started

Documentation

Contributing to Bazel

See CONTRIBUTING.md

Build status