SliTaz SliTaz Forum

You are not logged in.

#576 2025-07-24 20:10:35

shann
Administrator
Registered: 2011-04-01
Posts: 1,296
Website

Re: [Current version (6.0) dev thread] - Usage of SliTaz 4.0 / rolling

I try to test something.

Ubuntu 20.04 have glibc 2.31, ubuntu 22.04 have glibc 2.35.

I fetch make and busybox from ubuntu 22.04, and test it on my chroot with glibc 2.34

root@slitaz:~# /lib/libc.so.6

GNU C Library (GNU libc) stable release version 2.34.

Copyright (C) 2021 Free Software Foundation, Inc.

This is free software; see the source for copying conditions.

There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A

PARTICULAR PURPOSE.

Compiled by GNU CC version 10.2.0.

libc ABIs: UNIQUE IFUNC ABSOLUTE

For bug reporting instructions, please see:

<https://www.gnu.org/software/libc/bugs.html>.

root@slitaz:~# ldd busybox_ubuntu

    linux-vdso.so.1 (0x00007ffe21985000)

    libresolv.so.2 => /lib/libresolv.so.2 (0x00007facd1e2a000)

    libc.so.6 => /lib/libc.so.6 (0x00007facd1c30000)

    /lib64/ld-linux-x86-64.so.2 (0x00007facd1ef1000)

root@slitaz:~# ldd make_ubuntu

    linux-vdso.so.1 (0x00007ffd05f27000)

    libc.so.6 => /lib/libc.so.6 (0x00007f4db94b6000)

    /lib64/ld-linux-x86-64.so.2 (0x00007f4db96f6000)

root@slitaz:~# ./make_ubuntu

Segmentation fault

root@slitaz:~# ./busybox_ubuntu | head -1

BusyBox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu3.1) multi-call binary.

I don't understand but busybox work and make failed ...

Offline

#577 2025-07-25 06:40:47

gibor
Moderator
Registered: 2011-04-30
Posts: 1,067

Re: [Current version (6.0) dev thread] - Usage of SliTaz 4.0 / rolling

I have differences with ldd from yours, particularly on references to libraries:

tux@slitaz:~$ ldd /usr/bin/make

        linux-vdso.so.1 (0x00007ffc1efb2000)

        libdl.so.2 => /lib/libdl.so.2 (0x00007f907534e000)

        libc.so.6 => /lib/libc.so.6 (0x00007f9075149000)

        /lib64/ld-linux-x86-64.so.2 (0x00007f9075355000)

tux@slitaz:~$ ldd /bin/busybox

        linux-vdso.so.1 (0x00007ffc6e543000)

        libm.so.6 => /lib/libm.so.6 (0x00007f2b8a24f000)

        libc.so.6 => /lib/libc.so.6 (0x00007f2b8a04a000)

        /lib64/ld-linux-x86-64.so.2 (0x00007f2b8a32d000)

Offline

#578 2025-07-25 06:46:59

shann
Administrator
Registered: 2011-04-01
Posts: 1,296
Website

Re: [Current version (6.0) dev thread] - Usage of SliTaz 4.0 / rolling

Hi gibor,

I think do test with old glibc 2.28 chroot to bump to 2.34.

Concerning diff ldd, i have a same as you for SliTaz binary, except libm for busybox smile

root@slitaz:/home/slitaz/wok# ldd /usr/bin/make

/bin/bash: warning: setlocale: LC_ALL: cannot change locale (fr_FR.UTF-8)

    linux-vdso.so.1 (0x00007ffec8514000)

    libdl.so.2 => /lib/libdl.so.2 (0x00007f76588da000)

    libc.so.6 => /lib/libc.so.6 (0x00007f7658722000)

    /lib64/ld-linux-x86-64.so.2 (0x00007f76588e1000)

root@slitaz:/home/slitaz/wok# ldd /bin/busybox

/bin/bash: warning: setlocale: LC_ALL: cannot change locale (fr_FR.UTF-8)

    linux-vdso.so.1 (0x00007ffd830de000)

    libc.so.6 => /lib/libc.so.6 (0x00007f7287f19000)

    /lib64/ld-linux-x86-64.so.2 (0x00007f72880d3000)

If your make binary with glibc 2.34 work, can you please put it as attachment ? For i test if work on my side without segfault

Offline

#579 2025-07-25 07:13:37

gibor
Moderator
Registered: 2011-04-30
Posts: 1,067

Re: [Current version (6.0) dev thread] - Usage of SliTaz 4.0 / rolling

I can't attach the binary file; the forum responds with the following message:

You need to actually submit some content!

Attachments

    [tar] [denied extension] make.tar (220 KB)

    [txt] [denied mime] make.txt (218.4 KB) 1 minute old

    [denied extension] make (218.4 KB) 1 minute old

edit: external link

https://disk.yandex.com/d/ZgBU0INPcTA6nA

Offline

#580 2025-07-25 07:59:52

shann
Administrator
Registered: 2011-04-01
Posts: 1,296
Website

Re: [Current version (6.0) dev thread] - Usage of SliTaz 4.0 / rolling

Thanks gibor.

Hmm really strange hmm

On chroot env with glibc 2.31 your make binary work, when i install glibc-base 2.34, stop it to work and segment fault.

root@slitaz:/# /tmp/make_gibor

make_gibor: *** No targets specified and no makefile found.  Stop.

root@slitaz:/# ldd /tmp/make_gibor

/bin/bash: warning: setlocale: LC_ALL: cannot change locale (fr_FR.UTF-8)

    linux-vdso.so.1 (0x00007ffc8f2ee000)

    libdl.so.2 => /lib/libdl.so.2 (0x00007f9313cbf000)

    libc.so.6 => /lib/libc.so.6 (0x00007f9313b02000)

    /lib64/ld-linux-x86-64.so.2 (0x00007f9313cc6000)

root@slitaz:/# tazpkg -i /home/slitaz/packages/glibc-base-2.34-x86_64.tazpkg --forced

Package "glibc-base" blocked.

root@slitaz:/# vi /var/lib/tazpkg/blocked-packages.list

root@slitaz:/# tazpkg -i /home/slitaz/packages/glibc-base-2.34-x86_64.tazpkg --forced

Installation of package "glibc-base"

==================================================================================================================

GNU libc minimal libraries and UTF-8 support for SliTaz.

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

Copying package...                                                                                     [ Done ]

Extracting package...                                                                                  [ Done ]

Remember modified packages...                                                                          [ Done ]

Execute pre-install commands...                                                                        [ Done ]

Installing package...                                                                                  [ Done ]

Removing all tmp files...                                                                              [ Done ]

==================================================================================================================

Package "glibc-base" (2.34) is installed.

root@slitaz:~# /tmp/make_gibor

Segmentation fault

root@slitaz:~# make

Segmentation fault

root@slitaz:~# cp -a glibc-base-2.31-x86_64/fs/* /

root@slitaz:~# make

make: *** No targets specified and no makefile found.  Stop.

root@slitaz:~# /tmp/make_gibor

make_gibor: *** No targets specified and no makefile found.  Stop.

Offline

#581 2025-07-25 08:57:00

shann
Administrator
Registered: 2011-04-01
Posts: 1,296
Website

Re: [Current version (6.0) dev thread] - Usage of SliTaz 4.0 / rolling

I would like do test after build temp cross tool follow LFS, seem not work on my another chroot env  but if i chroot on temporary system make seem work.

root@slitaz:/cross/x86_64/sources/make-4.3# chroot /cross/x86_64

I have no name!@slitaz:/# make

make: *** No targets specified and no makefile found.  Stop.

I have no name!@slitaz:/# exit

exit

root@slitaz:/cross/x86_64/sources/make-4.3#

root@slitaz:~# ./make_rebuild

./make_rebuild: /lib/libc.so.6: version `GLIBC_2.33' not found (required by ./make_rebuild)

./make_rebuild: /lib/libc.so.6: version `GLIBC_2.34' not found (required by ./make_rebuild)

root@slitaz:~# tazpkg -i /home/slitaz/packages/glibc-base-2.34-x86_64.tazpkg --forced

Installation of package "glibc-base"

==================================================================================================================

GNU libc minimal libraries and UTF-8 support for SliTaz.

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

Copying package...                                                                                     [ Done ]

Extracting package...                                                                                  [ Done ]

Remember modified packages...                                                                          [ Done ]

Execute pre-install commands...                                                                        [ Done ]

Installing package...                                                                                  [ Done ]

Removing all tmp files...                                                                              [ Done ]

==================================================================================================================

Package "glibc-base" (2.34) is installed.

root@slitaz:~# ./make_rebuild

Segmentation fault

root@slitaz:~# cp -a glibc-base-2.31-x86_64/fs/* /

root@slitaz:~# ./make_rebuild

./make_rebuild: /lib/libc.so.6: version `GLIBC_2.33' not found (required by ./make_rebuild)

./make_rebuild: /lib/libc.so.6: version `GLIBC_2.34' not found (required by ./make_rebuild)

Offline

#582 2025-07-25 09:03:46

shann
Administrator
Registered: 2011-04-01
Posts: 1,296
Website

Re: [Current version (6.0) dev thread] - Usage of SliTaz 4.0 / rolling

Interessting think.

If i copy libc.6 build with follow LFS cross tool, make happy and work.

=> Diff between build glibc 2.34 on my env and follow lfs, it's i didn't patch glibc 2.34.

In case maybe with patch i generate glibc in unstable state.

Offline

#583 2025-07-25 11:27:52

shann
Administrator
Registered: 2011-04-01
Posts: 1,296
Website

Re: [Current version (6.0) dev thread] - Usage of SliTaz 4.0 / rolling

Continue my checks.

I do something to ensure glibc sanity :

- Remove files on my current64_glibc233 env for glibc-base, glibc-locale and glibc-dev

- Copy files from /cross/x86_64 sysroot for each files.list to current64_glibc233

- Enter to current64_glibc233 env, programs seem continue to work.

- Test to build glibc 2.34 again to check.

I suspect clash between glibc 2.34 and remain glibc soname version (*-2.31.so*).

Infact since glibc 2.34, versionning solib don't exist, now libc.so.6 is not symlink to libc-2.34.so

Seem glibc build successfully, but test i do when i try to copy glibc-base files just compiled, segfault come back hmm

In case, maybe something wrong when build glibc or my toolchain broke glibc build

Offline

#584 2025-07-25 12:48:59

gibor
Moderator
Registered: 2011-04-30
Posts: 1,067

Re: [Current version (6.0) dev thread] - Usage of SliTaz 4.0 / rolling

After the make binary, do you want the folder containing the entire compiled glibc-2.34 for cross-testing?

It costs me nothing to upload it...

Offline

#585 2025-07-25 13:03:37

shann
Administrator
Registered: 2011-04-01
Posts: 1,296
Website

Re: [Current version (6.0) dev thread] - Usage of SliTaz 4.0 / rolling

No sure if necessary and help me to debug.

If i follow that i do

- gen slitaz current64 chroot env (glibc 2.31, binutils 2.37, gcc 8.3.0, linux api 5.10.238)

Inside chroot env, ensure have toolchain and necessary package to build temp lfs toolchain

- compile "cross temporary toolchain" follow LFS (glibc 2.34, binutils 2.37, gcc 10.2.0, linux api 5.10.238)

=> in case with slitaz-toolchain, i build successfully temporary toolchain include glibc 2.34.

=> inside "lfs chroot", temporary toolchain, libc and make binary work

- Remove glibc-base, glibc-locale, glibc-dev on glibc233 chroot and replace it with glibc 2.34

=> chroot seem continue to work and can build glibc 2.34 with wok but segfault when installed on chroot.

Just i do something and seem libc work :

Rebuild binutils without [c]--disable-initfini-array[/c], rebuild gcc,gcc-lib-*,libgomp,libobjc,*fortran packages, and rebuild glibc.

Leaving aufs chroot...

Updating x86_64 chroot environment...

Package "glibc-base" blocked.

root@slitaz:/home/slitaz/wok# make

make: *** No targets specified and no makefile found.  Stop.

root@slitaz:/home/slitaz/wok# cp -a glibc-base/taz/glibc-base-2.34/fs/* /

root@slitaz:/home/slitaz/wok# make

make: *** No targets specified and no makefile found.  Stop.

root@slitaz:/home/slitaz/wok# make

make: *** No targets specified and no makefile found.  Stop.

root@slitaz:/home/slitaz/wok# md5sum glibc/install/lib/libc.so.6 glibc-base/taz/glibc-base-2.34/fs/lib/libc.so.6 /

lib/libc.so.6

892f18d092c3cd695c475e189ab7e1ee  glibc/install/lib/libc.so.6

00a77647dc4fee3cbcd74a742fcb4209  glibc-base/taz/glibc-base-2.34/fs/lib/libc.so.6

00a77647dc4fee3cbcd74a742fcb4209  /lib/libc.so.6

(lfs chroot) root:/# md5sum /lib/libc.so.6

9cb09b5c64ffd2aa965da8e1ad6b4090  /lib/libc.so.6

Change i do for glibc receipt (also maybe add nss fix help)

root@slitaz:/home/slitaz/wok# hg diff glibc

diff -r 22f2b8a2ea08 glibc/receipt

--- a/glibc/receipt     Sun Jul 06 15:33:46 2025 +0000

+++ b/glibc/receipt     Fri Jul 25 13:06:27 2025 +0000

@@ -1,7 +1,7 @@

# SliTaz package receipt.

PACKAGE="glibc"

-VERSION="2.28"

+VERSION="2.34"

CATEGORY="meta"

SHORT_DESC="The GNU C libraries. This package is used to compile the libc."

MAINTAINER="pankso@slitaz.org"

@@ -79,86 +79,19 @@

                [ -d "/var/lib/tazpkg/installed/gawk" ] || tazpkg get-install gawk

        fi

-       # Make 4.x support...

-       sed -i 's/3\.79/4.* | &/' configure*

-       # Fixes and patches from LFS, Redhat

-       sed -i -e 's/"db1"/& \&\& $name ne "nss_test1"/' scripts/test-installation.pl

        sed -i 's|@BASH@|/bin/bash|' elf/ldd.bash.in

-        # 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

-

-        # Glibc misc Bug Fixes

-        # fix for {linux,sys}/xattr.h incompatibility - commit fdbe8eae

-        #patch -p1 -i $stuff/glibc-2.19-xattr_header.patch

-

-        # fix issues in sin/cos slow path calculation - commit ffe768a9

-        #patch -p1 -i $stuff/glibc-2.19-fix-sign-in-bsloww1-input.patch

-

-        # fix tzselect with missing TZDIR - commit 893b4f37/c72399fb

-        #patch -p1 -i $stuff/glibc-2.19-tzselect-default.patch

-

-       # Glibc misc Bug Fixes

-       #patch -Np1 -i $stuff/glibc-2.14.1-fixes-1.patch

-

-       # Glibc Bug Sort Relocatable Objects Patch

-       #patch -Np1 -i $stuff/glibc-2.14.1-sort-1.patch

-

-       # Fix a bug that prevents Glibc from building with GCC-4.6.2

-       #patch -Np1 -i $stuff/glibc-2.14.1-gcc_fix-1.patch

-

-       # Revert commit causing issues with crappy DNS servers

-       #patch -Np1 -i $stuff/glibc-2.14-revert-4768ae77.patch

-

-       # re-export RPC interface until libtirpc is ready as a replacement

-       # http://sourceware.org/git/?p=glibc.git;a=commitdiff;h=acee4873 (only fedora branch...)

-       #patch -Np1 -i $stuff/glibc-2.14-reexport-rpc-interface.patch

-       # http://sourceware.org/git/?p=glibc.git;a=commitdiff;h=bdd816a3 (only fedora branch...)

-       #patch -Np1 -i $stuff/glibc-2.14-reinstall-nis-rpc-headers.patch

-       # GHOST

-       #patch -Np1 -i $stuff/glibc-2.14.1-CVE-2015-0235.patch

-

-        # https://sourceware.org/bugzilla/show_bug.cgi?id=21661

-        #patch -p1 -i $stuff/glibc-2.23-gcc.patch

-

        # Patch for reenable C.UTF8

        patch -p1 -i $stuff/glibc-c-utf8-locale.patch

-       # Patch for CVE-2024-2961

-       # see https://sourceware.org/git/?p=glibc.git;a=blob;f=advisories/GLIBC-SA-2024-0004;h=23a8115d;hb=HEAD

-       # https://sourceware.org/git/?p=glibc.git;a=patch;h=682ad4c8 (adjust little for 2.28)

-       patch -p1 < $stuff/glibc-2.28-CVE-2024-2961.patch

-

-       # Patch for CVE-2025-4802, adjust for backport to 2.28

-       # see https://www.cve.org/CVERecord?id=CVE-2025-4802

-       # see https://sourceware.org/cgit/glibc/commit/?id=1e18586c

-       patch -p1 -i $stuff/CVE-2025-4802.patch

-

-       # Update for binutils 2.29, see https://sourceware.org/bugzilla/show_bug.cgi?id=21661

-       sed -i 's|obstack_compat;|obstack_compat  __attribute__ ((nocommon));|' malloc/obstack.c

-

-        # 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\[\] neutral' \

-        resolv/base64.c

-

-       # Fix a stack imbalance that occurs under some conditions:

-       #sed -i '195,213 s/PRIVATE_FUTEX/FUTEX_CLOCK_REALTIME/' \

-       #       nptl/sysdeps/unix/sysv/linux/x86_64/pthread_rwlock_timedrdlock.S \

-       #       nptl/sysdeps/unix/sysv/linux/x86_64/pthread_rwlock_timedwrlock.S

+       sed -e '402a\      *result = local->data.services[database_index];' \

+           -i nss/nss_database.c

        # Glibc needs ld.so.conf in the install destdir.

        mkdir -p $WOK/$PACKAGE/install/etc

        touch $WOK/$PACKAGE/install/etc/ld.so.conf

        mkdir ../glibc-build && cd ../glibc-build

-

+

        # Read the INSTALL file in glibc. Also Glibc dont build with -Os flag.

        # --enale-kernel use latest SliTaz Kernel version. From Glibc INSTALL:

        # "The higher the VERSION number is, the less compatibility code is

@@ -168,15 +101,14 @@

                i386|i486)

                        echo "CFLAGS += -O2 -march=i486 -mtune=i486" > configparms ;;

                x86_64)

-                       echo "CFLAGS += -O2 -fPIC"> configparams ;;

+                       echo "CFLAGS += -O2 -march=nocona -fPIC" > configparams ;;

                arm*)

                        echo "CFLAGS += -O2 -march=$ARCH -mtune=$ARCH" > configparms ;;

        esac

-       { libc_cv_slibdir=/lib $src/configure \

+       { libc_cv_include_x86_isa_level=no libc_cv_slibdir=/lib $src/configure \

                --disable-profile \

                --enable-add-ons \

-               --enable-kernel=2.6.30 \

-               --enable-obsolete-rpc \

+               --enable-kernel=5.10.221 \

                --libexecdir=/usr/lib/glibc \

                --build=$HOST_SYSTEM \

                --host=$HOST_SYSTEM \

Offline

#586 2025-07-25 13:11:17

shann
Administrator
Registered: 2011-04-01
Posts: 1,296
Website

Re: [Current version (6.0) dev thread] - Usage of SliTaz 4.0 / rolling

Maybe i said win too fast,

Seem segfault appear for commands hmm

root@slitaz:/home/slitaz/wok# make

make: *** No targets specified and no makefile found.  Stop.

root@slitaz:/home/slitaz/wok# cook glibc-locale

Segmentation fault

sh: 0: unknown operand

nodev    aufs

Setup aufs chroot...

Segmentation fault

sh: 0: unknown operand

Cook: glibc-locale 2.34

==================================================================================================================

QA: checking package receipt...

==================================================================================================================

Pack: glibc-locale 2.34-x86_64

==================================================================================================================

Executing: genpkg_rules

* Removing all base files... Done

* Removing locale: cs Done

* Removing locale: de Done

* Removing locale: es Done

* Removing locale: fr Done

* Removing locale: hu Done

* Removing locale: id Done

* Removing locale: it Done

* Removing locale: pt Done

* Removing locale: ru Done

* Removing locale: sl Done

* Removing locale: zh_CN Done

* Removing locale: zh_TW Done

Copying "receipt"...                                                                                    Segmentation fault

Segmentation fault

cat: can't open '/home/slitaz/wok/glibc-locale/taz/glibc-locale-*/files.list': No such file or directory

Summary for: glibc-locale 2.34

==================================================================================================================

Packed      : 31.4M

Compressed  :

Files       : 0

Cook time   : 0s

Cook date   : 2025-07-25 13:08

Host arch   : x86_64

==================================================================================================================

Leaving aufs chroot...

Updating x86_64 chroot environment...

Segmentation fault

Segmentation fault

sh: 0: unknown operand

Segmentation fault

sh: bad number

Package "glibc-locale" blocked.

Offline

#587 2025-07-29 13:58:37

shann
Administrator
Registered: 2011-04-01
Posts: 1,296
Website

Re: [Current version (6.0) dev thread] - Usage of SliTaz 4.0 / rolling

Hi,

Seem that below process work (need to ensure that breaking nothing on EeePC and case usage)

1/ rebuild slitaz-toolchain (with remove --disable-initfini-array for binutils)

=> when test glibc-base on current64 chroot segfault for make

2/ rebuild toolchain again with new binutils / gcc fresh packages

=> install glibc-base again on current64 chroot, make happy no segfault

3/ Inside current64 chroot, prepare cook env with [c]cook setup[/c]

=> reinstall glibc-base / gcc / binutils from fresh packages

4/ From current64 chroot, try to build package (test with zlib)

=> no segfault see

5/ Last test, try to rebuild glibc and check if segfault when package glibc-*, i blocked glibc-* to ensure no erase.

=> seem no issue or segfault appear when pack glibc-* (except not found for version libs 2.3*.so)

Offline

#588 2025-07-29 18:49:43

shann
Administrator
Registered: 2011-04-01
Posts: 1,296
Website

Re: [Current version (6.0) dev thread] - Usage of SliTaz 4.0 / rolling

Test on my EeePC,

All apps seem work correctly.

I update udev/gvfs packages (i don't push new udev / gvfs on mirror), work except issue i see about pcmanfm when disconnect through pcmanfm.

At time i can push udev/gvfs packages on mirror for current64.

Need to check for mass rebuild with glibc 2.34, or at least gvfs/pcmanfm to test if segfault libc.so.6 when disconnect mtp on pcmanfm dissapear or not.

[attachment=53178,3716]

EDIT: i push udev, libgudev, pcmanfm, gvfs new packages on mirror.

For pcmanfm, rebuild it and new change it's french translation for right click ("ouvrir en tant que root", "lancer le diaporama", "définir en tant que fond d'écran")

Offline

#589 2025-07-30 07:08:46

shann
Administrator
Registered: 2011-04-01
Posts: 1,296
Website

Re: [Current version (6.0) dev thread] - Usage of SliTaz 4.0 / rolling

Hi

Just finish to rebuild slitaz-toolchain twice and update chroot current64. Ready for mass rebuild.

(current64) root@eretria:/home/slitaz/wok# cat /usr/share/doc/slitaz/toolchain.txt

SliTaz GNU/Linux toolchain

================================================================================

Build date   : 2025-07-30

Architecture : x86_64

Build system : x86_64-slitaz-linux

Host  system : x86_64-slitaz-linux

Packages:

    * Binutils 2.37

    * Linux API headers 5.10.238

    * GCC 10.2.0

    * Glibc 2.34

Toolchain documentation: http://doc.slitaz.org/en:cookbook:toolchain

================================================================================

(current64) root@eretria:/home/slitaz/wok# /lib/libc.so.6

GNU C Library (GNU libc) stable release version 2.34.

Copyright (C) 2021 Free Software Foundation, Inc.

This is free software; see the source for copying conditions.

There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A

PARTICULAR PURPOSE.

Compiled by GNU CC version 10.2.0.

libc ABIs: UNIQUE IFUNC ABSOLUTE

For bug reporting instructions, please see:

<https://www.gnu.org/software/libc/bugs.html>.

(current64) root@eretria:/home/slitaz/wok# make

make: *** No targets specified and no makefile found.  Stop.

Offline

#590 2025-07-30 09:52:48

shann
Administrator
Registered: 2011-04-01
Posts: 1,296
Website

Re: [Current version (6.0) dev thread] - Usage of SliTaz 4.0 / rolling

With glibc 2.34, begin mass rebuild and at time i have few packages failed.

texinfo need to be patch https://bugs.gentoo.org/803485

gc need to be bump to 8.0.6, with 7.2g cook failed with [c]multiple definition of 'GC_jmp_buf';[/c]

libwrap need to be patch (sys_errlist and sys_nerr calls remove since glibc 2.32), see https://www.linuxquestions.org/questions/slackware-14/slackware-from-scratch-and-x11-4175560702/page49.html#post6154760

Continue to mass rebuild, when finished, i will doing tests on EeePC to ensure all work as expected.

Offline

#591 2025-07-30 17:49:42

gibor
Moderator
Registered: 2011-04-30
Posts: 1,067

Re: [Current version (6.0) dev thread] - Usage of SliTaz 4.0 / rolling

Hi, what you state about textinfo puts me in doubt: I have a problem with wget, where there seems to be a mismatch on address resolution. Now with what you are saying I have a doubt that it is a malfunction of the same.

Is there a command to test the correct operation?

Can you test with wget if it performs the download, or if it responds NOT FOUND at the end of the redirects?

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

Ciao, quello che affermi su textinfo mi mette dei dubbi: ho un problema con wget, dove pare che ci sia un disallineamento sulla risoluzione degli indirizzi. Ora con quello che dici mi viene il dubbio che sia un malfunzionamento dello stesso.

C'è un comando per testare il corretto funzionamento?

Puoi provare con wget se esegue il download, o se alla fine dei redirect risponde NOT FOUND?

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

python3 adups_search_updates.py

[*] Config: {'project': 'bird$sz6737$7.0_EU$MV168$NUU$N5001L_en-US_other', 'version': 'N5001L-EU-MV168-20190118'}

[*] POST Data: key=1D08F54F25DE319EE62E66447DCC139899D6B44CB6BFB1F1EAC6EB069A9ADEED11E0EBE1FBA69FC627EBCDE98D17E5E4E182DDFABD2C8BD994EA6A8CB9ABE1DDFCC60DCA81C1A900A5B9B7BFE1C0F75FF0DC94EB179FF18099A5E2CF5388D189E916E2E5F5FDB997&shaKey=ae039d7b092fd7f60a8b57c84562c3f0c404e1a86ea042dbee7774c797ead35f

[*] POST: https://fota5p.adups.com/otainter-5.0/fota5/detectSchedule.do

[+] Update found!

[Update Info]

   Version: N5001L-EU-MV168-20190326

   Size: 60.036491 MB

   Download URL: http://cloudflare.mayitek.com/ota/root_data02_2/bird_sz/bird_sz6737_7.0/EU_MV168_NUU_N5001L/en-US/other/N5001L-EU-MV168-20190326/N5001L-EU-MV168-20190118-N5001L-EU-MV168-201903261553587021848/update.zip?m=null

   MD5 Sum: df4399574a61d8f9b44d7fbce911b73a

wget download

wget http://cloudflare.mayitek.com/ota/root_data02_2/bird_sz/bird_sz6737_7.0/EU_MV168_NUU_N5001L/en-US/other/N5001L-EU-MV168-20190326/N5001L-EU-MV168-20190118-N5001L-EU-MV168-201903261553587021848/update.zip

Offline

#592 2025-07-30 18:02:38

shann
Administrator
Registered: 2011-04-01
Posts: 1,296
Website

Re: [Current version (6.0) dev thread] - Usage of SliTaz 4.0 / rolling

Hi gibor,

Not sure if related :

root@slitaz:~# tazpkg -l |grep glibc

glibc                              2.34              meta

glibc-base                         2.34              base-system

glibc-dev                          2.34              development

glibc-locale                       2.34              system-tools

root@slitaz:~# tazpkg -l |grep wget

wget                               1.21.3            network

root@slitaz:~# wget http://cloudflare.mayitek.com/ota/root_data02_2/bird_sz/bird_sz6737_7.0/EU_MV168_NUU_N5001L/en-US/other/N5001L-EU-MV168-20190326/N5001L-EU-MV168-20190118-N5001

L-EU-MV168-201903261553587021848/update.zip

--2025-07-30 17:59:33--  http://cloudflare.mayitek.com/ota/root_data02_2/bird_sz/bird_sz6737_7.0/EU_MV168_NUU_N5001L/en-US/other/N5001L-EU-MV168-20190326/N5001L-EU-MV168-20190118-N5001L-EU-MV168-201903261553587021848/update.zip

Resolving cloudflare.mayitek.com... 2606:4700:3110::6812:35cf, 2606:4700:3110::6812:3238, 104.18.50.56, ...

Connecting to cloudflare.mayitek.com|2606:4700:3110::6812:35cf|:80... connected.

HTTP request sent, awaiting response... 302 Found

Location: http://fotadown.mayitek.com/ota/root_data02_2/bird_sz/bird_sz6737_7.0/EU_MV168_NUU_N5001L/en-US/other/N5001L-EU-MV168-20190326/N5001L-EU-MV168-20190118-N5001L-EU-MV168-201903261553587021848/update.zip [following]

--2025-07-30 17:59:33--  http://fotadown.mayitek.com/ota/root_data02_2/bird_sz/bird_sz6737_7.0/EU_MV168_NUU_N5001L/en-US/other/N5001L-EU-MV168-20190326/N5001L-EU-MV168-20190118-N5001L-EU-MV168-201903261553587021848/update.zip

Resolving fotadown.mayitek.com... 157.185.128.117, 140.150.22.16

Connecting to fotadown.mayitek.com|157.185.128.117|:80... connected.

HTTP request sent, awaiting response... 302 Found

Location: http://43.143.48.199/ota/root_data02_2/bird_sz/bird_sz6737_7.0/EU_MV168_NUU_N5001L/en-US/other/N5001L-EU-MV168-20190326/N5001L-EU-MV168-20190118-N5001L-EU-MV168-201903261553587021848/update.zip [following]

--2025-07-30 17:59:34--  http://43.143.48.199/ota/root_data02_2/bird_sz/bird_sz6737_7.0/EU_MV168_NUU_N5001L/en-US/other/N5001L-EU-MV168-20190326/N5001L-EU-MV168-20190118-N5001L-EU-MV168-201903261553587021848/update.zip

Connecting to 43.143.48.199:80... connected.

HTTP request sent, awaiting response... 301 Moved Permanently

Location: http://fota-delta-package-1254102626.cos.ap-shanghai.myqcloud.com/apps/ota/root_data02_2/bird_sz/bird_sz6737_7.0/EU_MV168_NUU_N5001L/en-US/other/N5001L-EU-MV168-20190326/N5001L-EU-MV168-20190118-N5001L-EU-MV168-201903261553587021848/update.zip [following]

--2025-07-30 17:59:35--  http://fota-delta-package-1254102626.cos.ap-shanghai.myqcloud.com/apps/ota/root_data02_2/bird_sz/bird_sz6737_7.0/EU_MV168_NUU_N5001L/en-US/other/N5001L-EU-MV168-20190326/N5001L-EU-MV168-20190118-N5001L-EU-MV168-201903261553587021848/update.zip

Resolving fota-delta-package-1254102626.cos.ap-shanghai.myqcloud.com... 117.68.20.85, 117.68.20.84

Connecting to fota-delta-package-1254102626.cos.ap-shanghai.myqcloud.com|117.68.20.85|:80... connected.

HTTP request sent, awaiting response... 404 Not Found

2025-07-30 17:59:35 ERROR 404: Not Found.

If i try url on firefox, receive xml error for object :

<Error>

[c]NoSuchKey[/c]

<Message>The specified key does not exist.</Message>

<Resource>

/apps/ota/root_data02_2/bird_sz/bird_sz6737_7.0/EU_MV168_NUU_N5001L/en-US/other/N5001L-EU-MV168-20190326/N5001L-EU-MV168-20190118-N5001L-EU-MV168-201903261553587021848/update.zip

</Resource>

<RequestId>Njg4YTVkZjVfNGIzMDY4MDlfMWU4ZV83NTVhZDI3</RequestId>

<TraceId>

OGVmYzZiMmQzYjA2OWNhODk0NTRkMTBiOWVmMDAxODc0OWRkZjk0ZDM1NmI1M2E2MTRlY2MzZDhmNmI5MWI1OTc5ODg4ODNhM2YxMjhiZjRjM2YxMGJhMzMwMjU5YTg0Y2I4MDFlOGYwMDcyYmMyMGJhNDg3MjNlZTQ5MWRlZWQ=

</TraceId>

</Error>

Now it's py3k need be patched to avoid stuck test with gcc10 https://bugs.python.org/issue38965.

Offline

#593 2025-07-30 19:32:58

gibor
Moderator
Registered: 2011-04-30
Posts: 1,067

Re: [Current version (6.0) dev thread] - Usage of SliTaz 4.0 / rolling

Thanks, I didn't encounter any errors during compilation with Python 3. Perhaps the patch was already included, since I use Python 3.13.5, but I'll check the sources.

The download also fails on Android FOTA, so I think support has ended, but this hasn't been reported by the source servers.

Offline

#594 2025-07-30 19:50:31

shann
Administrator
Registered: 2011-04-01
Posts: 1,296
Website

Re: [Current version (6.0) dev thread] - Usage of SliTaz 4.0 / rolling

ok, no problem.

For my issue it's not python3 (3.9.22) but py3k (3.7.0).

I recheck required for packages i don't build on current except graphviz that required by imagemagick.

If remind i need to build py3k because graphviz failed to run with python3-dev, on temp chroot i have used to build lfs cross tool, i retry to build graphviz with python3 (3.9.22), seem build ok and imagemagick build also. I think i can don't rebuild it and remove py3k, py3k-dev from current, infact not used in others packages.

Offline

#595 2025-08-03 20:21:20

shann
Administrator
Registered: 2011-04-01
Posts: 1,296
Website

Re: [Current version (6.0) dev thread] - Usage of SliTaz 4.0 / rolling

Hi,

Mass rebuild in progress, think remain ~100 packages to be build.

Globally all build correctly, sometime issue related to gcc 10 with "multiple definitions" error for few packages, patch available or need to add [c]-fcommon[/c] on CFLAGS.

After need to build iso and test to my EeePC to ensure all work as expected before push stuff.

In preliminary test, notice that upgrade glibc 2.31 to 2.34 in place work without issue, same smooth when switch to glibc 2.31 from 2.28.

Offline

#596 2025-08-04 19:08:55

shann
Administrator
Registered: 2011-04-01
Posts: 1,296
Website

Re: [Current version (6.0) dev thread] - Usage of SliTaz 4.0 / rolling

Mass rebuild for 1744 packages is done.

three changes reported :

- libpthread-stubs not rebuild, failed to build, seem packages required it can be build without (suspect with new glibc / gcc, not necessary since).

- py3k/py3k-dev removed, only graphviz required and can be build with python3

- gvfs-obexftp removed in 2.36.3

Now it's time to build iso and do tests on EeePC, check if all work as expected in live mode, and if upgrade from installed system smooth or not.

Offline

#597 2025-08-06 08:47:34

gibor
Moderator
Registered: 2011-04-30
Posts: 1,067

Re: [Current version (6.0) dev thread] - Usage of SliTaz 4.0 / rolling

Globally all build correctly, sometime issue related to gcc 10 with "multiple definitions" error for few packages, patch available or need to add -fcommon on CFLAGS.

Hi, to correct the error in gcc 10 I also use another method: during compilation, when “multiple definitons” appears, it also appears where the second definition of that argument is. At that point, step by step, you can edit the sources by inserting “extern” in those lines.

Offline

#598 2025-08-07 06:48:26

shann
Administrator
Registered: 2011-04-01
Posts: 1,296
Website

Re: [Current version (6.0) dev thread] - Usage of SliTaz 4.0 / rolling

Hi gibor,

Infact if i check patch, for fews add "extern".

For my tests on EeePC it's great.

Upgrade in place on livecd OK

Upgrade in place on hard disk OK

For both it's smooth, we update glibc-base/gcc-lib-base first and all packages after.

Tests i do all default apps work and other also.

I notice little issue but not directly related to new stack, it's for my laptop with amdgpu.

Infact libglvnd installed by default for tazweb required libGL.so.1, but in my case need to be remove clash with mesa, and block glamoregl initialisation

Offline

#599 2025-08-11 16:24:34

shann
Administrator
Registered: 2011-04-01
Posts: 1,296
Website

Re: [Current version (6.0) dev thread] - Usage of SliTaz 4.0 / rolling

Hi,

Repo of current64 is up to date now, and iso are rebuild.

https://people.slitaz.org/~shann/slitaz-current64-stuff/slitaz-current64-base64-grub2.iso

https://people.slitaz.org/~shann/slitaz-current64-stuff/slitaz-current64-core64-grub2.iso

Need to update my local current chroot and rebuild packages/iso and push them on mirror.

On tank glibc can't rebuild correctly (i think due of kernel 3.x)

Offline

#600 2025-08-26 18:54:31

gibor
Moderator
Registered: 2011-04-30
Posts: 1,067

Re: [Current version (6.0) dev thread] - Usage of SliTaz 4.0 / rolling

Small test for the version of Shann https://people.slitaz.org/~shann/slitaz-current64-stuff/slitaz-current64-core64-grub2.iso used to build a wifi printer server on the usual tablet with Baytrail: first difficulty was missing the hostapd package. Built from source and onward.

Attempted to install firefox, but it was unavailable on the repos. Installed a version of mine that I was already using at 64bit, and it asks me for gtk-3. It is available and I install it with tazpkg normally. On reboot black screen... so after the first few tries I find nothing to do to fix it.

I reset the installation and restart giving up firefox which was superfluous in this case.

Replacing the kernel with my 5.15.0 which already contained what was needed for audio, video, and keys. I also add the full firmware package just so there are no surprises.

Packages: cups, xsane and some scripts the server works fine. It shares printers and scanners in wifi network with a fixed ip.

Congratulations Shann, not bad for a temporary build!

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

Piccolo test per la versione di Shann https://people.slitaz.org/~shann/slitaz-current64-stuff/slitaz-current64-core64-grub2.iso utilizzata per la creazione di un server printer in wifi sul solito tablet con il Baytrail: prima difficoltà mancava il pacchetto hostapd. Costruito dai sorgenti e avanti.

Tentativo di installare firefox, ma risultava non disponibile sui repo. Installato una mia versione che già utilizzavo a 64bit, e mi chiede gtk-3. È disponibile e lo installo con tazpkg normalmente. Al riavvio schermo nero... così dopo i primi tentativi non trovo nulla da fare per risolvere.

Azzero l'installazione e riparto rinunciando a firefox che era superfluo in questo caso.

Sostituzione del kernel con il mio 5.15.0 che conteneva già quello che serviva per l'audio, il video, ed i tasti. Aggiungo pure il pacchetto firmware completo tanto per non avere sorprese.

Pacchetti: cups, xsane ed alcuni script il server funziona bene. Condivide stampanti e scanner in rete wifi con un ip fisso.

Complimenti Shann, non male per essere una build provvisoria!

Offline

Registered users online in this topic: 0, guests: 1
[Bot] ClaudeBot

Board footer

Powered by FluxBB
Modified by Visman

[ Generated in 0.043 seconds, 7 queries executed - Memory usage: 1.65 MiB (Peak: 1.77 MiB) ]