-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vendored zlib 1.3 doesn't work with macOS SDK 11 + clang19 and later (upgrade to 1.3.1) #25124
Labels
P2
We'll consider working on this in future. (Assignee optional)
team-ExternalDeps
External dependency handling, remote repositiories, WORKSPACE file.
team-Rules-Java
Issues for Java rules
type: bug
Comments
sgowroji
added
the
team-ExternalDeps
External dependency handling, remote repositiories, WORKSPACE file.
label
Jan 29, 2025
malt3
changed the title
vendored zlib 1.3 doesn't work with macOS SDK 11 and later (upgrade to 1.3.1)
vendored zlib 1.3 doesn't work with macOS SDK 11 + clan19 and later (upgrade to 1.3.1)
Jan 29, 2025
@hvadehra for java_tools |
malt3
changed the title
vendored zlib 1.3 doesn't work with macOS SDK 11 + clan19 and later (upgrade to 1.3.1)
vendored zlib 1.3 doesn't work with macOS SDK 11 + clang19 and later (upgrade to 1.3.1)
Jan 29, 2025
malt3
added a commit
to tweag/rules_nixpkgs
that referenced
this issue
Jan 29, 2025
zlib 1.3 cannot be built with clang 19 and macOS SDK 11. Upating the vendored zlib to the latest version resolves this issue. This patch can be dropped once the following upstream issue is solved: bazelbuild/bazel#25124
malt3
added a commit
to tweag/rules_nixpkgs
that referenced
this issue
Jan 29, 2025
zlib 1.3 cannot be built with clang 19 and macOS SDK 11. Upating the vendored zlib to the latest version resolves this issue. This patch can be dropped once the following upstream issue is solved: bazelbuild/bazel#25124
malt3
added a commit
to tweag/rules_nixpkgs
that referenced
this issue
Jan 29, 2025
zlib 1.3 cannot be built with clang 19 and macOS SDK 11. Upating the vendored zlib to the latest version resolves this issue. This patch can be dropped once the following upstream issue is solved: bazelbuild/bazel#25124
To follow. |
Have your project migrated to Bzlmod or have you tried a newer Bazel version? In Bazel 8, zlib 1.3.1.bcr.1 should be used. |
But yes, we should get rid of the vendored zlib in Bazel source. |
meteorcloudy
added
P2
We'll consider working on this in future. (Assignee optional)
team-Rules-Java
Issues for Java rules
and removed
untriaged
labels
Feb 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
P2
We'll consider working on this in future. (Assignee optional)
team-ExternalDeps
External dependency handling, remote repositiories, WORKSPACE file.
team-Rules-Java
Issues for Java rules
type: bug
Description of the bug:
The version of zlib currently vendored in Bazel (
third_party/zlib
) contains zlib 1.3.Newer versions of clang and the macOS SDK cannot compile it, due to
fdopen
not being defined.Upgrading to zlib 1.3.1 helps (I tested it by patching
remote_java_tools
).Which category does this issue belong to?
Java Rules
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Use rules_java and set the macOS SDK to 11 or later. Build any
java_library
,java_binary
orjava_test
.Which operating system are you running Bazel on?
macOS
What is the output of
bazel info release
?release 6.5.0 (tested with later versions up to 8.0.0)
If
bazel info release
returnsdevelopment 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
?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?
Other projects also reported issues with zlib 1.3 and newer macOS SDKs: pocoproject/poco#4586
Any other information, logs, or outputs that you want to share?
Output when trying to build
zlib
as part of java_tools:The text was updated successfully, but these errors were encountered: