[GH-ISSUE #165] ubuntu 18 compatibility? #121

Closed
opened 2026-02-25 23:33:29 +03:00 by kerem · 7 comments
Owner

Originally created by @sigmonsays on GitHub (Sep 22, 2019).
Original GitHub issue: https://github.com/go-shiori/shiori/issues/165

sig@desktop2:~/Downloads$ ./shiori-linux-amd64 
./shiori-linux-amd64: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by ./shiori-linux-amd64)

sig@desktop2:~/Downloads$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.2 LTS
Release:        18.04
Codename:       bionic

sig@desktop2:~/Downloads$ file $(which ls)
/bin/ls: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/l, for GNU/Linux 3.2.0, BuildID[sha1]=9567f9a28e66f4d7ec4baf31cfbf68d0410f0ae6, stripped
Originally created by @sigmonsays on GitHub (Sep 22, 2019). Original GitHub issue: https://github.com/go-shiori/shiori/issues/165 <pre> sig@desktop2:~/Downloads$ ./shiori-linux-amd64 ./shiori-linux-amd64: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by ./shiori-linux-amd64) sig@desktop2:~/Downloads$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic sig@desktop2:~/Downloads$ file $(which ls) /bin/ls: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/l, for GNU/Linux 3.2.0, BuildID[sha1]=9567f9a28e66f4d7ec4baf31cfbf68d0410f0ae6, stripped </pre>
kerem closed this issue 2026-02-25 23:33:30 +03:00
Author
Owner

@deanishe commented on GitHub (Sep 23, 2019):

I had the same issue on Stretch. It works fine if you build it yourself.

<!-- gh-comment-id:533953390 --> @deanishe commented on GitHub (Sep 23, 2019): I had the same issue on Stretch. It works fine if you build it yourself.
Author
Owner

@RadhiFadlillah commented on GitHub (Sep 23, 2019):

Yeah, this is the problem when building Linux binary from distro with rolling release like Manjaro. I will use Ubuntu VM to replace it ASAP.

<!-- gh-comment-id:533965501 --> @RadhiFadlillah commented on GitHub (Sep 23, 2019): Yeah, this is the problem when building Linux binary from distro with rolling release like Manjaro. I will use Ubuntu VM to replace it ASAP.
Author
Owner

@RadhiFadlillah commented on GitHub (Sep 24, 2019):

Could you check the shiori-linux-amd64-buster in release page ? I've build it using Debian buster which hopefully fixed this issue.

<!-- gh-comment-id:534388380 --> @RadhiFadlillah commented on GitHub (Sep 24, 2019): Could you check the [`shiori-linux-amd64-buster`](https://github.com/go-shiori/shiori/releases/download/v1.5.0/shiori-linux-amd64-buster) in release page ? I've build it using Debian buster which hopefully fixed this issue.
Author
Owner

@shyim commented on GitHub (Sep 24, 2019):

I have the same with both binaries.
maybe just add travis which builds everything for you

<!-- gh-comment-id:534637490 --> @shyim commented on GitHub (Sep 24, 2019): I have the same with both binaries. maybe just add travis which builds everything for you
Author
Owner

@sigmonsays commented on GitHub (Sep 24, 2019):

Thanks for the cool project.

shiori-linux-amd64-buster shows the same issue on ubuntu 18.

I think travis is a good idea. It might be worth building in a docker for the target platform if you want more control. Here is an example script I put together. Let me know if you want it in a PR

Create the build script, buildit

#!/bin/bash
set -x
export GOPATH=/go
apt-get update
apt-get install -y git wget gcc
mkdir -p /usr/local
cd /usr/local
wget -O go.tar.gz https://dl.google.com/go/go1.13.linux-amd64.tar.gz
tar zxf go.tar.gz
export PATH="$PATH:/usr/local/go/bin"
go get github.com/go-shiori/shiori
cp -v $GOPATH/bin/* /target

then build it

rm -rf build
mkdir build
docker run --rm -v $(pwd)/build:/target -v $(pwd)/buildit:/build ubuntu:bionic /build
<!-- gh-comment-id:534677683 --> @sigmonsays commented on GitHub (Sep 24, 2019): Thanks for the cool project. shiori-linux-amd64-buster shows the same issue on ubuntu 18. I think travis is a good idea. It might be worth building in a docker for the target platform if you want more control. Here is an example script I put together. Let me know if you want it in a PR Create the build script, buildit <pre> #!/bin/bash set -x export GOPATH=/go apt-get update apt-get install -y git wget gcc mkdir -p /usr/local cd /usr/local wget -O go.tar.gz https://dl.google.com/go/go1.13.linux-amd64.tar.gz tar zxf go.tar.gz export PATH="$PATH:/usr/local/go/bin" go get github.com/go-shiori/shiori cp -v $GOPATH/bin/* /target </pre> then build it <pre> rm -rf build mkdir build docker run --rm -v $(pwd)/build:/target -v $(pwd)/buildit:/build ubuntu:bionic /build </pre>
Author
Owner

@RadhiFadlillah commented on GitHub (Sep 25, 2019):

@sigmonsays sorry, now Ubuntu 18.04 should be supported by shiori-linux-amd64-stretch in release page. It seems Ubuntu 18.04 still use GLIBC 2.27 while Buster and Manjaro is 2.28 alreay. Fortunately Debian Stretch still in 2.24, so I used that one.

For Travis I don't think I want to use it for now. There are still no unit test yet, and the release for Shiori is still not that often so IMHO it's better for me to build it manually.

<!-- gh-comment-id:534815870 --> @RadhiFadlillah commented on GitHub (Sep 25, 2019): @sigmonsays sorry, now Ubuntu 18.04 should be supported by [`shiori-linux-amd64-stretch`](https://github.com/go-shiori/shiori/releases/download/v1.5.0/shiori-linux-amd64-stretch) in release page. It seems Ubuntu 18.04 still use GLIBC 2.27 while Buster and Manjaro is 2.28 alreay. Fortunately Debian Stretch still in 2.24, so I used that one. For Travis I don't think I want to use it for now. There are still no unit test yet, and the release for Shiori is still not that often so IMHO it's better for me to build it manually.
Author
Owner

@RadhiFadlillah commented on GitHub (Oct 4, 2019):

Since it seems fixed now, I'll close this issue. Feel free to reopen it if needed.

<!-- gh-comment-id:538236946 --> @RadhiFadlillah commented on GitHub (Oct 4, 2019): Since it seems fixed now, I'll close this issue. Feel free to reopen it if needed.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/shiori#121
No description provided.