Changes required for GLIBC backward compatibility with gitian builds#501
Conversation
|
I'm still building final gitian build locally, will post hashes once done. |
dc116f0 to
213e1ba
Compare
|
can't test this till next week (monday) |
98bff46 to
712c20a
Compare
2251c0f to
0aea3d3
Compare
031b1de to
e338010
Compare
c6cc185 to
dd3462c
Compare
|
Added |
|
Gitian build hashes for 8d41032 Hashes: |
|
just a question, are you sure the flag should be |
Works either way 👍 I'm just used to not adding the space when doing |
|
BTW @proletesseract I've tested the gitian build on here, and I can confirm the pink color on the GUI on OSX. I'll see if I can fix it and create a PR |
|
ACK |
|
im running the gitian build on this PR now to confirm hashes |
|
@aguycalled I wanna change my bounty address to |
|
hashes match for me too, tested osx/debian |
|
Paid 1a630ac0f1736659e6362fd11eb8bee53d0e365b9f1a8640204f2a3690759bb2 |
This closes #482
These changes include some upstream changes to./src/compatcode and gitian build for linux downgraded totrustyso that the linux binaries will use older GLIBC when linkingWindows and OSX builds remain onbionicas they did not have the GLIBC back compat issuelibcurl had to be downgraded back to 7.58.0 ( Which was the version before PR #461 )EDIT:
All builds remain on
bionicAdded more compat code to get
libunbound 1.9.0andlibcurl 7.64working with older GLIBC