SliTaz Forum
You are not logged in.
Hi Filou,
i hope your health fine 
.
Don't worry, we need time for family, this summer i break time, huge work due of small team, and holiday (last week august).
Rome not build in one day, we need take time for build and test 
Offline
Hi Filou,
best vibes, keep up the good work!
Offline
Hi Filou,
211002_rootfs64_office.gz, bzImage
tazlito clean-distro
tazlito extract-distro /home/tux/slitaz.iso
cd /home/slitaz/5.0/distro/rootfs
tazlito gen-initiso
the new slitaz-5.0.iso size is 35.k
Offline
Hi Filou & Jianliulin,
When I use 210713_MySliTaz64.iso from https://people.slitaz.org/~filou/rootfs, I am able to boot into a GUI. However, when I try replacing the rootfs in this iso with the 211002_rootfs64_office.gz, I am unable to boot into GUI and it drops me on the login prompt on the same laptop.
I tried with a different device having a different graphics driver but the behavious is the same.
What should be done for getting a GUI using 211002_rootfs64_office.gz ? Is any boot parameter to be added ?
P.S.- I wanted to try 211002_rootfs64_office.gz as it was mentioned in a post that web browser is available in this. The 210713_MySliTaz64.iso does not have any web browser. When I tried dowmloading browser tazpkg from slitaz mirrors, i am unable to do so with a mirror synchronization error being reported. Also, since USB is not being recognized, local installation of tazpkg is not happening.
Can you pl suggest ?
Offline
Hi everyone and a happy new year to all of you.
It's been quite some time since I posted here something substantial but now I want to do so.
(I'll try to answer to slitaz_user4 in a minute, but first some more basic announcement...)
During the last weeks I was heavily involved in doing a new "mass sweep" after having set up a new wok on a LFS 11.2 basis.
Since during my first tries I quite soon made a mistake in accepting a glibc error concerning iconv and introducing libiconv in many packages, I had to learn at a later stage that this was a dead end. The same was applicable to pthread.
So I tried to do better in this run.
What did I do?
1.) Follow the LFS 11.2 documentation until I got to a chroot-able system with all necessary tools (gcc, binutils, ...)
2.) I then collected the slitaz scripts from the different .tazpkg as far as I could to "SliTaz-ize" the Chroot-System and modified them where necessary (worked quite well from the first try already).
3.) I cloned the wok and started to build again.
4.) I wrote a small script that re-ordered all the receipts by dependencies in order to do another "mass sweep".
5.) At some point I got a little impatient and wanted to see some results. So I picked a side-path before coming back to the mass-sweep
6.) During the side-path I concentrated on Wayland to get a better understanding and to support SliTaz' way into a sustainable future. I achived stable but feature-poor versions of Sway and Wayfire (both really impressed me, Sway for simplicity and Wayfire for its effects) still with some fixes to do (wf-panel doesn't work yet...).
7.) I then wanted to ave somethin presentable and concentrated on XFCE4 and LXDE. For sustainability reasons I tried to keep to GTK+3 and Python3 as far as possible.
At this moment, I am writing these lines under XFCE4 Ver. 4.18.0, havin AbiWord 3.0.5 and Gnumeric 1.12.53 open as well as mtPaint 3.50.09 on three monitors, Thunar presenting the directory trees (but no working gvfs yet), l3afpad for file editing and Evince for PDFs.
LXDE ist not working yet, but I am working on it...
Up to now, I have more than 2.500 packages compiled and will have to move on the next weeks.
I am preparing the uploads of everything (see https://people.slitaz.org/~filou/cooking64_new for the new packages) and will link the directories and files here soon... [attachment=51252,3293]
Offline
@slitaz_user4:
I'll update the available package with another one I am still using. (see https://people.slitaz.org/~filou/rootfs/211223_rootfs64_office.lzma )
If you still don't get a GUI could you then try to login with the prompt and then enter
[c]startx &> Test.log[/c]
please?
The Test.log file might tell us what is missing then...
... and for the browser:
Because of the high update ratios I tend to use the downloadable .tar Versions of the browsers (works for Palemoon, SeaMonkey and Firefox respectively).
I just download the Image, unpack it and start the binary from the Package
(for example: download from https://www.mozilla.org/de/firefox/new/, unpack with [c]tar xf [Firefox.tar.xz][/c] , cd to firefox directory and start with ./firefox)...
Offline
@jianliulin
Please be aware that my primary intent is to provide quite recent versions of the SliTaz packages in a x86_64 format and to compile some of them into bootable (or chroot-able) initramfs.
Many functionalities are not fully working though, and automatically creating working isos might be part of that.
Fully working scripts will remain the ultimate goal, but have to be corrected at a given time.
For the moment it is key to update the package receipts an build the full package basement for recent SliTaz versions...
... this is my contribution (as I understand it...)
In the meantime you could try a more manual solution:
1.) create a working dir:
[c]mkdir SliTaz_tmp && cd SliTaz_tmp[/c]
2.) unpack the lzma'ed rootfs:
[c]cp [YourDir]/rootfs.lzma . && lzma -d rootfs.lzma[/c]
2.) unpack the resulting cpio:
[c]cpio -idF rootfs[/c]
3.) either modify the rootfs "from outside":
[c]tazpkg -i [AnyPackage}.tazpkg --root=/[PATH]/SliTaz_tmp --nodeps[/c] (for each Package)
and edit any config files you need
or
Chroot into the image an modify "internally":
- create a Chroot.sh file somewhere outside SliTaz_tmp with the following:
====================================================
[c]#!/bin/sh
if [ -z "$1" ]; then
echo "Chroot into which directory?"
exit 1
fi
for FILESYS in dev proc sys run
do
mkdir -pv "$1/$FILESYS"
done
mount -v --bind /dev "$1/dev"
mount -v --bind /dev/pts "$1/dev/pts"
mount -vt proc proc "$1/proc"
mount -vt sysfs sysfs "$1/sys"
mount -vt tmpfs tmpfs "$1/run"
chroot "$1" /bin/sh --login
umount -v "$1/run" "$1/sys" "$1/proc" "$1/dev/pts" "$1/dev"[/c]
====================================================
and then chroot into the image with
[c]./Chroot.sh SliTaz_tmp[/c]
make your modifications inside the image (if you don't have internet access, then copy your /etc/resolv.conf into the image)
when finished, [c]exit[/c] the image (make sure, all directories inside the image are unmounted)
4.) when you're done with the modifications, cd into SliTaz_tmp and recreate an new version of the lzma'ed rootfs
[c]find . | cpio -o -H newc | lzma > /rootfs_new.lzma[/c]
... hope this helps...
Offline
Hi Filou,
Thanks for updating with 211223_rootfs64_office.lzma.
(1) After experimenting, I feel that all rootfs uploaded by you in people.slitaz.org/~filou/rootfs are able to boot into GUI only with linux kernel 5.10.3. With other kernel, no GUI is obtained and it drops into login prompt. I tried with two other Slitaz kernels (vmlinuz-4.17.7-slitaz & vmlinuz-3.16.55-slitaz64) and with a recent Puppy Linux kernel. It does not give a GUI for the other kernels.
(2) With kernel 5.10.3, I am now able to download and install latest versions of web browsers by following the method that you mentioned. I tried Firefox and Palemoon & both work properly.
(3) However, sound, wifi and USB tethering do not work, both in 211002_rootfs64_office.gz and 211223_rootfs64_office.lzma. Sound cards (mine is snd_hda_intel) are not recognized (“aplay -l” gives no sound cards found). Wifi adapter is not found and USB internet device (mobile phone in tethering mode) is not recognized when I use “udhcpc -i usb0” in terminal . I am able to regularly use sound and USB tethering on the same laptop with slitaz-rolling core64.
(4) On checking /lib/modules after booting, I find that it is empty unlike other slitaz versions where sound works.
(5) I went through similar forum posts- https://forum.slitaz.org/topic/having-sound-issues & https://forum.slitaz.org/topic/slitaz-future/page/15.
How do I install the modules required for sound, USB tethering and wifi to work ? I read in the first post that linux-sound (of the same kernel) needs to be installed. However, I am unable to find linux-sound-5.10.3.tazpkg.
(6) I installed linux-sound.4.17.7.tazpkg from next64 repo and all linux firmware and rebooted with new rootfs generated using tazusb gzip however sound, wifi and USB tethering still do not work.
(7) I also tried installing alsa plugins & alsa utils from cooking64_new repo however it throws up an error of glibc 2.34 not found (this continues after installing glibc 2.36) and some missing libraries.
I feel I am missing something basic. Pl suggest.
Offline
Hi slitaz_user4,
first: I am glad, that someone uses the files I uploaded, my impression was that noone really had an interest.
Maybe I should explain once again how I boot the rootfs:
I use grub4dos which provides the possibility to "batch boot" multiple initrd-files.
Like this, grub4dos first boots the kernel, then loads the rootfs.gz and afterwards loads the kernel modules (see https://people.slitaz.org/~filou/rootfs/ovl_modules.gz) on top of it (that's why "ovl"). So /lib/modules is empty "by intent" and is filled with the corresponding modules with the overlay (that's why most of your hardware doesn't work and GUI won't either...).
In fact, I stack more modules atop of this, namely for my home-directory, browsers or office packages (which I pack into cpio-files for that).
Like this, I can modularly load the packages I need for different hardwares and usages (Kernel would be hardware-specific while using the same home-Overlays on different machines...).
I posted a grub4dos config at the end of page 9 of this thread (https://forum.slitaz.org/topic/slitaz-future/page/9) while akm provided one for grub2 on page 14 (https://forum.slitaz.org/topic/slitaz-future/page/14). Maybe these could help...
If your grub does not support "stacking" different images, then you could merge the necessary kernel modules into the rootfs by using the "manual solution" I described in my last post...
All in all, the rootfs should work properly if you have a working Kernel/modules combination for your hardware and integrate it like described here...
Offline
Hi Filou,
(1) I used ovl_modules as an overlay along with rootfs during boot. Now, various modules including snd_hda_intel are getting loaded.
(2) I installed a number of packages(list attached) related to alsa & audio. Now, "aplay-l" gives the error messages of /lib/libc.so.6 version glibc 2.33 (and 2.34) not found. Screenshot is attached for reference.
(3) I normally use USB Tethering (with Android mobile) for internet. USB Tethering does not work . "udhcpc -i usb0" gives the error message of "udhcpc:SIOCGIFINDEX: No such device"
(4) While trying to download and install packages from "cooking64_new" repo, it is seen that tazpkg recharge fails as the file list has been named as "file.list.lzma" instead of "file-list.lzma" in "cooking64" old repo. So,dependencies are being pulled from the old repo (cooking64) only. Pl check this.
(5) Some of the packages in "cooking64" are missing in "cooking64_new". For example- libav-12.3
(6) Some packages available in "next64" repo are not available in "cooking64_new" repo. For example- at-spi2-core, libpcre, mesa-libgbm, xorg-libxcb, fdk-aac, linux, linux-wireless (Maybe, ovl_modules.gz takes care of the last two). So, some manual loading from "next64" repo is required for some dependencies. I am not sure whether that is the right thing to do as "next64"
is of a different kernel version.
Pl suggest what I need to do to get audio & USB tethering working. I am attaching lsmod, lspci, list of installed packages and tazhw detect-pci outputs as txt files.
Offline
Hi slitaz_user4,
(1) good to hear
(2)/(4) please be aware, that 'cooking64_new' is based on a different glibc than 'cooking64', that's why you get errors for aplay. For the time being stick to 'cooking64' since I did not publish any rootfs for the new repository yet (I have a Wayland only Sway version as well as XFCE rootfs that are providing a rudimentary GUI, but are not really publishable yet).
So the combination of Kernel+Modules+rootfs+'cooking64' should be the most promising way.
(3) For tethering, please install 'usb-modeswitch' and 'usb-modeswitch-data', I am not sure, if this might help. Otherwise, you could try to use a kernel + modules of any distribution that is working for your USB tethering already... (sorry for the moment).
(5) this is true, since for a full blown 64bit SliTaz repository, 'cooking64' was the first try from my side (with some problems that arose later (-> libiconv/libpthread). 'cooking64_new' is work in progress and will grow over time but is still premature.
(6) 'next64' and my work are totally independent. See (5).
Cheers!
Offline
@Filou
hi Filou，thank's your help.
I runing dotnet7.0 sdk (https://dotnet.microsoft.com/en-us/download/dotnet/7.0) on 211223_rootfs64_office.lzma , throw erorr missing icu ，I install icu and icu-dev ，It still not worked， What I need to do to make dotnet7.0 sdk run successfully
Offline
Hi jianliulin,
I guess you installed icu version 70.1 using [c]tazpkg -gi[/c], right?
(If you used Version 72.1 from the new repository, that one is compiled against a newer glib).
If we're talking about 70.1, maybe the following might help:
1.) login as root (or use [c]su[/c])
2.) execute [c]ldconfig[/c] in order to rebuild the dynamic libraries index
(if ldconfig can't be found, then install glibc-dev)
3.) try again
If you still get an error, then more details about "not worked" would be helpful.
(I don't know how you start the sdk, but you might add [c]&> dotnetsdk.log[/c] to your command in order to collect the necessary information...)
Offline
Hi Filou
A:
I boot 211002_rootfs64_office.gz with grub4dos
title 211002_rootfs64_office.gz
root (hd0,2)
kernel /slitaz/bzImage64 rw root=/dev/null vga=normal autologin lang=en_US kmap=us
initrd /slitaz/211002_rootfs64_office.gz
stlitaz cannot enter the desktop，I installed icu then can runing dotnet app
root@slitaz:~# ./test.exe
Hello Word!
B:
I boot 211002_rootfs64_office.gz and ovl_modules with grub4dos
title 211002_rootfs64_office.gz
root (hd0,2)
kernel /slitaz/bzImage64 rw root=/dev/null vga=normal autologin lang=en_US kmap=us
initrd /slitaz/211002_rootfs64_office.gz
initrd /slitaz/ovl_modules
stlitaz can enter the desktop， I installed icu then can not runing dotnet app
root@slitaz:~# ./test.exe
Process terminated. Couldn't find a valid ICU package installed on the system. Please install libicu (or icu-libs) using your package manager and try again. Alternatively you can set the configuration flag System.Globalization.Invariant to true if you want to run with no globalization support. Please see https://aka.ms/dotnet-missing-libicu for more information.
at System.Environment.FailFast(System.String)
at System.Globalization.GlobalizationMode+Settings..cctor()
at System.Globalization.GlobalizationMode+Settings.get_Invariant()
at System.Globalization.GlobalizationMode.get_Invariant()
at System.Globalization.CultureData.CreateCultureWithInvariantData()
at System.Globalization.CultureData.get_Invariant()
at System.Globalization.TextInfo..cctor()
at System.String.ToLowerInvariant()
at System.Text.EncodingHelper.GetCharset()
at System.Text.EncodingHelper.GetEncodingFromCharset()
at System.ConsolePal.GetConsoleEncoding()
at System.ConsolePal.get_OutputEncoding()
at System.Console.get_OutputEncoding()
at System.Console.CreateOutputWriter(System.IO.Stream)
at System.Console.<get_Out>g__EnsureInitialized|26_0()
at System.Console.get_Out()
at System.Console.WriteLine(System.String)
at Program.<Main>$(System.String[])
Aborted
root@slitaz:~#
211223_rootfs64_office.lzma like 211002_rootfs64_office.gz throw the same information
What's your email ,I send the test.exe（about 4M） to you ,you can reproduce the information
Offline
Hi jianliulin,
some aspects from my point of view:
1.) in case A you seem to be missing the kernel modules. If this is correct, then starting the desktop will always fail due to missing drivers/kernel modules.
2.) if I understand correctly, then you have built an .exe file using some dotnet environment. If this environment is part of the SliTaz repository and you discovered an issue there, then I suggest to open a new thread, since your problem has nothing to do with the development of SliTaz in the future (which this thread was originally opened up for).
(As you seem to be using the 64bit "interim"-version of SliTaz that I compiled on a Linux-From-Scratch 10 basis, I can't recall to have built a dotnet development package.)
At the moment, I don't understand, which tools you used to build which kind of executable (.exe suggests a Windows-executable). The missing link to the icu-library points in the direction that your Build-environment might have been built without the necessary icu development files...
Offline
@Filou,
LIBRARY_PATH
configure: error: C compiler cannot create executables
checking for x86_64-slitaz-linux-gcc... no
checking for gcc... gcc
checking whether the C compiler works... no
configure: error: in `/home/slitaz/wok/xorg-xf86-video-amdgpu/source/xorg-xf86-video-amdgpu-22.0.0':
configure: error: C compiler cannot create executables
See `config.log' for more details - Attachments config.log (12.2 KB,
slitaz-toolchain - isl version none
GNU C17 (SliTaz) version 8.2.0 (i486-slitaz-linux)
compiled by GNU C version 8.2.0, GMP version 6.1.2, MPFR version 4.0.1, MPC version 1.1.0, isl version none
$ echo 'int main() { return 0; }' > test.c
$ gcc -v -o test.o test.c
https://forum.slitaz.org/topic/slitaz-next-41485/page/2#post-49031
https://forum.slitaz.org/topic/update-kernel-1/page/3#post-48139
1.
root@slitaz:~# gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-slitaz-linux-gnu/12.2.0/lto-wrapper
Target: x86_64-slitaz-linux-gnu
Configured with: /home/slitaz/wok/gcc/source/gcc-12.2.0/configure --libexecdir=/usr/lib --disable-multilib --disable-bootstrap --with-system-zlib --enable-nls --enable-languages=c,c++,objc,fortran --enable-shared --enable-clocale=gnu --enable-objc-gc --enable-__cxa_atexit --enable-lto --enable-threads=posix --with-pkgversion=SliTaz --build=x86_64-slitaz-linux-gnu --target=x86_64-slitaz-linux-gnu
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 12.2.0 (SliTaz)
2.
root@slitaz:~# echo 'int main() { return 0; }' > test.c
root@slitaz:~# gcc -v -o test.o test.c
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-slitaz-linux-gnu/12.2.0/lto-wrapper
Target: x86_64-slitaz-linux-gnu
Configured with: /home/slitaz/wok/gcc/source/gcc-12.2.0/configure --libexecdir=/usr/lib --disable-multilib --disable-bootstrap --with-system-zlib --enable-nls --enable-languages=c,c++,objc,fortran --enable-shared --enable-clocale=gnu --enable-objc-gc --enable-__cxa_atexit --enable-lto --enable-threads=posix --with-pkgversion=SliTaz --build=x86_64-slitaz-linux-gnu --target=x86_64-slitaz-linux-gnu
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 12.2.0 (SliTaz)
COLLECT_GCC_OPTIONS='-v' '-o' 'test.o' '-mtune=generic' '-march=x86-64' '-dumpdir' 'test.o-'
/usr/lib/gcc/x86_64-slitaz-linux-gnu/12.2.0/cc1 -quiet -v test.c -quiet -dumpdir test.o- -dumpbase test.c -dumpbase-ext .c -mtune=generic -march=x86-64 -version -o /tmp/ccMbr0oH.s
/usr/lib/gcc/x86_64-slitaz-linux-gnu/12.2.0/cc1: error while loading shared libraries: libisl.so.23: cannot open shared object file: No such file or directory
3.
root@slitaz:~# tazpkg -gi isl
root@slitaz:~# gcc -v -o test.o test.c
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-slitaz-linux-gnu/12.2.0/lto-wrapper
Target: x86_64-slitaz-linux-gnu
[..]
COLLECT_GCC_OPTIONS='-v' '-o' 'test.o' '-mtune=generic' '-march=x86-64' '-dumpdir' 'test.o.'
/usr/lib/gcc/x86_64-slitaz-linux-gnu/12.2.0/collect2 -plugin /usr/lib/gcc/x86_64-slitaz-linux-gnu/12.2.0/liblto_plugin.so -plugin-opt=/usr/lib/gcc/x86_64-slitaz-linux-gnu/12.2.0/lto-wrapper -plugin-opt=-fresolution=/tmp/cc74BPIu.res -plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lgcc_s -plugin-opt=-pass-through=-lc -plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lgcc_s --eh-frame-hdr -m elf_x86_64 -dynamic-linker /lib64/ld-linux-x86-64.so.2 -o test.o crt1.o crti.o /usr/lib/gcc/x86_64-slitaz-linux-gnu/12.2.0/crtbegin.o -L/usr/lib/gcc/x86_64-slitaz-linux-gnu/12.2.0 -L/usr/lib/gcc/x86_64-slitaz-linux-gnu/12.2.0/../../../../lib -L/lib/../lib -L/usr/lib/../lib -L/usr/lib/gcc/x86_64-slitaz-linux-gnu/12.2.0/../../.. /tmp/ccvjJ66F.o -lgcc --push-state --as-needed -lgcc_s --pop-state -lc -lgcc --push-state --as-needed -lgcc_s --pop-state
/usr/lib/gcc/x86_64-slitaz-linux-gnu/12.2.0/crtend.o crtn.o
/usr/bin/ld: cannot find crt1.o: No such file or directory
/usr/bin/ld: cannot find crti.o: No such file or directory
collect2: error: ld returned 1 exit status
4.
root@slitaz:~# find /usr/ -name crt?.o
/usr/lib64/crt1.o
/usr/lib64/crti.o
/usr/lib64/crtn.o
root@slitaz:~# ln -s /usr/lib64/crt1.o /usr/lib/.
root@slitaz:~# ln -s /usr/lib64/crti.o /usr/lib/.
root@slitaz:~# ln -s /usr/lib64/crtn.o /usr/lib/.
root@slitaz:~# tazpkg -sp crt1.o
Search result for package "crt1.o"
===============================================================
glibc-dev
musl-libc-dev
===============================================================
2 packages
5.
root@slitaz:~# gcc -v -o test.o test.c
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-slitaz-linux-gnu/12.2.0/lto-wrapper
Target: x86_64-slitaz-linux-gnu
Configured with: /home/slitaz/wok/gcc/source/gcc-12.2.0/configure --libexecdir=/usr/lib --disable-multilib --disable-bootstrap --with-system-zlib --enable-nls --enable-languages=c,c++,objc,fortran --enable-shared --enable-clocale=gnu --enable-objc-gc --enable-__cxa_atexit --enable-lto --enable-threads=posix --with-pkgversion=SliTaz --build=x86_64-slitaz-linux-gnu --target=x86_64-slitaz-linux-gnu
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 12.2.0 (SliTaz)
COLLECT_GCC_OPTIONS='-v' '-o' 'test.o' '-mtune=generic' '-march=x86-64' '-dumpdir' 'test.o-'
/usr/lib/gcc/x86_64-slitaz-linux-gnu/12.2.0/cc1 -quiet -v test.c -quiet -dumpdir test.o- -dumpbase test.c -dumpbase-ext .c -mtune=generic -march=x86-64 -version -o /tmp/ccr2oPU8.s
GNU C17 (SliTaz) version 12.2.0 (x86_64-slitaz-linux-gnu)
compiled by GNU C version 12.2.0, GMP version 6.2.1, MPFR version 4.1.0, MPC version 1.2.1, isl version isl-0.24-GMP
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=65536
ignoring nonexistent directory "/usr/local/include"
ignoring nonexistent directory "/usr/lib/gcc/x86_64-slitaz-linux-gnu/12.2.0/../../../../x86_64-slitaz-linux-gnu/include"
#include "..." search starts here:
#include <...> search starts here:
/usr/lib/gcc/x86_64-slitaz-linux-gnu/12.2.0/include
/usr/lib/gcc/x86_64-slitaz-linux-gnu/12.2.0/include-fixed
/usr/include
End of search list.
GNU C17 (SliTaz) version 12.2.0 (x86_64-slitaz-linux-gnu)
compiled by GNU C version 12.2.0, GMP version 6.2.1, MPFR version 4.1.0, MPC version 1.2.1, isl version isl-0.24-GMP
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=65536
Compiler executable checksum: 3a8d01156457c23734b0a8c87475536a
COLLECT_GCC_OPTIONS='-v' '-o' 'test.o' '-mtune=generic' '-march=x86-64' '-dumpdir' 'test.o-'
as -v --64 -o /tmp/cc1rbU3x.o /tmp/ccr2oPU8.s
GNU assembler version 2.39 (x86_64-pc-linux-gnu) using BFD version (GNU Binutils) 2.39
COMPILER_PATH=/usr/lib/gcc/x86_64-slitaz-linux-gnu/12.2.0/:/usr/lib/gcc/x86_64-slitaz-linux-gnu/12.2.0/:/usr/lib/gcc/x86_64-slitaz-linux-gnu/:/usr/lib/gcc/x86_64-slitaz-linux-gnu/12.2.0/:/usr/lib/gcc/x86_64-slitaz-linux-gnu/
LIBRARY_PATH=/usr/lib/gcc/x86_64-slitaz-linux-gnu/12.2.0/:/usr/lib/gcc/x86_64-slitaz-linux-gnu/12.2.0/../../../../lib/:/lib/../lib/:/usr/lib/../lib/:/usr/lib/gcc/x86_64-slitaz-linux-gnu/12.2.0/../../../:/lib/:/usr/lib/
COLLECT_GCC_OPTIONS='-v' '-o' 'test.o' '-mtune=generic' '-march=x86-64' '-dumpdir' 'test.o.'
/usr/lib/gcc/x86_64-slitaz-linux-gnu/12.2.0/collect2 -plugin /usr/lib/gcc/x86_64-slitaz-linux-gnu/12.2.0/liblto_plugin.so -plugin-opt=/usr/lib/gcc/x86_64-slitaz-linux-gnu/12.2.0/lto-wrapper -plugin-opt=-fresolution=/tmp/ccqlrHHN.res -plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lgcc_s -plugin-opt=-pass-through=-lc -plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lgcc_s --eh-frame-hdr -m elf_x86_64 -dynamic-linker /lib64/ld-linux-x86-64.so.2 -o test.o /usr/lib/gcc/x86_64-slitaz-linux-gnu/12.2.0/../../../../lib/crt1.o /usr/lib/gcc/x86_64-slitaz-linux-gnu/12.2.0/../../../../lib/crti.o /usr/lib/gcc/x86_64-slitaz-linux-gnu/12.2.0/crtbegin.o -L/usr/lib/gcc/x86_64-slitaz-linux-gnu/12.2.0 -L/usr/lib/gcc/x86_64-slitaz-linux-gnu/12.2.0/../../../../lib -L/lib/../lib -L/usr/lib/../lib -L/usr/lib/gcc/x86_64-slitaz-linux-gnu/12.2.0/../../.. /tmp/cc1rbU3x.o -lgcc --push-state --as-needed -lgcc_s --pop-state -lc -lgcc --push-state --as-needed -lgcc_s --pop-state /usr/lib/gcc/x86_64-slitaz-linux-gnu/12.2.0/crtend.o /usr/lib/gcc/x86_64-slitaz-linux-gnu/12.2.0/../../../../lib/crtn.o
COLLECT_GCC_OPTIONS='-v' '-o' 'test.o' '-mtune=generic' '-march=x86-64' '-dumpdir' 'test.o.'
6.
root@slitaz:~# file test.o
test.o: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, with debug_info, not stripped
root@slitaz:~#
Offline
echo 'int main(){}' | gcc -xc -
> # echo 'int main() { return 0; }' > test.c
> # gcc -v -o test.o test.c
> See `config.log' for more details
1. config.log
$ grep -A10 int config.log
| int
| main ()
| {
|
| ;
| return 0;
| }
configure:3505: error: in `/home/slitaz/wok/xorg-xf86-video-amdgpu/source/xorg-xf86-video-amdgpu-22.0.0':
configure:3507: error: C compiler cannot create executables
See `config.log' for more details.
2. Installation of Glibc
Caution
At this point, it is imperative to stop and ensure that the basic functions (compiling and linking) of the new toolchain are working as expected. To perform a sanity check, run the following commands:
echo 'int main(){}' | gcc -xc -
readelf -l a.out | grep ld-linux
If everything is working correctly, there should be no errors, and the output of the last command will be of the form:
[Requesting program interpreter: /lib64/ld-linux-x86-64.so.2]
Note that for 32-bit machines, the interpreter name will be /lib/ld-linux.so.2.
If the output is not shown as above or there was no output at all, then something is wrong. Investigate and retrace the steps to find out where the problem is and correct it. This issue must be resolved before continuing on.
Once all is well, clean up the test file:
rm -v a.out
https://www.linuxfromscratch.org/lfs/view/11.2/chapter05/glibc.html
Offline
@alanyih:
I am sorry, but I'm not able to grasp your message here.
I can see that you are using my latest wok and you are absolutely correct with the missing links to /usr/lib64/crtX.o due to the expectancy of SOME packages having them in /usr/lib.
During the mass sweep I regularly stumble upon packages that fail to compile due to a missing component and receive the quite generic error message, that the compiler can't create executables. The details most often are to be found in the config.log, as you stated.
But do you have any question? Any recommendation?
I don't know what I should make out of your "mostly shell" posts.... (Sorry 'bout that...)
Cheers!
Offline
@ Filou,
compiling and linking - toolchain
make clear, we are talking about the toolchain.
1.
/usr/lib/gcc/x86_64-slitaz-linux-gnu/12.2.0/crtend.o crtn.o
/usr/bin/ld: cannot find crt1.o: No such file or directory
/usr/bin/ld: cannot find crti.o: No such file or directory
collect2: error: ld returned 1 exit status
# tazpkg -sp crt1.o
Search result for package "crt1.o"
glibc-dev
# tazpkg -lf glibc-dev | grep crt[1in].o
/usr/lib64/Mcrt1.o
/usr/lib64/Scrt1.o
/usr/lib64/crt1.o
/usr/lib64/crti.o
/usr/lib64/crtn.o
/usr/lib64/gcrt1.o
/usr/lib64/grcrt1.o
/usr/lib64/rcrt1.o
2.
echo 'int main(){}' | gcc -xc -
> # echo 'int main() { return 0; }' > test.c
> # gcc -v -o test.o test.c
ensure that the basic functions (compiling and linking) of the toolchain are working as expected.
If everything is working correctly, there should be no errors,
3.
8.5.1. Installation of Glibc
Prepare Glibc for compilation:
../configure --prefix=/usr \
--disable-werror \
--enable-kernel=3.2 \
--enable-stack-protector=strong \
--with-headers=/usr/include \
libc_cv_slibdir=/usr/lib
The meaning of the configure options:
[..]
libc_cv_slibdir=/usr/lib
This variable sets the correct library for all systems. We do not want lib64 to be used.
8.5.2.3. Configuring the Dynamic Loader
By default, the dynamic loader (/lib/ld-linux.so.2) searches through /usr/lib for dynamic libraries that are needed by programs as they are run. However, if there are libraries in directories other than /usr/lib, these need to be added to the /etc/ld.so.conf file in order for the dynamic loader to find them. Two directories that are commonly known to contain additional libraries are /usr/local/lib and /opt/lib, so add those directories to the dynamic loader's search path.
more details..
https://www.linuxfromscratch.org/lfs/view/11.2/chapter08/glibc.html#contents-glibc
https://www.linuxfromscratch.org/lfs/view/11.2/chapter05/glibc.html
Offline
@alanyih,
now I see what you are pointing too.
During the "LFS-phase" I kept closely to the LFS manual, but after adding the SliTaz-scripts i.o.t. prepare the Wok, I used (and adapted) the available SliTaz receipts.
Since these were created for a 32bit system, the config options you highlighted were not contained in the receipt, and I didn't recognize.
I will try to adapt the glibc(-dev) receipts to reflect this, hoping this will not break too many of the already cooked packages...
Thanx for the hint!
Offline
xfce-4.18 - slitaz
based on cooking64_new and
xfce-4.18 ( converted from slackware )
$ ldconfig -V
ldconfig (GNU libc) 2.36
Copyright (C) 2022 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.
Written by Andreas Jaeger.
$ tazpkg
SliTaz package manager - Version: 962
=================================================
Installed packages: 261
Installed files: 17217
Blocked packages: 0
Upgradeable packages: 0
Repository: Main
Last recharge: never.
Mirrored packages: 2516
=================================================
[attachment=51400,3334]
Offline
@alanyih
where can download the xfce-4.18-slitaz
Offline
@jianliulin,
under construction.
Offline
@alanyih:
thank you for your enduring work!
Could you elaborate on why you converted xfce 4.18 from slackware?
I provided xfce 4.18 packages about 2 months ago in the repository cooking_new. Did you meet any problems to get them running or were important components missing?
Offline
@Filou,
some files and packages missing
1. some files missing, e.g. libxfce4ui
/usr/bin/xfce4-about
/usr/lib64/girepository-1.0/Libxfce4ui-2.0.typelib
/usr/lib64/glade/modules/libxfce4uiglade2.la
/usr/lib64/glade/modules/libxfce4uiglade2.so
/usr/share/gir-1.0/Libxfce4ui-2.0.gir
/usr/share/glade/catalogs/libxfce4ui-2.xml
/usr/share/glade/pixmaps/hicolor/16x16/actions/widget-libxfce4ui-xfce-titled-dialog.png
/usr/share/glade/pixmaps/hicolor/22x22/actions/widget-libxfce4ui-xfce-titled-dialog.png
/usr/share/vala/vapi/libxfce4ui-2.deps
/usr/share/vala/vapi/libxfce4ui-2.vapi
/usr/share/xfce4/vendorinfo
2. some packages missing
$ tazpkg -s xfc
Search result for "xfc"
==================================================================
Installed packages
---------------------------------------------------------------
elementary-xfce 0.17 misc
libxfce4ui 4.18.1 misc
libxfce4util 4.18.1 misc
xfce4-appfinder 4.18.0 misc
xfce4-clipman-plugin 1.6.2 misc
xfce4-dev-tools 4.18.0 misc
xfce4-panel 4.18.1 misc
xfce4-panel-profiles 1.0.13 misc
xfce4-power-manager 4.18.0 misc
xfce4-pulseaudio-plugin 0.4.5 misc
xfce4-screensaver 4.16.0 misc
xfce4-screenshooter 1.10.3 misc
xfce4-session 4.18.0 misc
xfce4-settings 4.18.1 misc
xfce4-systemload-plugin 1.3.2 misc
xfce4-taskmanager 1.5.5 misc
xfce4-terminal 1.0.4 misc
xfce4-weather-plugin 0.11.0 misc
xfce4-whiskermenu-plugin2.6.2 misc
xfconf 4.18.0 misc
==================================================================
20 installed packages found for "xfc"
Available packages
--------------------------------------------------------------
libxfce4ui 4.18.0-x86_64 x-window
libxfce4ui-dev 4.18.0-x86_64 development
libxfce4util 4.18.0-x86_64 x-window
libxfce4util-dev 4.18.0-x86_64 development
libxfconf 4.18.0-x86_64 development
xfce4 4.18.0-x86_64 meta
xfce4-appfinder 4.18.0-x86_64 x-window
xfce4-dev-tools 4.18.0-x86_64 development
xfce4-icon-theme 4.4.3-x86_64 misc
xfce4-panel 4.18.0-x86_64 x-window
xfce4-panel-dev 4.18.0-x86_64 development
xfce4-session 4.18.0-x86_64 x-window
xfce4-session-dev 4.18.0-x86_64 x-window
xfce4-settings 4.18.1-x86_64 x-window
xfce4-slitaz-config 0.1-x86_64 misc
xfce4-taskmanager 1.5.5-x86_64 x-window
xfconf 4.18.0-x86_64 x-window
xfconf-dev 4.18.0-x86_64 development
==================================================================
18 available packages found for "xfc"
3. Can't fix many errors
[attachment=51407,3337]
[attachment=51407,3339]
4. Now studying.
suspend - resume
Discharging (89%, 109 hours 49 minutes)
slackware64-live-xfce
https://forum.slitaz.org/topic/slitaz-x86_64-asus-m3400qa/page/2#post-51215
https://forum.slitaz.org/topic/slitaz-x86_64-asus-m3400qa/page/2#post-51230
Offline
[ Generated in 0.019 seconds, 7 queries executed - Memory usage: 1.65 MiB (Peak: 1.77 MiB) ]