Hi,
I patch 5.10.221 for rtw88, thanks mageia bug tracker and realtek for work :).
Check to build orca and test on my EeePC
[Current version dev thread] - Usage of SliTaz 4.0 / rolling
(485 posts) (13 voices)- Started 1 year ago by shann
- Latest reply from shann
- This topic is not a support question
-
shann
offlineAdministratorPosted 4 months ago # -
shann
offlineAdministratorNeed to investigate for Orca, try to use 2.24 (same match gtk+ we have), implied build other packages
yelp-xsl / yelp-tools
dotconf / dotconf-dev
espeak / espeak-dev (i use espeak-ng)
ORBit2 / ORBit2-dev
GConf / GConf-dev
esound / esound-dev
gnome-mime-data
gnome-vfs / gnome-vfs-dev
libbonobo / libbonobo-dev
libgnome / libgnome-dev
gnome-python / gnome-python-dev
pyorbit
[at-spi (1.32) / at-spi-python (1.91.92) ]But not work as expected issue about Atspi
No module named gi.repository.After search think related to pygobject we build with
--disable-introspection, try with--enable-introspectionand use pycairo118-dev but issue :pygi-info.c:165:14: error: 'GI_INFO_TYPE_ERROR_DOMAIN' undeclared (first use in this function); did you mean 'GI_INFO_TYPE_UNRESOLVED'?
case GI_INFO_TYPE_ERROR_DOMAIN:
pygi-info.c:484:22: error: 'GI_INFO_TYPE_ERROR_DOMAIN' undeclared (first use in this function); did you mean 'GI_INFO_TYPE_UNRESOLVED'?
case GI_INFO_TYPE_ERROR_DOMAIN:
pygi-info.c:863:26: error: 'GI_INFO_TYPE_ERROR_DOMAIN' undeclared (first use in this function); did you mean 'GI_INFO_TYPE_UNRESOLVED'?
case GI_INFO_TYPE_ERROR_DOMAIN:Maybe need to use another version or branch 3.x
Posted 4 months ago # -
Ceel
offlineAdministratorPleasure to announce that i patch cookutils, tazpkg 944, now it's work well with x86_64 :).
Also test on my eeepc 1215N, work like a charm.Unfortunately, that's not the case for me for
cookutils:(
Generated a chroot withtazdev -gc, OK
Initialised the chroot withcook setup, OK
Tryied to cook a package,ERROR: unknown dep <pkg>when cook check the receipt; looks likecookdoesn't findpackages.list. Yet,tazpkg -gi <pkg>works fine in the chroot.
I generated a second wok, same.
I spent a few hours to try to find from where did the problem come but I'm far to have your skill :/Posted 3 months ago # -
shann
offlineAdministratorHi Ceel.
hmm sad to read this :(
Below that i do (i use current64_test, always current64 env) :
root@slitaz:~# tazdev gen-chroot current64_test current64 --mirror=http://people.slitaz.org/~shann/slitaz-current64-stuff/packages
Generating new chroot in: /home/slitaz/current64_test/chroot
=======================================================================================================================
Mirror URL: people.slitaz.org/~shann/slitaz-current64-stuff/packages [ Fait ]
Installing: slitaz-base-files [ Fait ]
Installing: busybox [ Fait ]
Installing: cookutils [ Fait ]
Installing: tazpkg [ Fait ]
Installing: lzma [ Fait ]
mkdir: can't create directory '/home/slitaz/current64_test/chroot/etc': Le fichier existe
Creating resolv.conf... [ Fait ]
Creating TZ... [ Fait ]
Restoring host packages list... [ Fait ]
=======================================================================================================================
Ready to chroot with: tazdev -c current64_testroot@slitaz:~#
Create symlink need before chroot
root@slitaz:~# ln -s lib /home/slitaz/current64_test/chroot/lib64
root@slitaz:~# ln -s lib /home/slitaz/current64_test/chroot/usr/lib64Enter chroot and run
cook setupOK
Edit /etc/slitaz/cook.conf to changeCFLAGS="-march=$ARCH -Os -pipe -fomit-frame-pointer"toCFLAGS="-march=nocona -Os -pipe -fomit-frame-pointer -fPIC"Sync my wok and run cook <pkg> (exemple with mpfr need gmp-dev)
You can download tarball directly and extract it to /home/slitazroot@slitaz:/# wget https://people.slitaz.org/~shann/slitaz-current64-stuff/wok-20240725.tar.gz
root@slitaz:/# tar xf wok-20240725.tar.gz -C /home/slitazroot@slitaz:/home/slitaz/wok# cook mpfr
nodev aufs
Setup aufs chroot...Cook: mpfr 4.1.0
=======================================================================================================================
QA: checking package receipt...
Checking build dependencies...
Installing (web/cache): gmp-dev-6.2.1-x86_64
Extracting source archive "mpfr-4.1.0.tar.xz"
Executing: compile_rules
CFLAGS : -march=nocona -Os -pipe -fomit-frame-pointer -fPIC
configure: loading site script /etc/slitaz/cook.site
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... ./install-sh -c -d
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether to enable maintainer-specific portions of Makefiles... yes
checking build system type... x86_64-slitaz-linux-gnu
checking host system type... x86_64-slitaz-linux-gnu
checking for grep that handles long lines and -e... /bin/grep
[...]
make[1]: Entering directory '/home/slitaz/wok/mpfr/source/mpfr-4.1.0'
make[2]: Entering directory '/home/slitaz/wok/mpfr/source/mpfr-4.1.0'
make[2]: Nothing to be done for 'install-exec-am'.
./install-sh -c -d '/home/slitaz/wok/mpfr/install/usr/share/doc/mpfr'
./install-sh -c -d '/home/slitaz/wok/mpfr/install/usr/lib/pkgconfig'
./install-sh -c -d '/home/slitaz/wok/mpfr/install/usr/share/doc/mpfr/examples'
/usr/bin/install -c -m 644 mpfr.pc '/home/slitaz/wok/mpfr/install/usr/lib/pkgconfig'
/usr/bin/install -c -m 644 examples/ReadMe examples/can_round.c examples/divworst.c examples/rndo-add.c examples/sample.c examples/threads.c examples/version.c '/home/slitaz/wok/mpfr/install/usr/share/doc/mpfr/examples'
/usr/bin/install -c -m 644 AUTHORS BUGS COPYING COPYING.LESSER NEWS TODO '/home/slitaz/wok/mpfr/install/usr/share/doc/mpfr/.'
make[2]: Leaving directory '/home/slitaz/wok/mpfr/source/mpfr-4.1.0'
make[1]: Leaving directory '/home/slitaz/wok/mpfr/source/mpfr-4.1.0'
==============================================================================================================================================================================================================================================
Build dependencies to remove: 1
Removing: gmp-devPack: mpfr 4.1.0-x86_64
=======================================================================================================================
Executing: genpkg_rules
Copying files... Done
Copying "receipt"... Done
Copying "description.txt"... Done
Executing strip on all files... Done
Time: 0.45s. Size: 2715488 B -> 2666752 B. Save: 48 KB.
Creating the list of files... Done
Creating md5sum of files... Done
Compressing the FS... Done
Updating receipt sizes... Done
Creating full cpio archive... Done
Restoring original package tree... Done
QA: checking for empty package... Done
=======================================================================================================================
Package "mpfr-4.1.0-x86_64.tazpkg" createdSummary for: mpfr 4.1.0
=======================================================================================================================
Source dir : 22.9M
Src file : mpfr-4.1.0.tar.xz
Src size : 1.5M
Produced : 4.1M
Packed : 2.6M
Compressed : 1.2M
Files : 3
Cook time : 17s
Cook date : 2024-07-25 15:22
Host arch : x86_64
=======================================================================================================================Leaving aufs chroot...
Updating x86_64 chroot environment...Installation of package "mpfr"
=======================================================================================================================
C library for multiple-precision floating-point computations.
-----------------------------------------------------------------------------------------------------------------------
Copying package... Done
Extracting package... Done
Remember modified packages... Done
Installing package... Done
Removing all tmp files... Done
=======================================================================================================================
Package "mpfr" (4.1.0) is installed.root@slitaz:/home/slitaz/wok#
Posted 3 months ago # -
Ceel
offlineAdministratorReally strange. That's exactly what I do, excepted I never sync the wok because I don't need to load all the receipts and stuff/
I'll give a look again at it later, a rainy day ;)
We have wait for the sun so loooong.Posted 3 months ago # -
Ceel
offlineAdministratorHi shann,
Well, the sun didn't bright a long time... :(
What do you mean by "always current64 env"? You are working from your full x86_64 ISO, right?
I did these tests :
- change the name of the filepackages.listin/var/lib/tazpkgmakescookreturns an errorfgrep: /var/lib/tazpkg/packages.list: No such file or directorysocookfinds the file.
- runfgrep gtk+-dev-2.24.33-x86_64 /var/lib/tazpkg/packages.listin a terminal returns
gtk+-dev-2.24.33-x86_64
butcookcontinue to fail when checking build dependencies...Posted 3 months ago # -
shann
offlineAdministratorHi Ceel,
yes but it's only for this week-end, normally next week will be sunny and hot 30° in average.
For "always current64 env", infact i'm running on my core x86_64, i would say, i have current64 chroot env for build.
Really strange, i do test on qemu with slitaz-current-base64 from my space, it's work also.
I do test from current (32 bits), of course generate chroot with tazdev not work but think expected.Posted 3 months ago # -
Ceel
offlineAdministratorI tryed to be as stupid as the computer:
cookdoes not find any build dependencies inpackages.listbut maybe it does not search what I believe it searches...
I modify the line 656_ 'ERROR: unknown dep "%s"' "$i"in_ 'ERROR: unknown dep "%s"' "$i-$vers$arch"in thecookscript and now:
Checking build dependencies... ERROR: unknown dep "gtk+-dev--x86_64"Seems the culprit is
$versbut as my knowledge in shell scripting is just a little higher that my knowledge in quantum physics i still didn't find where the problem is ;)Posted 3 months ago # -
shann
offlineAdministratorHi Ceel,
So really strange, i check cook script few line before Error line, we set
vers:line 632, we get VERSION from receipt in wok and set
vers
line 635, if not found we check on /var/lib/tazpkg/packages.info to setvers
line 653, if not found locally, we check if in mirror (check on /var/lib/tazpkg/packages.list)It's strange that after you create chroot, call
cook setup, don't found package in your case gtk+-dev.Infact when begin work on x86_64, i have similar issue but at beginning, now iso and repo have already tazpkg fix since.
Posted 3 months ago # -
Ceel
offlineAdministratorHi shann,
Yes. Seems the issue is at line 635: this morning I replaced it with
vers="2.24.33"(I'm trying to build libxfce4util package that needs only gtk+-dev, intltool and pkg-config as build dependencies, and intltool and pkg-config are already in the chroot); cook installed gtk+-dev and builtlibxfce4util.
Trying to get version manually from aawkcommand in a terminal works too, but I did it in the host. I'll try in the chroot but I don't think I can do some tests tomorrow.
Another test I did was to cook from the host (frugal installation):
mkdir /home/slitaz cook setupthen changed
CFLAGSin the cook script, "installed" libxfce4util receipt in the wok and
cook libxfce4util
same issue,ERROR: unknown dep "gtk+-dev--x86_64":(
So, it's not a problem with the chroot.
Did the same test booting from ISO but ISO you built on 04/07/24, but you wrote "when begin work on x86_64, i have similar issue but at beginning, now iso and repo have already tazpkg fix since"...
Maybe I should download the last ISO to do the test again.Posted 3 months ago # -
shann
offlineAdministratorHi Ceel,
I check history post, on begin July i rebuild iso with tazpkg 944 after fix issue.
https://forum.slitaz.org/topic/usage-of-slitaz-40-rolling/page/29#post-52454
Pleasure to announce that i patch cookutils, tazpkg 944, now it's work well with x86_64 :).Maybe you have issue with it, you can use latest iso to be sure you use same version.
Actual iso build it on July 11th.Posted 3 months ago # -
Ceel
offlineAdministratorHi shann,
Too hot to work outdoor, so back to my issue and then:
cookscript, line 635vers=$(awk -F$'\t' -vp="$i" '$1==p{print $2; quit}' $PKGS/packages.info 2> /dev/null)Variable PKGS is defined in
cook.confasPKGS="$SLITAZ/packages"withSLITAZ="/home/slitaz"
IMHO we should use$DB(cook.conf) or$PKGS_DB (slitaz.conf) both defined as="/var/lib/tazpkg"`\o/ ???
outoff topic: how can I disable my touchpad?
Posted 3 months ago # -
gibor
offlineModeratoroutoff topic: how can I disable my touchpad?
Hi Ceel, I solved it this way:
identify the touchpad IDxinput list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ PS/2 Mouse id=10 [slave pointer (2)]
⎜ ↳ AlpsPS/2 ALPS GlidePoint id=11 [slave pointer (2)]
⎜ ↳ USB Optical Mouse id=12 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Power Button id=8 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=9 [slave keyboard (3)]in my case it is (AlpsPS/2 ALPS GlidePoint id=11)
to disable the touchpad
xinput set-prop 11 "Device Enabled" 0or to re-enable it touchpad
xinput set-prop 11 "Device Enabled" 1To have the touch function in case of the mouse is unplugged, I made a script inserted in the auto run preferences
which should be easy enough for anyone to adapt.if [ "$(xinput list | grep "USB Optical Mouse")" != "" ];then xinput set-prop $(xinput list | grep AlpsPS | sed 's/.*=//' | sed 's/\[slave.*//') "Device Enabled" 0; else xinput set-prop $(xinput list | grep AlpsPS | sed 's/.*=//' | sed 's/\[slave.*//') "Device Enabled" 1; fi
Posted 3 months ago # -
shann
offlineAdministratorHi Ceel, gibor,
hmm good catch, need check, normally cook use wok as priority (/home/slitaz/packages) before mirror (/var/lib/tazpkg).
Of course that not explain why when test work without issue (with iso and tazdev)
Thanks gibor for this tips :).
Posted 3 months ago # -
Ceel
offlineAdministratorCiao gibor,
Perfetto! È esattamente questo che volevo.
Non ne potevo più vedere il cursor saltare di una finestra all'altra ogni volta che il mio braccio passa sopra il touchpad.
Grazie mille!!!Posted 3 months ago #
Reply »
You must log in to post.
