-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Failed to build Bazel 5.0.0 on Fedora #14819
Comments
@vbatts Can you help investigate this issue? Is this due to an old gcc version you use? |
@bazel-io fork 5.1 |
On 22/02/22 02:20 -0800, Yun Peng wrote:
***@***.*** Can you help investigate this issue? Is this due to an old gcc version you use?
A) this is seems to be on newer releases of fedora, so maybe not old
gcc. You can see in some of the build logs, the versions of gcc/glibc
being used.
B) this is not stuff that I am _using_, but rather community builds of
bazel for fedora and centos
|
@vbatts I understand, can you help debug this or provide a fedora docker image so we can reproduce the failure, currently we have no way to investigate what's going wrong. |
sure thing. These copr builds are done from
https://github.com/vbatts/copr-build-bazel/
To get a shell within fedora rawhide (default is "latest" which is
currently fedora 35):
```shell
make .container.run FED_VER=rawhide
```
and then to see the build failure (within the container):
```shell
make rebuild
```
|
Hmm, the build actually succeeded for me. Is this change related vbatts/copr-build-bazel@3d85864 ? |
classic. I forgot to commit&push.
Notice, it succeeded because that was fedora 34.
Please fetch from latest on copr-build-bazel.
|
I'm getting when running
Can you help check if setting BAZEL_CXXOPTS=c++11 helps? And vbatts/copr-build-bazel@3d85864 seems to be fixing a similar issue, do you know what's the difference this time? |
Thank you for contributing to the Bazel repository! This issue has been marked as stale since it has not had any activity in the last 1+ years. It will be closed in the next 14 days unless any other activity occurs or one of the following labels is added: "not stale", "awaiting-bazeler". Please reach out to the triage team ( |
we can close this issue. I'll open a new one regarding builds on fedora 38 and recent bazel versions (6.2 and 6.3). |
from @vbatts:
I've kicked off builds for fedora and cento.
This marks as package name as "bazel5"
https://copr.fedorainfracloud.org/coprs/build/3493215
The build failed on a number of the platforms
https://download.copr.fedorainfracloud.org/results/vbatts/bazel/fedora-36-aarch64/03493215-bazel5/build.log.gz
https://download.copr.fedorainfracloud.org/results/vbatts/bazel/epel-7-ppc64le/03493215-bazel5/build.log.gz
The text was updated successfully, but these errors were encountered: