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.

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

error while loading shared libraries: libaom.so.0: cannot open shared object file: No such file or directory #99

Closed
Lilac-Dream opened this issue Jan 27, 2022 · 5 comments · Fixed by #110
Assignees

Comments

@Lilac-Dream
Copy link

About Error
First:
image
Next: I make a right config.json and try to run it.
image

To Reproduce
I cann't use Releases(0.4.1 & 0.4.0) , but i can use Releases(0.3.2).

Environment (please complete the following information):
CentOS Linux release 8.5.2111

What should i do? Thank you~

@BennyThink
Copy link
Member

Can you try to install libaom?

@Lilac-Dream
Copy link
Author

image

I tried, and it didn't work.

@BennyThink
Copy link
Member

BennyThink commented Jan 27, 2022

Okay, it appears we build the binary using the latest version of Ubuntu, which has a newer version of glibc. One temporary solution is to use docker. The other one is to upgrade glibc.

We'll try to fix it later.

@n0vad3v
Copy link
Member

n0vad3v commented Jan 27, 2022

@BennyThink is making a point. Yes it's an issue for us.

However there is still another option to make it usable on CentOS without using Docker, that's to compile WebP Server Go on CentOS, instruction can be found on https://docs.webp.sh/BUILD.html.

@n0vad3v n0vad3v closed this as completed Mar 14, 2022
@n0vad3v n0vad3v linked a pull request Mar 24, 2022 that will close this issue
@n0vad3v
Copy link
Member

n0vad3v commented Mar 24, 2022

Please have a try on the latest version: https://github.com/webp-sh/webp_server_go/releases/tag/0.4.4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants