SliTaz Forum
You are not logged in.
Hi,
I continue to work to build Xorg stuff and apps (upgrade apache to 2.4 for work with openssl 1.1.1n, required for cups, ...).
But i have a question about usage SliTaz 4.0 / rolling.
Infact it's great to see that successfull upgrade stack step by step (gcc remain old version for moment) and begin rebuild 4.0 packages work (bump when necessary).
I think maybe good idea to create "frozen point" of cooking and do same stuff.
I don't vision if my stuff to try upgrade 4.0 base is lost time and need focus on other way to try upgrade cooking with frozen point.
Regards,
Shann
Offline
@Shann
I think maybe good idea to create "frozen point" of cooking and do same stuff.
good idea.
Offline
@Shann,
Great!
Offline
Hi,
first stone to road 6.x 
https://hg.slitaz.org/wok-6.x
I go to begin rebuild base stuff, at first step by step before launch cooker.
Infact i think have same issue with 4.x (fuse issue with new glibc, segfault for grub4dos with gcc, ...)
Offline
A wok (that is now available with https://hg.slitaz.org/wok-6.x/) is an important requirement
to enable the collaboration of other package maintainers for a fully 64 bit-capable Slitaz.
For Stanislas Leduc (alias Shann) not to have to start from scratch again,
this wok should, if possible, make use of the recipes which Nils Christiansen (alias Filou)
has already made for the creation of 64 bit packages.
Furthermore, it is necessary to have a cooker, that can create packages from them,
which are then stored in a public package repository (https://packages.slitaz.org/)
and can thus be used to create further packages.
It would be advantageous to support the recipe format 2 used by Aleksej Bobylev at
https://cook.slitaz.org/next64/wok-next64, because this makes it possible to
create a package and related packages (...-dev, ...-lang ,...) with just one recipe.
For package maintainers to test new 64 bit-capable packages locally first, before they
transfer the recipe to the wok https://hg.slitaz.org/wok-6.x/, it would be useful,
to have a (generated weekly automatically) bootable ISO image available with
the current development status.
This must be accompanied by a warning that it should not be used for productive applications
but is intended exclusively for package adaptations.
These measures would integrate the efforts that have already been made and
pave the way for a fully 64-bit capable Slitaz.
Offline
Hi HGT,
In case you are right, we have dispersed effort.
Alanyih, Aleksej, first devs to work on x86_64 versions, me and Filou work each x86 and x86_64 version.
Need global discussion with maintainers, but we can maybe use Filou wok to begin work on next release 6.0 (if remember he have based on LFS 11.2 to follow apps version).
Offline
I try to create chroot env from filou repository to check if we can have env on tank :
On vm with cooking i follow this steps :
- Fetch 13 packages, chroot_pkgs and deps (busybox, cookutils, slitaz-base-files, lzma, tazpkg)
=> tazpkg missing, i pick it from cooking repo
- Create chroot env manually with tazpkg -i --root=/path_chroot_env (i disable tazpkg auto_deps to avoid fetch from cooking repo)
In new chroot launch cook setup but notice most packages missing :
[c]
root@slitaz:~# chroot /home/slitaz/cooking64/chroot
root@slitaz:/# cook setup
Setting up your environment
===========================================================================================================================================================================================================
Creating directories structure in "/home/slitaz"
Creating DB files in "/home/slitaz/cache"
Checking for packages to install...
Unable to find package "slitaz-toolchain" in the mirrored packages list.
Unable to find package "get-slitaz-toolchain" in the mirrored packages list.
Unable to find package "slitaz-toolchain" in the extra packages list.
Unable to find package "aufs-utils" in the mirrored packages list.
Unable to find package "get-aufs-utils" in the mirrored packages list.
Unable to find package "aufs-utils" in the extra packages list.
Unable to find package "aufs" in the mirrored packages list.
Unable to find package "get-aufs" in the mirrored packages list.
Unable to find package "aufs" in the extra packages list.
Unable to find package "syslinux-extra" in the mirrored packages list.
Unable to find package "get-syslinux-extra" in the mirrored packages list.
Unable to find package "syslinux-extra" in the extra packages list.
Unable to find package "mercurial" in the mirrored packages list.
Unable to find package "get-mercurial" in the mirrored packages list.
Unable to find package "mercurial" in the extra packages list.
md5sum: can't open 'rsync-3.2.7-x86_64.tazpkg': No such file or directory
Checksum error for "rsync-3.2.7-x86_64.tazpkg"
rm: can't remove 'rsync-3.2.7-x86_64.tazpkg': No such file or directory
Recharging repository "Main"
===========================================================================================================================================================================================================
Checking... Failed
Creating backup of the last packages list... Done
Getting "bundle.tar.lzma"... Failed
Restoring database files... Done
===========================================================================================================================================================================================================
Recharging failed
md5sum: can't open 'rsync-3.2.7-x86_64.tazpkg': No such file or directory
Checksum error for "rsync-3.2.7-x86_64.tazpkg"
rm: can't remove 'rsync-3.2.7-x86_64.tazpkg': No such file or directory
Please wait until the mirror synchronization is complete and try again.
md5sum: can't open 'dropbear-2022.82-x86_64.tazpkg': No such file or directory
Checksum error for "dropbear-2022.82-x86_64.tazpkg"
rm: can't remove 'dropbear-2022.82-x86_64.tazpkg': No such file or directory
Recharging repository "Main"
===========================================================================================================================================================================================================
Checking... Failed
Creating backup of the last packages list... Done
Getting "bundle.tar.lzma"... Failed
Restoring database files... Done
===========================================================================================================================================================================================================
Recharging failed
md5sum: can't open 'dropbear-2022.82-x86_64.tazpkg': No such file or directory
Checksum error for "dropbear-2022.82-x86_64.tazpkg"
rm: can't remove 'dropbear-2022.82-x86_64.tazpkg': No such file or directory
Please wait until the mirror synchronization is complete and try again.
md5sum: can't open 'tazlito-529-x86_64.tazpkg': No such file or directory
Checksum error for "tazlito-529-x86_64.tazpkg"
rm: can't remove 'tazlito-529-x86_64.tazpkg': No such file or directory
Recharging repository "Main"
===========================================================================================================================================================================================================
Checking... Failed
Creating backup of the last packages list... Done
Getting "bundle.tar.lzma"... Failed
Restoring database files... Done
===========================================================================================================================================================================================================
Recharging failed
md5sum: can't open 'tazlito-529-x86_64.tazpkg': No such file or directory
Checksum error for "tazlito-529-x86_64.tazpkg"
rm: can't remove 'tazlito-529-x86_64.tazpkg': No such file or directory
Please wait until the mirror synchronization is complete and try again.
Setting permissions for group "slitaz"...
===========================================================================================================================================================================================================
All done, ready to cook packages :-)
[/c]
Offline
Hi,
I setup fresh env in tank.
https://cook.slitaz.org/current/ linked to https://hg.slitaz.org/wok-current
Why "current" name, goal is infact to provide stable version, but in case we push new toolchain, upgrade packages, i think "current" naming more appropriate.
Offline
Hi,
I push new toolchain gcc 4.9.2 / glibc 2.19, bump glibc to 2.21.
Also manually fix issue with gcc83-lib-base installed on chroot that clash when build glibc package.
[c]Inconsistency detected by ld.so: get-dynamic-info.h: 134: elf_get_dynamic_info:
Assertion `info[15] == ((void *)0)' failed![/c]
On my local current chroot, i bump gcc 6.3.0 and rebuild toolchain, after toolchain done, i begin to rebuild base packages for check consistency before push.
Offline
Issue with glibc 2.21 and gcc 6.3.
setenv.c: In function '__unsetenv':
setenv.c:270:6: error: suggest explicit braces to avoid ambiguous 'else' [-Werror=parentheses]
if (ep != NULL)
^
cc1: all warnings being treated as errors
Found related and patch available https://bugzilla.redhat.com/show_bug.cgi?id=1312963
Toolchain rebuild, wait finish.
Offline
patch again glibc to build with gcc 6.
# Fix a bug that prevents Glibc from building with GCC-6.3.0
# https://bugzilla.redhat.com/show_bug.cgi?id=1312963 (-Werror=parentheses)
# https://sourceware.org/pipermail/libc-alpha/2015-April/059886.html (array-bounds)
patch -p1 -i $stuff/glibc-2.21-gcc6_fix-1.patch
# https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68024 (patch for style-definition)
patch -p1 -i $stuff/glibc-2.21-gcc6_fix-2.patch
# https://gcc.gnu.org/legacy-ml/gcc-patches/2015-11/msg00105.html
patch -p1 -i $stuff/glibc-2.21-gcc6_fix-3.patch
Build again, hope no others need patchs
Offline
After patch again glibc for unused const variable, build work.
# Fix unused const variable
sed -i 's|static const float one=1.0;|static const float __attribute__ ((unused)) one=1.0;|' \
sysdeps/ieee754/flt-32/s_cosf.c
sed -i 's|static const char rcsid\[\] =|static const char __attribute__ ((unused)) rcsid\[\]
' \
resolv/base64.c
Toolchain rebuild in progress, and after go for mass rebuild of base packages
Offline
I strange issue with cook autoconf 2.71.
Stack GCC 6.3.0 / Glibc 2.21 / Binutils 2.37
) | LC_ALL=C sort >>lib/autoscan/autoscan.list
autom4te: error: cannot create /tmp/am4tjFzyfo in /home/slitaz/wok/autoconf/source/autoconf-2.71: File exists
make[1]: *** [Makefile:2259: tests/wrapper.in] Error 1
make[1]: *** Waiting for unfinished jobs....
autom4te: error: cannot create /tmp/am4tdyBqFe in /home/slitaz/wok/autoconf/source/autoconf-2.71: File exists
make[1]: Leaving directory '/home/slitaz/wok/autoconf/source/autoconf-2.71'
make: *** [Makefile:928: all] Error 2
ERROR: cook failed
no issue when cook autoconf 2.69 or 2.70
Edit: i test in env with previous build (glibc 2.19 / gcc 4.9.2) same issue, work when i fallback perl previous build (5.14.1).
Suspect issue with my perl build, with glibc 2.21 / gcc 6.3.0, work with perl previous pkg
Edit: with build of perl 5.24.1 it's work think issue with new toolchain and old perl version
Offline
I build most packages of my base cooklist :
zlib
zlib-dev
ncurses
ncurses-common
ncurses-extra
ncurses-dev
ncursesw
ncursesw-extra
ncursesw-dev
ncurses-examples
texinfo
binutils
m4
gmp
gmp-dev
bison
flex
xz
liblzma
liblzma-dev
mpfr
mpfr-dev
bzip2
bzip2-dev
bzlib
elfutils
elfutils-dev
mpc-library
gawk
gcc
gcc-lib-base
gcc-lib-math
gfortran
libgfortran
libgomp
libobjc
readline
readline-dev
pcre
pcre-dev
db
libdb
db-dev
gdbm
gdbm-dev
less
tcl
tcl-dev
perl
microperl
openssl
libssl
libcrypto
libcrypto-dev
openssl-dev
cacerts
sqlite
libsqlite
libsqlite-tcl
sqlite-dev
libffi
libffi-dev
libidn
libidn-lang
libidn-dev
autoconf
automake
libtool
gperf
pam
pam-dev
bash
attr
attr-dev
acl
acl-dev
libcap
libcap-dev
python
python-dev
coreutils
libcap-ng
libcap-ng-dev
file
libmagic-dev
libmagic
util-linux
util-linux-uuid
util-linux-uuid-dev
util-linux-blkid
util-linux-blkid-dev
util-linux-mount
util-linux-mount-dev
util-linux-fdisk
util-linux-fdisk-dev
util-linux-smartcols
util-linux-smartcols-dev
wget
wget-lang
tar
tar-lang
libxml2
libxml2-python
libxml2-dev
libxml2-tools
expat
expat-dev
libgpg-error
libgpg-error-dev
libgcrypt
libgcrypt-dev
libtasn1
libtasn1-dev
libunistring
libunistring-dev
nettle
nettle-dev
gnutls
gnutls-dev
libgnutls
curl
libcurl
curl-dev
Remain half other part.
Offline
Successfully rebuild list, 377 packages.
Now need check that work as expected before push in wok-current.
Summary of changes due of introduce GCC 6.3.0 :
- remove loop of gettext build (attr need gettext to build that himself required attr-dev)
- remove libcroco as bdep of gettext (unmaintained)
- update receipt has need to use gcc 6.3.0, also change few receipts (back to gcc instead gcc83)
At time i put stuff packages/wok on my space :
https://people.slitaz.org/~shann/slitaz-current-stuff/packages
https://people.slitaz.org/~shann/slitaz-current-stuff/wok
Offline
Hi,
Test packages on rolling, except issue with grub4dos (cf https://forum.slitaz.org/topic/grub4dos-seem-break-on-rolling-20230430 ), desktop, apps seem work correctly after upgrade install rolling.
Offline
Hi,
Rebuild base packages, i create and push them on mirror in current folder.
https://mirror.slitaz.org/packages/current/
Need to add cron tasks for push them automatically, check to build isos.
Offline
Apply 4 patchs (2 for usbip and 2 last for linux kernel himself) :
linux-usbip-fix-format-overflow-gcc8.patch
linux-usbip-fix-implicit-fallthrough-gcc8.patch
linux-fix-format-overflow-gcc8.patch
linux-fix-noreturn-attributes-gcc8.patch
With this, i successfully building kernel but need test it on real environment to ensure sanity.
Infact i notice warnings about array-bounds / attribute-alias
Offline
Hi,
After test, i issue with build broadcom-wl, not sure if relate of gcc 8 or linux build.
Prefer ensure sanity of kernel build and rollback toolchain with gcc 6.3.0.
I think bump gcc to 8.3.0 implies bump to 4.x kernel branch.
Offline
@shann, is there anything I can help you with?
Offline
Hi devl547
I just finish to build xorg stack, not all packages but base with synaptics, vesa / fbdev.
Need also check for prepare iso with "current" repo, to test easy.
Road is long, doing step by step, upgrade cooking imply it (toolchain, kernel, xorg, openssl).
Each step can broken part, i hope that doing base > justx > gtk ensure sanity and not silent break.
See with gcc 6, base ok but xorg break (need patch for work).
At time for test i'm using rolling iso, and put current mirror to upgrade (test in base, justx flavor).
Just keep warn about tazpkg need upgrade first to upgrade in right way glibc/gcc-lib-base
Offline
[ Generated in 0.032 seconds, 7 queries executed - Memory usage: 1.62 MiB (Peak: 1.77 MiB) ]