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
add fallback curl config #1917
base: main
Are you sure you want to change the base?
add fallback curl config #1917
Conversation
Hello @keith, modules you maintain (curl) have been updated in this PR. Please review the changes. |
wouldn't it have to be patches that are in the curl dependency tree and setting that as |
I don't think so. I believe if you have a target that depends on from bazel docs about
This goes for |
these are the modules that currently set
In my project I believe mine was caused by utilising |
meaning curl would have to depend on the libraries that have it for it to cause an issue. note that I'm actually working on making curl use HAVE_CONFIG_H which i think is safer than what we're doing now |
should be fixed by #1943 |
I see what you're saying, but I assumed the opposite was true as well. I've been able to reproduce it here: https://github.com/ecsact-dev/ecsact_cli/actions/runs/8947494955/job/24579495333#step:4:270 cc_binary(
name = "ecsact_cli",
# ...
deps = [
"//ecsact/cli/commands:codegen",
"//ecsact/cli/commands:command",
"//ecsact/cli/commands:config",
"//ecsact/cli/commands:build",
"//ecsact/cli/commands:recipe-bundle", # offending target with @curl + @libarchive
],
)
When I comment out I'm trying to make a smaller repro, but I haven't successfully done so. |
interesting. as long as |
several packages have it in |
several C/C++ packages define
HAVE_CONFIG_H
which leaks into curl causing an errorthis adds the default
curl_config.h
header to avoid this issuealternatively we could update several other packages in the BCR to not define
HAVE_CONFIG_H