SliTaz Forum
You are not logged in.
Need 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 [c]No module named gi.repository[/c].
After search think related to pygobject we build with [c]--disable-introspection[/c], try with [c]--enable-introspection[/c] and 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
Offline
Pleasure 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 [c]cookutils[/c] 
Generated a chroot with [c]tazdev -gc[/c], OK
Initialised the chroot with [c]cook setup[/c], OK
Tryied to cook a package, [c]ERROR: unknown dep <pkg>[/c] when cook check the receipt; looks like [c]cook[/c] doesn't find [c]packages.list[/c]. Yet, [c]tazpkg -gi <pkg>[/c] 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 
Offline
Hi 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_test
root@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/lib64
Enter chroot and run [c]cook setup[/c] OK
Edit /etc/slitaz/cook.conf to change [c]CFLAGS="-march=$ARCH -Os -pipe -fomit-frame-pointer"[/c] to [c]CFLAGS="-march=nocona -Os -pipe -fomit-frame-pointer -fPIC"[/c]
Sync my wok and run cook <pkg> (exemple with mpfr need gmp-dev)
You can download tarball directly and extract it to /home/slitaz
root@slitaz:/# wget https://people.slitaz.org/~shann/slitaz-current64-stuff/wok-20240725.tar.gz
root@slitaz:/# tar xf wok-20240725.tar.gz -C /home/slitaz
root@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-dev
Pack: 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" created
Summary 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#
Offline
Really 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.
Offline
Hi 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 file [c]packages.list[/c] in [c]/var/lib/tazpkg[/c] makes [c]cook[/c] returns an error [c]fgrep: /var/lib/tazpkg/packages.list: No such file or directory[/c] so [c]cook[/c] finds the file.
- run [c]fgrep gtk+-dev-2.24.33-x86_64 /var/lib/tazpkg/packages.list[/c] in a terminal returns
[c]gtk+-dev-2.24.33-x86_64[/c]
but [c]cook[/c] continue to fail when checking build dependencies...
Offline
Hi 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.
Offline
I tryed to be as stupid as the computer: [c]cook[/c] does not find any build dependencies in [c]packages.list[/c] but maybe it does not search what I believe it searches...
I modify the line 656 [c]_ 'ERROR: unknown dep "%s"' "$i"[/c] in [c]_ 'ERROR: unknown dep "%s"' "$i-$vers$arch"[/c] in the [c]cook[/c] script and now:
[c]Checking build dependencies...
ERROR: unknown dep "gtk+-dev--x86_64"[/c]
Seems the culprit is [c]$vers[/c] but 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
Offline
Hi Ceel,
So really strange, i check cook script few line before Error line, we set [c]vers[/c] :
line 632, we get VERSION from receipt in wok and set [c]vers[/c]
line 635, if not found we check on /var/lib/tazpkg/packages.info to set [c]vers[/c]
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 [c]cook setup[/c], 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.
Offline
Hi shann,
Yes. Seems the issue is at line 635: this morning I replaced it with [c]vers="2.24.33"[/c] (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 built [c]libxfce4util[/c].
Trying to get version manually from a [c]awk[/c] command 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):
[c]mkdir /home/slitaz
cook setup[/c]
then changed [c]CFLAGS[/c] in the cook script, "installed" libxfce4util receipt in the wok and
[c]cook libxfce4util[/c]
same issue, [c]ERROR: unknown dep "gtk+-dev--x86_64"[/c]
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.
Offline
Hi 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
[c]Pleasure to announce that i patch cookutils, tazpkg 944, now it's work well with x86_64 .[/c]
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.
Offline
Hi shann,
Too hot to work outdoor, so back to my issue and then:
[c]cook[/c] script, line 635
[c]vers=$(awk -F$'\t' -vp="$i" '$1==p{print $2; quit}' $PKGS/packages.info 2> /dev/null)[/c]
Variable PKGS is defined in [c]cook.conf[/c] as [c]PKGS="$SLITAZ/packages"[/c] with [c]SLITAZ="/home/slitaz"[/c]
IMHO we should use [c]$DB[/c] (cook.conf) or [c]$PKGS_DB (slitaz.conf) both defined as[/c]="/var/lib/tazpkg"`
\o/ ???
outoff topic: how can I disable my touchpad?
Offline
outoff topic: how can I disable my touchpad?
Hi Ceel, I solved it this way:
identify the touchpad ID
xinput 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" 0
or to re-enable it touchpad
xinput set-prop 11 "Device Enabled" 1
To 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
Offline
Hi 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 .
Offline
Ciao 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!!!
Offline
Ciao Ceel, Shann,
Di niente, feci quella soluzione anch'io per gli stessi motivi :-)
Offline
Hi shann,
I booted from ISO 20240711 and didn't change anything;
created a chroot and created symlinks [c]lib64[/c];
entered in the chroot;
setup the wok;
modified [c]CFLAGS[/c];
create dir [c]/home/slitaz/wok/libxfce4util[/c];
copyied the [c]receipt[/c] in it;
then [c]cook libxfce4util[/c]
and same issue
[c]Checking build dependencies...
ERROR: unknown dep "gtk+-dev"[/c]
I was quite sure of this because
- tazdev creates the chroot, and
- cook installs packages
from the repo so from the last build of the packages.
I had a look in the [c]cook[/c] script in my Rolling's chroot; line 635 is exactly the same.
I don't understand how [c]cook[/c] can find the version of a package in a file that does NOT exist.
We agree that [c]$PKGS/packages.info[/c] is [c]/home/slitaz/packages/packages.info[/c], right?
But [c]/home/slitaz/packages[/c] contains only the packages that have been cooked, no [c]packages.info[/c] here. Where am I wrong?
Offline
Hi Ceel,
hmm think found issue.
I boot qemu with base 20240711
1/ create chroot with tazdev
2/ adjust symlink for lib64
3/ run cook setup
4/ adjust cook.conf for CFLAGS
Instead of extract wok, i extract it to /home/slitaz/wok-current and create an empty /home/slitaz/wok, pick up libxfce4util folder on wok.
Run [c]cook libxfce4util[/c]
first failed about HOST_ARCH=i486, adjust receipt to have both arch [c]HOST_ARCH="i486 x86_64"[/c]
Run [c]cook libxfce4util[/c]
failed because don't find gtk+-dev <= here because try to fetch version from wok.
I put gtk+-dev folder to wok.
Run [c]cook libxfce4util[/c]
failed again complain about gtk+ not found <= because gtk+ not in wok.
If i setup $PKGS to $DB on line 635, work without issue.
I build atk/atk-dev, and it's ok, cook use my local atk/atk-dev from /home/slitaz/packages and other from repo.
In case good catch, if all packages not in wok, cook have race condition to found version
Offline
I don't understand how [c]cook[/c] can find the version of a package in a file that does NOT exist.
I think I've the answer: it doesn't find.
My 2 pence that in Rolling [c]$vers[/c] is also unset (try [c]cook libxfce4util --debug[/c] to check).
But this has no incidence because for i486, [c]$arch[/c] is unset too. So when [c]cook[/c] searches for the dep in the repo: [c]if fgrep -q $i-$vers$arch $root$DB/packages.list[/c] it looks for [c]$i-[/c] and it finds it whatever the version.
Offline
Hi shann,
[c]tazpkg -lf <pkg_name>[/c] returns the list that a package installs.
In current x86_64 the command returns the list only if the package is installed, if its not:
[c]tazpkg -lf cups
Installed files by "cups"
================================================================================
================================================================================
0 files[/c]
(boot from ISO Base64 2024/07/11).
Current x86_64 always boots with the max brighteness (at least on my Lenovo).
[*]If the power adaptator is plugged, when I switch it off, the screen switches in dark mode (eco, +1!); but it remains in dark mode when I switch the adaptator on.
[*]If the adaptator was off/unplugged at boot, when I switch it on, the screen switches also in dark mode.
It seems the screen switches in eco mode at the first change of the power line and the stays in this mode. Just for information, not a problem for me, on the contrary, dark mode is better for me
Offline
Hi Ceel,
Shit happen, check with current (32bits), it's ok, and infact current64 nothing.
Found issue,when i build on my current64 chroot, i clean wok before save it and generate pkgdb.
Side effect in case
root@slitaz:~# lzcat /var/lib/tazpkg/files.list.lzma | awk -F':' '{print $1}' | sort -u
GConf
GConf-dev
ORBit2
ORBit2-dev
broadcom-wl64
gmtp
iptables
iptables-dev
linux64-aufs
root@slitaz:~#
For brightness, maybe miss think for acpi on kernel.
Offline
Hi Ceel,
I have rebuild all wok, [c]tazpkg -lf <package>[/c] work again, but see that [c]tazpkg -sf[/c] seem not work properly or miss think .
Exemple search libc.so.6 it's ok.
root@slitaz:~# tazpkg -sf libc.so.6
Search result for file "libc.so.6"
======================================
Package glibc-base:
/lib/libc.so.6
======================================
1 file
root@slitaz:~#
root@slitaz:~# tazpkg -sf cupsd
Search result for file "cupsd"
======================================
======================================
0 file
root@slitaz:~#
root@slitaz:~# tazpkg -lf cups | grep cupsd
/etc/cups/cupsd.conf
/etc/cups/cupsd.conf.default
/etc/init.d/cupsd
/usr/sbin/cupsd
/usr/sbin/cupsdisable
root@slitaz:~#
Offline
Hi shann,
Long time I didn't come on the forum.
Strange behaviour of [c]cook setup[/c] in Current x86_64, [c]linux64-aufs[/c] is not installed; below, extract of my chroot [c]tazpkg.log[/c]:
[c]...
2024-08-16 10:34:13 - Installed - bzip2 (1.0.8) - 30d28e906f5ac5cc5e98709d8747b88a
2024-08-16 10:34:14 - Installed - aufs (20220912) - d2de85799ef638241a2f8807e227c75c
2024-08-16 10:34:14 - Installed - aufs-utils (20230814) - 3ab03f0d2a79e3edddf438dfd7c320a0
2024-08-16 10:34:15 - Installed - syslinux (4.06) - fcec87280d7091a6570459d856d2e98f
...[/c]
However, [c]tazpkg info aufs[/c] returns
Package : aufs
State : installed package
Version : 20220912
Category : base-system
Short desc : aufs5 kernel module
Depends : linux64-aufs
Web site : https://aufs.sf.net/
Size : 20K/48K
I had a look at the [c]aufs[/c] receipt:
...
case $ARCH in
i?86)
WANTED="linux-aufs"
DEPENDS="linux-aufs" ;;
x86_64)
WANTED="linux64-aufs"
DEPENDS="linux64-aufs" ;;
esac
...
shouldn't there be also "[c];;[/c]" at the end of the [c]WANTED=[/c] lines?
Offline
Hi shann...
I think "case $ARCH in" for "/usr/bin/cook that depend on /etc/slitaz/cook.conf" for "BUILD_DEPENDS" in receipt
and "case $SLITAZ_ARCH in" for /usr/bin/tazpkg that depend on /etc/slitaz/slitaz.conf for "DEPENDS" in receipt
Offline
[ Generated in 0.019 seconds, 7 queries executed - Memory usage: 1.64 MiB (Peak: 1.77 MiB) ]