PINE64
slarm64 (unofficial slackware) Rock64 RK3328 (aarch64) - Printable Version

+- PINE64 (https://forum.pine64.org)
+-- Forum: ROCK64 (https://forum.pine64.org/forumdisplay.php?fid=85)
+--- Forum: Linux on Rock64 (https://forum.pine64.org/forumdisplay.php?fid=88)
+--- Thread: slarm64 (unofficial slackware) Rock64 RK3328 (aarch64) (/showthread.php?tid=5868)

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14

RE: slarm64 (unofficial slackware) Rock64 RK3328 (aarch64) - mara - 11-23-2020

(11-23-2020, 02:12 AM)Enig123 Wrote: Thank you for your quick help. BTW, I am using the base image, and the slackpkg installed from the current branch does not work as expected somehow. It kept asking for the correct pgp key.

Perhaps I installed the wrong version of slackpkg?

Edit: Another question is for how to unzip a .zip file, which usually use package named "unzip" in most Linux distributions.

in the file /etc/slackpkg/slackpkg.conf change CHECKGPG=on to CHECKGPG=off

unzip is in the package infozip-6.0-aarch64-5.txz

RE: slarm64 (unofficial slackware) Rock64 RK3328 (aarch64) - Enig123 - 11-23-2020

Further help needed please. When I was trying to compile some c program, the following error message appears:
/usr/libexec/gcc/aarch64-slackware-linux/10.2.0/cc1: error while loading shared libraries: libisl.so.23: cannot open shared object file: No such file or directory

How can I do to fix it? I've already installed both 'd' and 'l' categories.

Edit: Even if I resolved this error by adding link to /usr/lib64/libisl.so.22.0.1, there's other similar errors coming, like libzstd.so.1, there must be something wrong with my development setup.

RE: slarm64 (unofficial slackware) Rock64 RK3328 (aarch64) - mara - 11-23-2020

(11-23-2020, 02:42 PM)Enig123 Wrote: Further help needed please. When I was trying to compile some c program, the following error message appears:
/usr/libexec/gcc/aarch64-slackware-linux/10.2.0/cc1: error while loading shared libraries: libisl.so.23: cannot open shared object file: No such file or directory

How can I do to fix it? I've already installed both 'd' and 'l' categories.

Edit: Even if I resolved this error by adding link to /usr/lib64/libisl.so.22.0.1, there's other similar errors coming, like libzstd.so.1, there must be something wrong with my development setup.
the library is in l isl-0.23-aarch64-1.txz
it looks like not all packages are new.
try to do

Code:
slackpkg update
slackpkg upgrade-all


RE: slarm64 (unofficial slackware) Rock64 RK3328 (aarch64) - Enig123 - 11-23-2020

Tried it but with no success, unfortunately. The upgrade-all didn't do anything at all.

Edit: Other troubles that I've encountered, which also related to lib not found:
case 1: nslookup: error while loading shared libraries: libedit.so.0: cannot open shared object file: No such file or directory
case 2: dig: error while loading shared libraries: libjson-c.so.5: cannot open shared object file: No such file or directory

RE: slarm64 (unofficial slackware) Rock64 RK3328 (aarch64) - mara - 11-23-2020

this is a bit weird when using the image.
what image did you use.

yeah, you installed bind separately, so you also need to install the library data.

RE: slarm64 (unofficial slackware) Rock64 RK3328 (aarch64) - Enig123 - 11-23-2020

(11-23-2020, 04:24 PM)mara Wrote: this is a bit weird when using the image.
what image did you use.

yeah, you installed bind separately, so you also need to install the library data.
The image I am using is kernel 4.4.241 base.

As I recall, I didn't install bind separately, the nslookup command is already there.

And, which library data is needed for nslookup to work?

Edit: Right now, to fix the development environment is more urgent for me.

Edit1: Just tested nslookup with the 4.9.y base image, the same error message appeared.

RE: slarm64 (unofficial slackware) Rock64 RK3328 (aarch64) - mara - 11-24-2020

libedit-20191231_3.1-aarch64-1.txz
json-c-0.15_20200726-aarch64-1.txz

added packages required for bind

RE: slarm64 (unofficial slackware) Rock64 RK3328 (aarch64) - mara - 11-24-2020

update:
slarm64-current-aarch64-base-rootfs-20201115-4.4.246-rock64-build-20201124.img.zst
slarm64-current-aarch64-base-rootfs-20201115-4.4.246-rock64-build-20201124.img.zst.sha256
slarm64-current-aarch64-xfce-rootfs-20201115-4.4.246-rock64-build-20201124.img.zst
slarm64-current-aarch64-xfce-rootfs-20201115-4.4.246-rock64-build-20201124.img.zst.sha256

@Enig123,
in this image I added missing libraries to nslookup.

RE: slarm64 (unofficial slackware) Rock64 RK3328 (aarch64) - Enig123 - 11-24-2020

(11-24-2020, 03:44 PM)mara Wrote: update:
slarm64-current-aarch64-base-rootfs-20201115-4.4.246-rock64-build-20201124.img.zst
slarm64-current-aarch64-base-rootfs-20201115-4.4.246-rock64-build-20201124.img.zst.sha256
slarm64-current-aarch64-xfce-rootfs-20201115-4.4.246-rock64-build-20201124.img.zst
slarm64-current-aarch64-xfce-rootfs-20201115-4.4.246-rock64-build-20201124.img.zst.sha256

@Enig123,
in this image I added missing libraries to nslookup.
Thanks.

Do I have to do it from scratch or is there a way to upgrade from last version?

And, how about the development setup issue?

Edit: Well, I just tried another time to setup development environment with the new image. It's not there yet.
Not only gcc has the same shared libraries (libisl.so.23 for example) error, git also has similar error, while it showed to be libnghttp2.so.14 instead.

I will be very appreciated if you guys can fix these errors and make this already great distribution even ready-er.

RE: slarm64 (unofficial slackware) Rock64 RK3328 (aarch64) - mara - 11-25-2020

(11-24-2020, 04:46 PM)Enig123 Wrote: Do I have to do it from scratch or is there a way to upgrade from last version?

And, how about the development setup issue?

Edit: Well, I just tried another time to setup development environment with the new image. It's not there yet.
Not only gcc has the same shared libraries (libisl.so.23 for example) error, git also has similar error, while it showed to be libnghttp2.so.14 instead.

I will be very appreciated if you guys can fix these errors and make this already great distribution even ready-er.

using a new image, yes.

install
l/isl-0.23-aarch64-1.txz
n/nghttp2-1.41.0-aarch64-1.txz

these are not distribution errors, this is dependency management, which in this distribution lies on the shoulders of the user.