-
Notifications
You must be signed in to change notification settings - Fork 37
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 glibc binary #70
Add glibc binary #70
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This does not appear to build out of the box on our centos6 image, due to a requirement on bison 2.7 (centos6 has bison 2.4). That image is using devtoolset-7-gcc
, but it doesn't appear to include bison.
I should have checked that before making this pr! I will see if it's reasonable to build or download bison 2.7 as part of the build process for the |
- also add some TODOs about a possible utils.v2.bash
Let me know when this is reviewable again. |
@stuhood after fd2f10c, this should be reviewable -- it builds on my exact-same-docker-image. Once |
That's wrong! There's a later build failure. Sorry, will be 100% sure next time. |
Can you confirm that the downgraded glibc actually needs the newer bison? It looks sufficiently old to maybe work in the centos image. EDIT: I confirmed that it still needs bison
...so perhaps it's possible to skip that step in the configure script. |
I believe it is, I had seen that in the release notes but did not think more of it. Will implement that now. |
@stuhood I have not been able to get this to build in a finite amount of time in my centos6 image. Setting |
I have this (post 10d1827) running in the background. |
It failed with:
|
Ok, that was the exact error that the serial make had fixed. I didn't see it repro when I tested it, so I tried adding parallelism again, but I guess that's the thing about concurrency errors. I have reverted that commit and it should work -- if you run into a new issue I will investigate. Thanks for your patience. |
...hm. That previous failure was likely because my machine is out of disk space. |
Oh. That might explain why I saw it running concurrently and not single
threaded (which I never have yet ran to completion and may have eventually
hit the same out of space error?)
…On Wed, Jun 13, 2018 at 12:07 Stu Hood ***@***.***> wrote:
...hm. That previous failure was likely because my machine is out of disk
space.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#70 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABPqT-gP_U6oAGgYnWj_C-j3605hKGUaks5t8WLwgaJpZM4UhERl>
.
|
See discussion in pantsbuild/pants#5943 -- we shouldn't be providing glibc, and we will instead be searching for it on the host, or erroring out. |
See pantsbuild/pants#5943. We are providing the
glibc
binary (55 MB tar.gz file), which we build from source. We provide version2.27
, the newest version. The script works on my machine and the archive produced works with theGLibc
BinaryTool from pantsbuild/pants#5943 on my machine as well (the unskipped tests pass).