@shann, I'm currently not at home. Going to check tomorrow on a 15yo test computer.
>Publish comment on current with 4.19.294 kernel :)
Nice)
So latest glibc, gcc 6.x and LTS kernel 4.19.x are going to be our current base system?
@shann, I'm currently not at home. Going to check tomorrow on a 15yo test computer.
>Publish comment on current with 4.19.294 kernel :)
Nice)
So latest glibc, gcc 6.x and LTS kernel 4.19.x are going to be our current base system?
At case, remain most packages to builds (4630), only 1267 cooked (~21% of repo).
Always remain midori / webkit, need to switch on 2.x webkit branch i think.
Of course, we can discuss about fix version of base system, at time we have :
* Binutils 2.37 (released in 2021)
* Linux API headers 3.16.55 (released in 2018) => wip switch to 4.19.x
* GCC 6.3.0 (released in 2016)
* Glibc 2.21 (released in 2015)
If tests are good enough to daily usage, we can be use it, polish version to ensure that core desktop as safe / stable.
Noted that openssl also need bump (1.0.2u, kernel and for support need to switch on 1.1.x).
And after continue on current to prepare next step to switch another toolchain, gcc 10.x, glibc 2.30 etc ...
For haproxy on front of SliTaz infrastructure vms, i have this running :
haproxy 2.x branch
glibc 2.31
openssl 1.1.1l
kernel 5.4.x (custom for kvm env)
based on my slitaz64-stuff (https://people.slitaz.org/~shann/slitaz64-stuff/repo/packages/unstable/), i note that don't push/sync last work.
>remain most packages to builds (4630)
There are lots of packages with close to zero users. And even less of them use SliTaz.
Also, there are many packages in our repos that are built, but not working cause of lacking files, dependencies or are improperly configured.
>Noted that openssl also need bump
I tried bumping to 1.1.1v and had about 3000 packages built with no problems. But that's with our stock gcc4.
Infact, you are right.
If i check my branch for vm front infra stuff, i have only 174 packages, include base + dev stuff.
For openssl, built not problem, just keep in mine that wget/curl/cacerts/python/git are really sad if not rebuild with new version when bump 1.0.x > 1.1.x :).
For night, i launch in new chroot env my cooklist for base / dev stuff (270 packages), but only current repo (without cooking fallback), that ensure use only new packages.
most of them work but i have miss deps and issue with one package :
For network issue, fault wifi adapter seem unstable (normally i disable power-save, but i think need tweak again)
grep "cook failed" /home/slitaz/6.0/chroot/home/slitaz/log/*
/home/slitaz/6.0/chroot/home/slitaz/log/expat.log.0:ERROR: cook failed
=> issue network to fetch src
/home/slitaz/6.0/chroot/home/slitaz/log/libcap-ng.log:ERROR: cook failed
=> issue network to fetch src
/home/slitaz/6.0/chroot/home/slitaz/log/libxml2.log.0:ERROR: cook failed
=> issue network to fetch src
/home/slitaz/6.0/chroot/home/slitaz/log/python-setuptools.log:ERROR: cook failed
=> issue network to fetch src/home/slitaz/6.0/chroot/home/slitaz/log/linld.log:ERROR: missing 4 dependenciesERROR: cook failed
=> need ucl-dev / upx/home/slitaz/6.0/chroot/home/slitaz/log/perl.log:ERROR: cook failed
=> bump to 5.24.4 / use .tar.gz extension / patch for 5.24.4/home/slitaz/6.0/chroot/home/slitaz/log/busybox.log:ERROR: missing 6 dependenciesERROR: cook failed
=> need uclibc-cross-compiler-i486, musl-libc-dev, dietlibc/home/slitaz/6.0/chroot/home/slitaz/log/cacerts.log:ERROR: missing 2 dependenciesERROR: cook failed
=> need locale-en (that required himself slitaz-i18n)/home/slitaz/6.0/chroot/home/slitaz/log/linux.log:ERROR: missing 8 dependenciesERROR: cook failed
=> need uclibc-cross-compiler-x86_64, bc, libwrap/home/slitaz/6.0/chroot/home/slitaz/log/slitaz-configs.log:ERROR: missing 12 dependenciesERROR: cook failed
=> need locale-* (that required himself slitaz-i18n)/home/slitaz/6.0/chroot/home/slitaz/log/syslinux.log:ERROR: missing 4 dependenciesERROR: cook failed
=> need mingw32-gcc
mingw32-binutils
mingw32-runtime-headers
mingw32-w32api-headers
mingw32-gcc-c
mingw32-runtime
mingw32-w32api
For perl, i fix it, for missing deps (bc, libwrap, ucl, upx) build ok, need check for uclibc, musl, dietlibc and also mingw32 part for syslibux.
Hi
I put kernel and rootfs here https://people.slitaz.org/~shann/slitaz-current-stuff/current_20230909/
Need update linux receipts to have 4.19.294 and aufs (aufs4 branch) in repo :).
>aufs patchset
One idea for some distant future - maybe look at overlayfs, that's included in the kernel with no external patches.
Hi devl547,
For aufs you are right, it's on my todo to switch on overlayfs :).
At time, all stuff for cook based on it and implied rework cookutils, why i keep it for moment.
I launch kernel build, (skip x86_64 for moment, for 4.x, we need cross toolchain, issue with uclibc prebuilt).
build kernel 4.19.294 ok, but need tweak receipts for modules.
Infact few now included (acpi/video acpi/button, ...), other become mainline instead staging (usbip, rt8192ee, ...)
@shann
>slitaz-current-20230903.iso work as expected
Works correctly, no problem booting.
End training class for today :).
Hmm thanks for answer, iso can do with syslinux work, need check if when i build iso with cookiso, syslinux is not old version.
@devl547
I put new iso with syslinux build, i see that forget to set iso as hybrid :).
Now it's ok, new isos pushed https://people.slitaz.org/~shann/slitaz-current-stuff/new_isos/
For kernel, i relaunch build,
in case of modules i see :
linux-wireless, r8192ee and rtl8821ae now mainline (crystalhd removed)
linux-kvm, lguest module removed since 4.14
for linux-sound, after build linux, seem missing firmware folder.
I go to check and adjust next receipt for firmware, i used linux config that i bump to 4.19 (come from 4.14)
Hi,
Yesterday i continue adjust kernel config to have all modules need, and adjust modules.list with right path of modules (staging to mainline, subpath for usb udc device, etc.)
also adjust usbip receipt (staging to mainline), and tweak linux receipt to avoid try to cook linux64 modules if "--nox64" is set.
By default no condition set and try build all wanted linux including linux64-*.
>Now it's ok, new isos pushed
Checked, core iso works correctly. But the size >_>
Looks like we need to do something with libwebkit and all other big stuff. Waiting to get my hands dirty)
For size, i check with slitaz-rolling-5in1.
Decompressed in ram same size ~230M, diff i see compress rootfs.gz, in my case i used gzip -9 to repack rootfs.gz when i add packages midori/webkit, rolling use lzma.
You must log in to post.