kernel pae-2
kernel pae
Memory : 2961MB (384MB used)I also note to build kernel pae :)
Kernel : Linux 5.4.41-slitaz (x86_64)
Memory : 15788MB (706MB used)
Date/Time : Thu Jul 8 12:35:44 2021
Processor : 8x AMD Ryzen 7 5800H with Radeon Graphics Memory : 2961MB (384MB used) Operating System : Slitaz GNU/Linux current # free -m total used free shared buff/cache available Mem: 2891 355 1697 665 839 1784 Swap: 1445 0 1445
A PAE-enabled kernel should have more than 4GB RAM.
POSTED 31 MINUTES AGO #
kernel pae
Rebuild apps in progress.
I also note to build kernel pae :)
slitaz-x86_64 - ASUS Vivobook Pro 14 M3400QA
Kernel : Linux 5.4.41-slitaz (x86_64)
C Library : GNU C Library version 2.26 (stable)
C Compiler : GNU C Compiler version 7.3.0 (SliTaz64)Resolution : 2880x1800 pixels
Version : 1.19.3 (X.Org)
Name : M3400QA (ASUS)Summary
-------
-Computer-
Processor : 8x AMD Ryzen 7 5800H with Radeon Graphics
Memory : 15788MB (706MB used)
Operating System : SliTaz GNU/Linux
User Name : tux (SliTaz User)
Date/Time : Thu Jul 8 12:35:44 2021
https://forum.slitaz.org/topic/slitaz-x86_64-asus-m3400qa
ASUS Vivobook Pro 14 M3400QA
Processor AMD Ryzen™ 7 5800H processor 3.2GHz 8 cores
Graphics AMD Radeon™ Graphics
Display 14.0 inches, OLED, WQXGA+ (2880 x 1800) 16:10, 400nits,
DCI-P3: 100%, Pantone Validated
Memory 8GB DDR4 SO-DIMM x 2, Memory Max 16GB
Storage 512GB M.2 NVMe™ PCIe® 3.0 SSD
Network Wi-Fi 6(802.11ax)+Bluetooth 5.0 (Dual band) 2*2
华硕无畏 Pro14 锐龙版 (chinese)
https://www.asus.com.cn/Laptops/For-Home/VivoBook/Vivobook-Pro-14-M3400/techspec/
1. # tazpkg -gi slitaz-toolchain
....
Installation of package "slitaz-toolchain"
=================================================================================
SliTaz meta package to rebuild or install current toolchain.
---------------------------------------------------------------------------------
Copying package... [ Done ]
Extracting package... [ Done ]
Remember modified packages... [ Done ]
Installing package... [ Done ]
Removing all tmp files... [ Done ]
=================================================================================
Package "slitaz-toolchain" (6.0) is installed.
# gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/i486-slitaz-linux/8.3.0/lto-wrapper
Target: i486-slitaz-linux
Configured with: /home/slitaz/wok/gcc/source/gcc-8.3.0/configure --libexecdir=/usr/lib --enable-nls --enable-languages=c,c++,objc,fortran --enable-shared --with-system-zlib --enable-clocale=gnu --enable-objc-gc --enable-__cxa_atexit --enable-lto --enable-threads=posix --disable-bootstrap --with-pkgversion=SliTaz --build=i486-slitaz-linux --host=i486-slitaz-linux --with-tune=i486
Thread model: posix
gcc version 8.3.0 (SliTaz)
2.
# free -m
total used free shared buff/cache available Mem: 2891 355 1697 665 839 1784 Swap: 1445 0 1445
3. hardinfo
-Computer- Processor : 8x AMD Ryzen 7 5800H with Radeon Graphics Memory : 2961MB (384MB used) Operating System : Slitaz GNU/Linux current User Name : tux (SliTaz User) Date/Time : Sun Nov 26 02:55:08 2023 -Display- Resolution : 1920x1200 pixels OpenGL Renderer : Unknown X11 Vendor : (null) -Multimedia- Audio Adapter : HDA-Intel - HD-Audio Generic Audio Adapter : HDA-Intel - HD-Audio Generic Operating System ---------------- -Version- Kernel : Linux 4.19.298-slitaz (i686) Compiled : #4 SMP Fri Nov 17 15:16:46 Europe 2023 C Library : Unknown Default C Compiler : GNU C Compiler version 8.3.0 (SliTaz) Distribution : Slitaz GNU/Linux current -Current Session- Computer Name : slitaz User Name : tux (SliTaz User) Home Directory : /home/tux Desktop Environment : Unknown (Window Manager: Openbox) -Misc- Uptime : 53 minutes
Load Average : 0.02, 0.02, 0.00
https://forum.slitaz.org/topic/usage-of-slitaz-40-rolling/page/14#post-51807
Dynamic Loader
Normally tazweb has been compiled with libsoup248 / libwebkit and to avoid clash with libsoup / webkitgtk (webkit2gtk soon), each have own path (/usr/libsoup248, /usr/libwebkit).
And tazweb have LD_LIBRARY_PATH to use it.
With this command tazweb run :
LD_LIBRARY_PATH=/usr/libsoup248:/usr/libwebkit tazweb
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.
....
https://www.linuxfromscratch.org/lfs/view/11.2/chapter08/glibc.html#contents-glibc
https://forum.slitaz.org/topic/usage-of-slitaz-40-rolling/page/13#post-51793
receipt - mesa.SlackBuild
I begin stuff to ensure we have stable and recent version.
In case i compare current wok versions with Slackware 15.0, because it's more conservative in upgrade and keep security in mind.
For xorg stuff, i check also with 14.2 for proto packages (15.0 have 2021.5 metapackage)
On all packages build on current, we have 1018 it's same version (it's include also only slitaz pkg), 136 remain. Seem good point :)
40 UPDATED
24 SKIP because need major upgrade as Mesa / Xorg / GCC / Glibc / Kernel
72 need to check
Index of /slackware/slackware-15.0/source/x/mesa
Name Last modified Size Description Parent Directory - doinst.sh.gz 2018-12-07 20:28 388 get-mesa.sh 2015-12-11 04:09 720 mesa-21.3.5.tar.xz 2022-01-26 19:56 16M mesa-21.3.5.tar.xz.sig 2022-01-26 19:56 329 mesa-demos-8.4.0.tar.lz 2018-02-23 09:54 6.9M mesa.SlackBuild 2022-01-28 21:22 6.9K mesa.url 2010-10-01 06:23 78 patches-revert/ 2021-03-12 02:31 - patches/ 2021-10-15 19:57 - slack-desc 2019-09-25 21:15 814
https://slackware.nl/slackware/slackware-15.0/source/x/mesa/
https://forum.slitaz.org/topic/usage-of-slitaz-40-rolling/page/13#post-51792
tux@slitaz:~$ lsmodModule Size Used byipv6 213160 24ppdev 4154 0vmwgfx 115863 1ttm 50906 1 vmwgfxdrm_kms_helper 23610 1 vmwgfxdrm 161345 5 ttm,drm_kms_helper,vmwgfxe1000 78776 0intel_agp 7740 0parport_pc 14485 0intel_gtt 8322 1 intel_agpagpgart 17619 4 drm,ttm,intel_agp,intel_gtti2c_core 14640 2 drm,drm_kms_helperparport 21431 2 ppdev,parport_pcvideo 10751 0button 3289 0
slitaz-41 -- slim-cmake-lpthreads
The one for "-lpthreads" just accidentally happened to be the last one in the log...
Solution: go through the log from the top, identify the section with the configure checks, find the last configure check prior to the point, where CMake identifies failure and dumps its logs. You might also try so search for the text "Configuring incomplete, errors occurred!"
I fight with slim :/.
Issue with cmake build :
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.2")
-- Checking for one of the modules 'fontconfig'
CMake Error at /usr/share/cmake-3.22/Modules/FindPkgConfig.cmake:890 (message):
None of the required 'fontconfig' found
Call Stack (most recent call first):
cmake/modules/FONTCONFIGConfig.cmake:18 (pkg_search_module)
CMakeLists.txt:108 (find_package)FontConfig Found
PAM disabled
ConsoleKit disabled
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- Configuring incomplete, errors occurred!
Run Build Command(s):/usr/bin/make -f Makefile cmTC_88b6c/fast && /usr/bin/make -f CMakeFiles/cmTC_88b6c.dir/build.make CMakeFiles/cmTC_88b6c.dir/build
make[1]: Entering directory '/home/slitaz/wok/slim/source/slim-1.3.6/build/CMakeFiles/CMakeTmp'
Building C object CMakeFiles/cmTC_88b6c.dir/CheckFunctionExists.c.o
/usr/bin/cc -march=i486 -Os -pipe -fomit-frame-pointer -Wall -g -O2 -DCHECK_FUNCTION_EXISTS=pthread_create -o CMakeFiles/cmTC_88b6c.dir/CheckFunctionExists.c.o -c /usr/share/cmake-3.22/Modules/CheckFun
Linking C executable cmTC_88b6c
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_88b6c.dir/link.txt --verbose=1
/usr/bin/cc -march=i486 -Os -pipe -fomit-frame-pointer -Wall -g -O2 -DCHECK_FUNCTION_EXISTS=pthread_create -rdynamic CMakeFiles/cmTC_88b6c.dir/CheckFunctionExists.c.o -o cmTC_88b6c -lpthreads
/usr/bin/ld: cannot find -lpthreads
collect2: error: ld returned 1 exit status
make[1]: *** [CMakeFiles/cmTC_88b6c.dir/build.make:99: cmTC_88b6c] Error 1
make[1]: Leaving directory '/home/slitaz/wok/slim/source/slim-1.3.6/build/CMakeFiles/CMakeTmp'
make: *** [Makefile:127: cmTC_88b6c/fast] Error 2
https://forum.slitaz.org/topic/slitaz-development-strategy-direction/page/5#post-50768
I have c++ project that was smoothly running on a given machine, and now I am trying to compile it on another one with the same operating system (Xubuntu 14.04).
I've installed all the dependencies and I'am using cmake to build the project, although it stops with the following error:
Determining if the function pthread_create exists in the pthreads failed with the following output: ... /usr/bin/ld: cannot find -lpthreads
The problem was happening when running cmake. Though, in this case cmake was not the problem the error was silent and the -lpthreads related error/warning was the only thing being written to the cmake error log file, although that was not causing any issue. I've done a minimal version of the cmakelists.txt and started testing it line by line until I found which package was causing it to stop: finally I found it was a version mismatch...
Hint: search for the actual error message
Typically you'd look for the last error message. However, this (often useful) strategy in such cases leads astray.
What you are looking at is the
CMakeCache.txt, theCMakeOutput.logor theCMakeError.log. How comes? When some of the macros or tests in the configure phase fails, CMake "helpfully" dumps these files to the output. Unfortunately, these files can be thousands of lines long, and typically contain lots of "*** Error: xyz"entries, for various configure checks. The one for "-lpthreads" just accidentally happened to be the last one in the log...Solution: go through the log from the top, identify the section with the configure checks, find the last configure check prior to the point, where CMake identifies failure and dumps its logs. You might also try so search for the text "
Configuring incomplete, errors occurred!"Typically you'll either find a very precise actual error message there, or at least you find the name / path of the macro or function called last, and this allows you to pinpoint down what actually went wrong.
