SliTaz Forum
You are not logged in.
Wow, great job, shann.
So we gonna have a SliTaz 4.0 with upgraded toolchain and libs?
I stopped contributing to the project a couple of years ago cause of outdated gcc/glibc/etc and being unable to compile latest software versions.
Offline
Hi enigma9o7, devl547,
For moment iso compose only base and toolchain stuff (167 packages)
I need recompile kernel, infact vm host used 3.16.55 x64, but on chroot i use more recent linux-api-headers and glibc 
(need to keep .config small as possible without enabled all new options).
devl547, yes goal it's provide 4.0 with recent toolchain / libs.
latest iso i provide slitaz-4.0-basedev-20220506.iso, it's base upon binutils 2.36.1 / gcc 10.2.0 / glibc 2.19.
With backward compat of glibc, packages in 4.0 seem work, just for test .
I follow LFS 10.1 packages version, goal it's to have binutils 2.36.1 / gcc 10.2.0 / glibc 2.33.
this ugprade toolchain involves bump version (kernel > 3.2, few new deps).
I very pay attention of new dependencies introduce (avoid dependency hell).
This is my roadmap :
Milestone 1 :
base iso with new toolchain stuff work
Milestone 2 :
justx iso work
=> For this step, i hope that gtk and graphical stuff work without big bump need.
Milestone 3 :
gtkonly iso work
Milestone 4 :
core iso work
Offline
I put iso with kernel 5.4.193-vm (minimal stuff only work on vm)
https://people.slitaz.org/~shann/slitaz-4.0-stuff/slitaz-4.0-basedev-20220513.iso
not finish for final toolchain, remain 5 releases to go on 2.33.
For kernel i check to have 5.4 with 3.16 config
Offline
Hi,
Milestone 1 :
base iso with new toolchain stuff work
Milestone 2 :
justx iso work
Milestone 3 :
gtkonly iso work
Milestone 4 :
core iso work
Great!
You are right.
SliTaz style - KISS
keep in simple and stupid
Offline
Hi,
I need to ensure sanity toolchain, when i try to build glibc 2.32 or 2.33, binutils broken and complain about more .h file 'WARNING: argz.h: present but cannot be compiled' and finish cook error with
[c]./config.h:568:15: error: two or more data types in declaration specifiers
./config.h:571:17: error: two or more data types in declaration specifiers[/c]
broken gcc second pass also.
Offline
https://www.gnu.org/software/gnulib/manual/html_node/argz_002eh.html
Offline
thanks,
complain about :
argz.h
limits.h
locale.h
nl_types.h
malloc.h
stddef.h
time.h
sys/param.h
wchar.h
fcntl.h
...
I begin check and maybe issue about autoconf, but it's very strange.
with glibc-2.30 no problem, with glibc >, failed systematically 
I bump autoconf to 2.71 (same as LFS 10.1), but error again.
The main error seem about "two or more data types in declaration specifiers",
seem https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94089 good trace
Offline
Strange, I have no errors on local compilation in glibc-2.32
https://pastebin.com/AS6fcgtF
Offline
Hi,
In case no problem in glibc compilation, it's after glibc compiled
binutils "first pass" ok
gcc first pass ok
glibc (locale,extra-samba,base,dev) ok
binutils "second pass" failed
gcc second pass failed 'due of binutils previous failed'
But with glibc-2.30 all step work.
Offline
seem https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94089 good trace
Try:
Comment 1
If you use a gcc with a different glibc, you need to rerun fixincludes. Fixincludes is installed too.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94089#c1
or
# Do not run fixincludes
sed -i 's@\./fixinc\.sh@-c true@' gcc/Makefile.in
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=gcc10#n43
Offline
Hi,
thanks alanyih, i follow Arch fix about not run fixincludes, binutils/gcc pass1 ok, glibc 2.32 ok, binutils pass2 it's now ok, gcc pass2 in progress .
I relaunch cook toolchain again to ensure that sanity (build time ~50 mns) before mass rebuild.
Offline
Offline
I put iso in space
https://people.slitaz.org/~shann/slitaz-4.0-stuff/slitaz-4.0-basedev-20220518.iso
https://people.slitaz.org/~shann/slitaz-4.0-stuff/toolchain_20220518/wok
https://people.slitaz.org/~shann/slitaz-4.0-stuff/toolchain_20220518/packages
(i also push packages repo files)
Warn, kernel it's 5.4.193 minimal work only on vm (disk isci, e1000/virtio net).
Install sucessfully
tux@slitaz:~$ uname -a
Linux slitaz 5.4.193-vm #1 SMP Sat May 14 22:51:11 CEST 2022 i686 GNU/Linux
tux@slitaz:~$ free -m
total used free shared buff/cache available
Mem: 2026 10 2011 0 3 1969
Swap: 0 0 0
tux@slitaz:~$ tazpkg -l
List of all installed packages
===============================================================================================================================================================================================
acl 2.2.53 system-tools
attr 2.4.48 system-tools
busybox 1.31.1 base-system
bzlib 1.0.8 utilities
cacerts 20211107 security
cdrkit 1.1.11 utilities
depmod 3.12 base-system
dialog 1.1-20110707 base-system
dropbear 2022.82 security
e2fsprogs 1.46.1 base-system
gcc-lib-base 10.2.0 development
gdbm 1.19 misc
gettext-base 0.21 base-system
glibc-base 2.33 base-system
glibc-extra-samba 2.33 base-system
glibc-locale 2.33 system-tools
grub4dos-linux 0.4.4 system-tools
kbd-base 2.2.0 base-system
kmod 28 base-system
libcap 2.48 system-tools
libcomerr 1.46.1 base-system
libcrypto 1.1.1n security
libdb 4.8.26 misc
liblzma 5.2.5 misc
libssl 1.1.1n development
libtaz 1.6 base-system
lzlib 4.57 base-system
lzma 4.57 base-system
ncurses-common 6.3 base-system
ncursesw 6.3 base-system
openssl 1.1.1n security
perl 5.32.1 development
popt 1.16 system-tools
rsync 3.1.3 network
slitaz-base-files 4.6 base-system
slitaz-boot-scripts 4.7.2 base-system
slitaz-configs-base 4.9.2 base-system
slitaz-tools 4.9.1 system-tools
tazdev 1.6 development
tazlito 4.6.2 base-system
tazpkg 5.3.3 base-system
util-linux-ng-blkid 2.36.2 base-system
util-linux-ng-mount 2.36.2 base-system
util-linux-ng-uuid 2.36.2 base-system
zlib 1.2.11 base-system
===============================================================================================================================================================================================
45 packages installed.
tux@slitaz:~$
I go to work on kernel for real hardware
Offline
Yeah! I just gave your new ISO a spin and what I could see from the boot screen whizzing past, everything looked perfectly normal. There were no error messages. But then, alas, it got stuck in the language configuration and wouldn't respond to any keyboard action. Since I'm using a USB keyboard... is it possible the hardware isn't supported at this stage? I think, we still have an old PS/2 keyboard somewhere. If I can find it, I will try this tomorrow.
Offline
Hi,
Thanks Darjeeling for test, infact kernel 5.4 i build very small and only work in vm, i plan today to add kernel 3.16.55 from cooking it's now case.
This step to wait that build 5.4 with 3.16 config without default options with oldconfig.
i used directly packages, receipt 3.16.55 complain about aufs, linux-aufs, ... circulars dependencies, need check and fix them .
Thanks on-call to ring at 4:00 AM ^^
Iso update on my space, and i move previous iso to reflect usage :
https://people.slitaz.org/~shann/slitaz-4.0-stuff/slitaz-4.1-basedev-20220519.iso with both kernel 5.4 and 3.16 (choice on isolinux for kernel)
I install 3.16.55 only without other stuff (agp, drm, ...)
https://people.slitaz.org/~shann/slitaz-4.0-stuff/slitaz-4.0-basedev-20220518_kvmonly.iso with kernel 5.4 vm only
Yesterday i buying computer i have in 2010 (dell latitude x300), pentium M 1.2Ghz, 1Go RAM (max support), for real bench.
If i remember, i donate own to my cousin that need.
Offline
To keep info when i try tazinst with both kernel, seem issue about kernel installed.
I boot iso with 3.16.55 but tazinst put 5.4.193-vm inside /boot folder instead of 3.16.55 because it's first found on /lib/modules .
tux@slitaz:~$ uname -a
Linux slitaz 3.16.55-slitaz #4 SMP Mon Dec 6 13:01:40 UTC 2021 i686 GNU/Linux
tux@slitaz:~$ df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 9.8G 124.2M 9.1G 1% /
tmpfs 1011.4M 0 1011.4M 0% /dev/shm
tux@slitaz:~$ free -m
total used free shared buff/cache available
Mem: 2022 9 1997 0 15 2000
Swap: 0 0 0
tux@slitaz:~$ tazpkg -l |grep glibc
glibc-base 2.33 base-system
glibc-extra-samba 2.33 base-system
glibc-locale 2.33 system-tools
tux@slitaz:~$
Offline
Hi, on toshiba satellite pro notebook with core duo and with kernel 3.16 everything seems to be smooth. With kernel 5.4 it only boots live with initrd but does not detect any hard drives.
Offline
Hi gibor,
thanks, nice to read that.
Infact 5.4 not ready for real hardware, i think better i remove them on and create 2 iso one with 3.16.55, can be used on vm/real hard, and other kvmonly with 5.4 at time .
Offline
I test upgrade my test-vm (previously bump with glibc 2.19 stuff in few week), just for see.
Due of new glibc, tazpkg up failed, upgrade pkgs without upgrade core libs.
Need boot from live, install glibc-base, gcc-lib-base, ... (base for new libs)
After done, i reboot, and system upgrade successfull 54 packages.
=> glibc 2.33 backward compat with 2.0-2.18, 2.22-2.33 (except 2.31), in case normally ugprade from 2.13 it's ok.
But tazpkg upgrade not improved; upgrade with tazint is more safe i think.
Slim work, login ok.
Xorg work, see openbox desktop, but pcmanfm/lxpanel failed, issue about "Attempt to unlock mutex that was not locked"
To achieve Milestone 1, remain to have kernel 5.4 work on real hard, and test, test
Offline
Playing with the latest iso: combined with the old version everything seems to work except tazpanel and the old problem with midori (tls hand shake)
Offline
I'm following this thread with a lot of enthusiasm, I've never seen so many admins, moderators and developers participating, this brings good hopes for a prosperous future for SliTaz.
"Main reason last year i purpose sponsor and host gracefully, i absolutely don't want to see the project die."
I thank you for all your effort and work on SliTaz, I also wouldn't want to see SliTaz on this sad DistroWatch list (https://distrowatch.com/search.php?ostype=All&category=All&origin=All&basedon=All¬basedon=None&desktop=All&architecture=All&package=All&rolling=All&isosize=All&netinstall=All&language=All&defaultinit=All&status=Discontinued#simple) of GNU/Linux distributions that have been discontinued.
If in the future you want more people to help "cook" packages for SliTaz, consider teaching people interested in learning, so more people can help with this volunteer work.
SliTaz could stop being a "rolling" GNU/Linux distribution, I don't know what the advantage of this is for SliTaz, especially given the current moment the distribution is going through. It would be much better to consider switching to a "stable" type.
Many thanks to all the people who keep SliTaz alive.
marcelocripe
(Original text in Brazilian Portuguese)
- - - - -
Eu estou acompanhando este tópico com muito entusiasmo, eu nunca vi tantos administradores, moderadores e desenvolvedores participando, isto trás boas esperanças de um futuro próspero ao SliTaz.
"Main reason last year i purpose sponsor and host gracefully, i absolutely don't want to see the project die."
Eu agradeço por todo o seu esforço e trabalho no SliTaz, eu também não gostaria de ver o SliTaz nesta triste lista do DistroWatch (https://distrowatch.com/search.php?ostype=All&category=All&origin=All&basedon=All¬basedon=None&desktop=All&architecture=All&package=All&rolling=All&isosize=All&netinstall=All&language=All&defaultinit=All&status=Discontinued#simple) de distribuições GNU/Linux que foram descontinuadas.
Se no futuro quiserem que mais pessoas ajudem a "cozinhar" pacotes para o SliTaz, considerem a possibilidade de ensinar as pessoas interessadas em aprender, desta forma mais pessoas poderão ajudar neste trabalho voluntário.
O SliTaz poderia deixar de ser uma distribuição GNU/Linux do tipo "rolling", eu não sei qual é a vantagem disto para o SliTaz, ainda mais pelo momento atual que a distribuição vem passando. Seria muito melhor considerar passar a ser do tipo "stable".
Muito obrigado a todas as pessoas que mantém o SliTaz vivo.
marcelocripe
(Texto original em idioma Português do Brasil)
Offline
Hi gibor,
oh wow great stuff .
For tazpanel, seem issue about symlink to /usr/bin/http_helper.sh point to /usr/lib/slitaz/httphelper.sh (doesn't exist), sorry it's my faulty when work and backport busybox receipt.
Go to check and fix them.
Also i see 404 Not found when launch tazpanel, update Exec= in /usr/share/applications/tazpanel.desktop to add index.cgi at end of line.
Seem strange that /etc/slitaz/httpd.conf is correct [c]I:index.cgi[/c] and [c]H:/var/www/tazpanel[/c] present.
Concerning midori i think about gnutls / glib-networking not yet upgraded.
Hi marcelorcipe,
Thanks for support, infact agree that rolling-release not really good for SliTaz, we need to keep on stable / cooking.
Stable => stable and usual version
target: all users
Cooking => next stable version in development
target: devs, advanced users, testers
For increase help and dev, you are right, we need to teaching them and i will do with pleasure.
Offline
I update toolchain_20220518 folder with packages update (busybox / tazpanel), and wok.
2 fix for tazpanel :
- sleep 1 in /etc/init.d/tazpanel for let keep time to write pidid in pidfile
- index.cgi in tazpanel.desktop
I rebuild your iso with packages updated
https://people.slitaz.org/~shann/slitaz-4.0-stuff/slitaz-4.1-mergedbasedev-20220520_1939.iso
I tested, and tazpanel work very well.
Offline
[ Generated in 0.019 seconds, 7 queries executed - Memory usage: 1.62 MiB (Peak: 1.77 MiB) ]
