Skip to content
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.

Sign up for GitHub

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

Jump to bottom

fix(whitepaper): build fails on Ubuntu 18 due to glibc 2.29 #703

Closed
petermetz opened this issue Mar 22, 2021 · 0 comments · Fixed by #706
Closed

fix(whitepaper): build fails on Ubuntu 18 due to glibc 2.29 #703

petermetz opened this issue Mar 22, 2021 · 0 comments · Fixed by #706
Assignees
@petermetz
Labels
bug Something isn't working

Comments

@petermetz
Copy link
Contributor

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:

  1. Also making it work on Windows (and Ubuntu 18 of course)
  2. Will be easier to make the whitepaper build part of the CI as well

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 pdf

Expected behavior

make task building the pdf just works, no issues.

Logs/Stack traces

wkhtmltopdf --dpi 150 --disable-smart-shrinking hyperledger-cactus-whitepaper.html --allow  - hyperledger-cactus-whitepaper.pdf
wkhtmltopdf: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by wkhtmltopdf)
wkhtmltopdf: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by wkhtmltopdf)
Makefile:13: recipe for target 'pdf' failed
make: *** [pdf] Error 1

Screenshots

N/A

Cloud provider or hardware configuration:

Dev machine

Operating system name, version, build:

Ubuntu 18.04

Hyperledger Cactus release version or commit (git rev-parse --short HEAD):

main @ a28edcf

Hyperledger Cactus Plugins/Connectors Used

N/A

Additional 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
@petermetz petermetz added the bug Something isn't working label Mar 22, 2021
@petermetz petermetz self-assigned this Mar 22, 2021
petermetz added a commit to petermetz/cacti that referenced this issue Mar 22, 2021
@petermetz
fix(whitepaper): build fails on Ubuntu 18 due to glibc 2.29 hyperledg…
e0093d5 
…er-cacti#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-cacti#703

Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
@petermetz petermetz mentioned this issue Mar 23, 2021
Merged
petermetz added a commit to petermetz/cacti that referenced this issue Mar 23, 2021
@petermetz
fix(whitepaper): build fails on Ubuntu 18 due to glibc 2.29 hyperledg…
ab21451 
…er-cacti#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-cacti#703

Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
petermetz added a commit to petermetz/cacti that referenced this issue Apr 5, 2021
@petermetz
fix(whitepaper): build fails on Ubuntu 18 due to glibc 2.29 hyperledg…
4099ce4 
…er-cacti#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-cacti#703

Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
petermetz added a commit that referenced this issue Apr 18, 2021
@petermetz
fix(whitepaper): build fails on Ubuntu 18 due to glibc 2.29 #703
ec22a0f 
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
Assignees

@petermetz petermetz

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(whitepaper): build fails on Ubuntu 18 due to glibc 2.29 #703 petermetz/cacti
1 participant
@petermetz