Skip to content
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

Build problem: Bazel trying to download zlib from bad URL #153

Open
philtomson opened this issue Jan 31, 2023 · 1 comment
Open

Build problem: Bazel trying to download zlib from bad URL #153

philtomson opened this issue Jan 31, 2023 · 1 comment

Comments

@philtomson
Copy link

I managed to get the make install to work with OCaml 4.08.1. (there were issues with mismatching checksums for rules_cc and rules_proto in the WORKSPACE file - apparently the checksums have changed, see this article: https://github.blog/changelog/2023-01-30-git-archive-checksums-may-change/ - I managed to get it working by changing the expected checksums)

However, make build fails because bazel is trying to fetch zlib from a bad URL:

INFO: Repository zlib instantiated at:
/home/phil/build/bolt/WORKSPACE:38:25: in
/home/phil/.cache/bazel/_bazel_phil/abeafe38d8f7979ebcff8db245dd2916/external/rules_proto/proto/repositories.bzl:23:21: in rules_proto_dependencies
Repository rule http_archive defined at:
/home/phil/.cache/bazel/_bazel_phil/abeafe38d8f7979ebcff8db245dd2916/external/bazel_tools/tools/build_defs/repo/http.bzl:372:31: in
WARNING: Download from https://zlib.net/zlib-1.2.11.tar.gz failed: class java.io.FileNotFoundException GET returned 404 Not Found
ERROR: An error occurred during the fetch of repository 'zlib':
Traceback (most recent call last):
File "/home/phil/.cache/bazel/_bazel_phil/abeafe38d8f7979ebcff8db245dd2916/external/bazel_tools/tools/build_defs/repo/http.bzl", line 132, column 45, in _http_archive_impl

I've not been able to figure out where that zlib URL is defined so I can change it.

@sudip-unb
Copy link

I am also facing the exact same issue because of the broken URL and it is probably coming from WORKSPACE file. However, could not resolved it yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants