Open keith opened 2 years ago
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted" or "no stalebot". Thank you for your contributions.
Hi @keith , did you ever make it past this? I'm hitting something similar. Thanks
I don't think so
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.
I have a similar issue when trying to build envoy with clang as well.
I have a similar issue when trying to build envoy with clang as well.
In my case, I unset a bunch of env vars in the patch file which seemed to be interfering with the boring ssl build
unset LDFLAGS
unset BAZEL_CXXOPTS
unset BAZEL_COMPILER
unset BAZEL_LINKLIBS
unset CXXFLAGS
unset LLVM_CONFIG
unset CXX
unset BAZEL_LINKOPTS
unset CLANG_FORMAT
unset CC
Building with
bazelisk build envoy -c opt --config=clang --define=boringssl=fips
on 851606902390f9e650002538114f89ab95596ab4: