SliTaz on Raspberry Pi 3

SliTaz Forum » English Support » Live and installation

SliTaz on Raspberry Pi 3

(12 posts) (2 voices)

Started 5 years ago by shann
Latest reply from shann
This topic is not a support question

Tags:

No tags yet.

shann

offline
Administrator
Hi,

I see that SliTaz not support on RPi 3, latest version support first version.

This week i building cross-toolchain for armv7-a (only RPi 3), on Debian x64 host.

Toolchain version :
Binutils : 2.31.1
GCC : 8.2.0
Glibc : 2.27
GMP : 6.1.2
MPFR : 4.0.1
MPC : 1.1.0
ISL : 0.18
CLOOG : 0.18.1

Now cross-toolchain is ready, next step to build from wok minimal stuff to boot SliTaz :D.

Best regards.
Attachments
cross_toolchain_slitaz.png (99.5 KB, 946 downloads) 5 years old
cross_toolchain_slitaz.png (77.5 KB, 541 downloads) 5 years old
Posted 5 years ago #

shann

offline

Administrator

First package cook :).

Summary for: busybox 1.29.2-armv7
================================================================================
Src file    : busybox-1.29.2.tar.bz2
Src size    : 2.2M
Source dir  : 45.6M
Produced    : 1.1M
Cook time   : 46s ~ 1m
Cook date   : 2018-08-07 08:56
Target arch : armv7
--------------------------------------------------------------------------------
 # :  Packed : Compressed : Files : Package name
--------------------------------------------------------------------------------
 1 :    1.1M :     460.1K :   408 : busybox-1.29.2-armv7.tazpkg
================================================================================

Posted 5 years ago #

shann

offline

Administrator

Hi,

Because i need bootstrap to build package, i use slitaz64 rootfs (old because use gcc 4.9.2 and glibc 2.19).
I try to create rootfs x64 from next64 :
- glibc-base contain lib64 empty dir, not used but cause failed when chroot inside rootfs (need to drop them)
- need create symlink "ln -s ./lib lib64" to chroot inside rootfs work
- When i try to install package from next64 repository

~ # tazpkg -gi make
md5sum: can't open 'make-4.2.1.tazpkg': No such file or directory
/usr/libexec/tazpkg/install: line 428: can't open /var/cache/tazpkg/next/packages/make-4.2.1.tazpkg: no such file
/usr/libexec/tazpkg/install: .: line 428: can't open './receipt'
realpath: /var/cache/tazpkg/next/packages/make-4.2.1.tazpkg: No such file or directory
/usr/libexec/tazpkg/install: line 446: can't open : no such file
/usr/libexec/tazpkg/install: .: line 446: can't open '/tmp/tmp.IKJxCs/receipt'
/usr/libexec/tazpkg/install: .: line 446: can't open '/tmp/tmp.IKJxCs/receipt.var'

Best regards,

Posted 5 years ago #

Aleksej

offline

Coder-hobbyist

Hi shann,

> ~ # tazpkg -gi make
> md5sum: can't open 'make-4.2.1.tazpkg': No such file or directory

Reference: http://cook.slitaz.org/next64/make

All the package files from the Next64 repository has "-x86_64" suffix, so package file for "make" is "make-4.2.1-x86_64.tazpkg".

Check your /etc/slitaz/slitaz.conf:

. . . . .

# SliTaz architecture.
SLITAZ_ARCH="x86_64"

. . . . .

------------------------------

> - glibc-base contain lib64 empty dir, not used but cause failed when chroot inside rootfs (need to drop them)

Reference: http://cook.slitaz.org/next64/glibc/files#glibc-base

/lib64/ directory isn't empty, it contains two very important symlinks without them any executable will work. For example:

root@slitaz:/home/slitaz/wok# ldd /bin/busybox
	linux-vdso.so.1 (0x00007ffd974b1000)
	libm.so.6 => /lib/libm.so.6 (0x00007fa291e4d000)
	libtirpc.so.3 => /lib/libtirpc.so.3 (0x00007fa29238a000)
	libc.so.6 => /lib/libc.so.6 (0x00007fa291aa4000)
	/lib64/ld-linux-x86-64.so.2 (0x00007fa292191000)
	libpthread.so.0 => /lib/libpthread.so.0 (0x00007fa291887000)
root@slitaz:/home/slitaz/wok# ldd /bin/xz
	linux-vdso.so.1 (0x00007ffd323cd000)
	liblzma.so.5 => /lib/liblzma.so.5 (0x00007fe76dc68000)
	libpthread.so.0 => /lib/libpthread.so.0 (0x00007fe76da4b000)
	libc.so.6 => /lib/libc.so.6 (0x00007fe76d6a2000)
	/lib64/ld-linux-x86-64.so.2 (0x00007fe76de81000)

These paths (/lib64/ld-linux-x86-64.so.2 and other one) are inside executable files:

root@slitaz:/home/slitaz/wok# readelf -l /bin/busybox 

Elf file type is EXEC (Executable file)
Entry point 0x408170
There are 8 program headers, starting at offset 64

Program Headers:
  Type           Offset             VirtAddr           PhysAddr
                 FileSiz            MemSiz              Flags  Align
  PHDR           0x0000000000000040 0x0000000000400040 0x0000000000400040
                 0x00000000000001c0 0x00000000000001c0  R E    0x8
  INTERP         0x0000000000000238 0x0000000000400238 0x0000000000400238
                 0x000000000000001c 0x000000000000001c  R      0x1
      [Requesting program interpreter: /lib64/ld-linux-x86-64.so.2]
  LOAD           0x0000000000000000 0x0000000000400000 0x0000000000400000
                 0x00000000000b71b4 0x00000000000b71b4  R E    0x200000
  LOAD           0x00000000000b7df0 0x00000000006b7df0 0x00000000006b7df0
                 0x00000000000010d2 0x00000000000018a8  RW     0x200000
  DYNAMIC        0x00000000000b7e00 0x00000000006b7e00 0x00000000006b7e00
                 0x00000000000001f0 0x00000000000001f0  RW     0x8
  NOTE           0x0000000000000254 0x0000000000400254 0x0000000000400254
                 0x0000000000000020 0x0000000000000020  R      0x4
  GNU_EH_FRAME   0x0000000000000000 0x0000000000000000 0x0000000000000000
                 0x0000000000000000 0x0000000000000000  R      0x8
  GNU_STACK      0x0000000000000000 0x0000000000000000 0x0000000000000000
                 0x0000000000000000 0x0000000000000000  RW     0x8

 Section to Segment mapping:
  Segment Sections...
   00
   01     .interp
   02     .interp .note.ABI-tag .hash .dynsym .dynstr .gnu.version .gnu.version_r .rela.dyn .rela.plt .init .plt .text .fini .rodata
   03     .init_array .fini_array .dynamic .got .got.plt .data .bss
   04     .dynamic
   05     .note.ABI-tag
   06
   07

Normally /lib64/ should contain only these two symlinks, please don't make mistake symlinking /lib64/ with /lib/. Of course you're free to make as you want, for example, Arch Linux symlinked all the /lib/, /usr/lib/, /lib64/, /usr/lib64/ into one.

Posted 5 years ago #

shann

offline
Administrator
Hi Aleksej,

Infact slitaz.conf SLITAZ_ARCH="i486" (i installed in rootfs slitaz-base-files-337-x86_64.tazpkg download from http://cook.slitaz.org/next64), i check package (slitaz.conf file indicate i486 arch instead )

For glibc, screen below, i downloaded also from cook, and lib64 folder is empty :/.
I create symlink only to check if work, but if not standard, i don't them.
Attachments
glibc_from_cook.png (81.1 KB, 767 downloads) 5 years old
Posted 5 years ago #
shann

offline
Administrator

Hum, i recheck inside chroot, package it's ok.
Seem that install "tazpkg" on my Debian false result, i extract package downloaded in chroot, and lib64 is empty (but good inside chroot) :(.

Posted 5 years ago #
shann

offline
Administrator

But i used glibc 2.27, and next64 use glibc 2.26, i think not work correctly :/.
I show in other thread, you prepare migrate next64 to use glibc 2.27 (but need to recompile all).

Posted 5 years ago #
Aleksej

offline
Coder-hobbyist

> Infact slitaz.conf SLITAZ_ARCH="i486"

Oh, you're right. It's the bug I've overlooked.
Fixed: http://hg.slitaz.org/wok-next/rev/20907

> i extract package downloaded in chroot, and lib64 is empty

I downloaded glibc-base from here: http://cook.slitaz.org/next64/glibc/download
and extracted it. Folder lib64/ is in place.

> For glibc, screen below

Can't understand how it can be. ls don't show the symlinks? Or required the absolute path or "./" at the begin of the relative path? Looks you haven't Midnight Commander or PCManFM on that box? You may use them also to check files existence...

> I show in other thread, you prepare migrate next64 to use glibc 2.27

Yes, I'll update it in the near days.

Posted 5 years ago #

shann

offline

Administrator

I check with mc, not symlinks present.
On my desktop, i open package and symlink is present.

Very strange on SliTaz Next 64 chroot same operation :

~ # tazpkg install glibc-base-2.26-x86_64.tazpkg  --root=rootfs

Recharging repository "Main"
======================================================================================================================================================================================
Checking...                                                                                                                                                                [ Done ]
Database timestamp: 07/29/18 19:31
Creating backup of the last packages list...                                                                                                                               [ Done ]
Getting "bundle.tar.lzma"...                                                                                                                                               [ Done ]
Getting "files-list.lzma"...                                                                                                                                               [ Done ]
======================================================================================================================================================================================
Last database is ready to use.

Note that next time you recharge the list, a list of differences will be displayed to show new and upgradeable packages.

/usr/libexec/tazpkg/install: line 428: can't open glibc-base-2.26-x86_64.tazpkg: no such file
/usr/libexec/tazpkg/install: .: line 428: can't open './receipt'

Installation of package "glibc-base"
======================================================================================================================================================================================
The GNU C libraries (minimal libraries and UTF-8 support for SliTaz)
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Copying package...                                                                                                                                                         [ Done ]
Extracting package...                                                                                                                                                      [ Done ]
Remember modified packages...                                                                                                                                              [ Done ]
Installing package...                                                                                                                                                      [ Done ]
Removing all tmp files...                                                                                                                                                  [ Done ]
grep: rootfs/var/lib/tazpkg/installed/glibc-base/receipt: No such file or directory
fgrep: rootfs/var/lib/tazpkg/installed/glibc-base/files.list: No such file or directory
fgrep: rootfs/var/lib/tazpkg/installed/glibc-base/files.list: No such file or directory
fgrep: rootfs/var/lib/tazpkg/installed/glibc-base/files.list: No such file or directory
fgrep: rootfs/var/lib/tazpkg/installed/glibc-base/files.list: No such file or directory
fgrep: rootfs/var/lib/tazpkg/installed/glibc-base/files.list: No such file or directory
fgrep: rootfs/var/lib/tazpkg/installed/glibc-base/files.list: No such file or directory
cp: can't stat 'rootfs/var/lib/tazpkg/installed/glibc-base/md5sum': No such file or directory
md5sum: can't open 'rootfs/var/lib/tazpkg/installed/glibc-base/receipt': No such file or directory
sed: rootfs/var/lib/tazpkg/installed.info: No such file or directory
/usr/libexec/tazpkg/install: line 12: can't create rootfs/var/lib/tazpkg/installed.info: nonexistent directory
sort: rootfs/var/lib/tazpkg/installed.info: No such file or directory
mv: can't rename '/tmp/tmp.iE1azM': No such file or directory
chmod: rootfs/var/lib/tazpkg/installed.info: No such file or directory
======================================================================================================================================================================================
Package "glibc-base" (2.26) is installed.

~ # ls glibc-base-2.26-x86_64/fs/ -l
total 16
drwxr-xr-x    2 root     root          4096 Aug 10 13:22 etc
drwxr-xr-x    2 root     root          4096 Aug 10 13:22 lib
drwxr-xr-x    2 root     root          4096 Aug 10 13:22 lib64
drwxr-xr-x    5 root     root          4096 Aug 10 13:22 usr
~ # ls glibc-base-2.26-x86_64/fs/lib64/ -l
total 0
lrwxrwxrwx    1 root     root            17 Aug 10 13:22 ld-linux-x86-64.so.2 -> ../lib/ld-2.26.so
lrwxrwxrwx    1 root     root            17 Aug 10 13:22 ld-lsb-x86-64.so.3 -> ../lib/ld-2.26.so

Great, for moment i can rebuild toolchain with 2.26 to check if build successful minimal packages for running :)

Posted 5 years ago #

shann

offline
Administrator

Hi Aleksej,

I will try to cook bzip2, seem site bzip.org has a gone way :/.

i used this website archive "https://fossies.org/linux/misc/bzip2-1.0.6.tar.gz/".

Best regards

Posted 5 years ago #
Aleksej

offline
Coder-hobbyist

Hi Stanislas,

I've read about bzip2 just yesterday: http://www.opennet.ru/opennews/art.shtml?num=49110 (in Russian) with the link to the original news: https://lwn.net/Articles/762264/ (in English).

Here we can see no additional source repositories across about 120 Linux distributions, but only bzip.org: https://repology.org/metapackage/bzip2/information

Thank you for the link!

Current versions of the source tarballs are stored on the SliTaz server. You can download bzip2 sources, for example, here: http://cook.slitaz.org/next64/bzip2/download

When (and if) bzip2 project will release the new version I hope we'll see it both with the new (or old) web site. And now I will change receipt to your link...

Posted 5 years ago #
shann

offline
Administrator
Hi Aleksej,

nothing, i show this and report them :).

I try to build tazpkg, seem depend libnotify that depend ...
When i try to build ncurses i have issue with tic and pc file :/
```
/cross/armv7/tools/lib/gcc/armv7-slitaz-linux-gnueabihf/7.3.0/../../../../armv7-slitaz-linux-gnueabihf/bin/ld: data size 9113600
cd /home/slitaz/wok/ncurses/install/usr/lib && (ln -s -f libncursesw.so.6.1 libncursesw.so.6; ln -s -f libncursesw.so.6 libncursesw.so; )
installing ../lib/libncursesw.a as /home/slitaz/wok/ncurses/install/usr/lib/libncursesw.a
/usr/bin/install -c -m 644 ../lib/libncursesw.a /home/slitaz/wok/ncurses/install/usr/lib/libncursesw.a
armv7-slitaz-linux-gnueabihf-ranlib /home/slitaz/wok/ncurses/install/usr/lib/libncursesw.a
make[1]: Leaving directory '/home/slitaz/wok/ncurses/source/ncurses-6.1/ncurses'
cd progs && make DESTDIR="/home/slitaz/wok/ncurses/install" RPATH_LIST="/usr/lib" install
make[1]: Entering directory '/home/slitaz/wok/ncurses/source/ncurses-6.1/progs'
mkdir -p /home/slitaz/wok/ncurses/install/usr/bin
/usr/bin/install -c -s tic     /home/slitaz/wok/ncurses/install/usr/bin/<code>echo tic|       sed 's/$//'|sed 's,x,x,'|sed 's/$//'</code>
strip: Unable to recognise the format of the input file
```
/home/slitaz/wok/ncurses/install/usr/bin/tic'
install: strip: No such file or directory
make[1]: *** [Makefile:201: install.progs] Error 1
make[1]: Leaving directory '/home/slitaz/wok/ncurses/source/ncurses-6.1/progs'
make: *** [Makefile:116: install] Error 2
ln: /home/slitaz/wok/ncurses/install/usr/lib/pkgconfig/ncurses.pc: No such file or directory
ln: /home/slitaz/wok/ncurses/install/usr/lib/pkgconfig/form.pc: No such file or directory
ln: /home/slitaz/wok/ncurses/install/usr/lib/pkgconfig/panel.pc: No such file or directory
ln: /home/slitaz/wok/ncurses/install/usr/lib/pkgconfig/menu.pc: No such file or directory
mv: can't rename '/home/slitaz/wok/ncurses/install/usr/share/terminfo/x/xterm': No such file or directory
mv: can't rename '/home/slitaz/wok/ncurses/install/usr/share/terminfo/x/xterm-256color': No such file or directory
/home/slitaz/wok/ncurses/install/usr/bin/tic: line 1: syntax error: unexpected word (expecting ")")
ln: /home/slitaz/wok/ncurses/install/usr/share/terminfo/x/xterm: No such file or directory
`

strip binary is include in binutils packages, but in receipt, both x86_64 or arm never indicate build_depends.
Posted 5 years ago #

RSS feed for this topic

Reply

You must log in to post.

SliTaz on Raspberry Pi 3

Attachments

Attachments

Reply