fix(whitepaper): build fails on Ubuntu 18 due to glibc 2.29 #703
Assignees
Labels
bug
Something isn't working
Comments
petermetz
added a commit
to petermetz/cacti
that referenced
this issue
Mar 22, 2021
…er#703 Refactored the whitepaper build toolchain to be based on entirely just containers so that it is easier to set up the build which now only requires a working docker installation and make (for the Makefile). Also refactored the generated files to be placed under the ./whitepaper/build/ directory instead of being dumped straight into the ./whitepaper/ directory so that it is easier to differentiate between what are build files and what are not. There are 3 different pdf generation tasks in order to provide contributors with a way of comparing the differnet pdfs rendring issues (since we have a few bugs active in that sense still). The supposedly "best" pdf render is produced by the make target called "pdf-wk-with-flags" which is exported to the build directory with a similar suffix in the filename as well. The new way to do a full build is by issuing the `make` command from the ./whitepaper/ directory of the project. A Dockerfile was added accordingly and is tagged for the current revision on DockerHub as: petermetz/cactus-whitepaper-builder:2021-03-22-fix-703 Fixes hyperledger#703 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
petermetz
added a commit
to petermetz/cacti
that referenced
this issue
Mar 23, 2021
…er#703 Refactored the whitepaper build toolchain to be based on entirely just containers so that it is easier to set up the build which now only requires a working docker installation and make (for the Makefile). Also refactored the generated files to be placed under the ./whitepaper/build/ directory instead of being dumped straight into the ./whitepaper/ directory so that it is easier to differentiate between what are build files and what are not. There are 3 different pdf generation tasks in order to provide contributors with a way of comparing the differnet pdfs rendring issues (since we have a few bugs active in that sense still). The supposedly "best" pdf render is produced by the make target called "pdf-wk-with-flags" which is exported to the build directory with a similar suffix in the filename as well. The new way to do a full build is by issuing the `make` command from the ./whitepaper/ directory of the project. A Dockerfile was added accordingly and is tagged for the current revision on DockerHub as: petermetz/cactus-whitepaper-builder:2021-03-22-fix-703 Fixes hyperledger#703 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
petermetz
added a commit
to petermetz/cacti
that referenced
this issue
Apr 5, 2021
…er#703 Refactored the whitepaper build toolchain to be based on entirely just containers so that it is easier to set up the build which now only requires a working docker installation and make (for the Makefile). Also refactored the generated files to be placed under the ./whitepaper/build/ directory instead of being dumped straight into the ./whitepaper/ directory so that it is easier to differentiate between what are build files and what are not. There are 3 different pdf generation tasks in order to provide contributors with a way of comparing the differnet pdfs rendring issues (since we have a few bugs active in that sense still). The supposedly "best" pdf render is produced by the make target called "pdf-wk-with-flags" which is exported to the build directory with a similar suffix in the filename as well. The new way to do a full build is by issuing the `make` command from the ./whitepaper/ directory of the project. A Dockerfile was added accordingly and is tagged for the current revision on DockerHub as: petermetz/cactus-whitepaper-builder:2021-03-22-fix-703 Fixes hyperledger#703 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
petermetz
added a commit
that referenced
this issue
Apr 18, 2021
Refactored the whitepaper build toolchain to be based on entirely just containers so that it is easier to set up the build which now only requires a working docker installation and make (for the Makefile). Also refactored the generated files to be placed under the ./whitepaper/build/ directory instead of being dumped straight into the ./whitepaper/ directory so that it is easier to differentiate between what are build files and what are not. There are 3 different pdf generation tasks in order to provide contributors with a way of comparing the differnet pdfs rendring issues (since we have a few bugs active in that sense still). The supposedly "best" pdf render is produced by the make target called "pdf-wk-with-flags" which is exported to the build directory with a similar suffix in the filename as well. The new way to do a full build is by issuing the `make` command from the ./whitepaper/ directory of the project. A Dockerfile was added accordingly and is tagged for the current revision on DockerHub as: petermetz/cactus-whitepaper-builder:2021-03-22-fix-703 Fixes #703 Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Back when the whitepaper build tooling was created it was working fine on Ubuntu 18 but nowadays it appears that the required glibc is not included in the repos for Ubuntu 18.
Rather than going for hacks it would be best to just containerize the build process that comes with the benefits of:
To Reproduce
Try to do this on an Ubuntu 18 machine and observe how it fails due to glibc being older than the required (and not being possible to be upgraded from the standard apt repos either)
cd whitepaper make configure make pdfExpected behavior
make task building the pdf just works, no issues.
Logs/Stack traces
Screenshots
N/ACloud provider or hardware configuration:
Dev machineOperating system name, version, build:
Ubuntu 18.04
Hyperledger Cactus release version or commit (git rev-parse --short HEAD):
main@ a28edcfHyperledger Cactus Plugins/Connectors Used
N/AAdditional context
https://askubuntu.com/questions/1143268/how-to-install-a-libc6-version-2-29
cc: @takeutak @sfuji822 @hartm @jonathan-m-hamilton @AzaharaC @jordigiam @kikoncuo @jagpreetsinghsasan
The text was updated successfully, but these errors were encountered: