Page 1 of 1
Compiling module from source - make gives error
Posted: 29 Aug 2022, 00:50
by Rava
The info is in post #2 by
ncmprhnsbl
_______________________________________
I am running x86-64 Port 5.0
beny wrote: ↑28 Aug 2022, 15:49
guest@porteus:~$ ls -l /var/log/packages/ | grep -i pytho
-rw-r--r-- 1 root root 26514 Jun 30 07:14 python-setuptools-57.5.0-x86_64-2
-rw-r--r-- 1 root root 7723 Jun 30 07:06 python-urllib3-1.26.8-x86_64-1
-rw-r--r-- 1 root root 540729 Jun 30 07:06 python3-3.9.12-x86_64-1_slack15.0
-rw-r--r-- 1 root root 1730 Jun 30 07:14 python3-pythondialog-3.5.3-x86_64-1_ncm
Code: Select all
root@porteus:~# cat /etc/slackware-version
Slackware 15.0
root@porteus:~# cat /etc/porteus/*
001-core.xzm:20220723
002-xorg.xzm:20220723
002-xtra.xzm:20220630
003-xfce4.xzm:20220209
initrd.xz:20201102
root@porteus:~# ls -l /var/log/packages/ | grep -i pytho
root@porteus:~#
One would presume I have no python… but I do:
Code: Select all
root@porteus:~# python --version
Python 3.9.12
For me, /var/log/packages/ is empty - unless I activated extra modules, currently I have this is there:
Code: Select all
root@porteus:~# ls -o /var/log/packages/
-rw-r--r-- 1 root 6715 2015-02-27 11:01 fbreader-0.12.10-x86_64-2ponce
-rw-r--r-- 1 root 14099 2015-01-05 05:29 geany-1.23.1-x86_64-1gv
Compiling module from source - make gives error
Posted: 29 Aug 2022, 02:36
by ncmprhnsbl
Rava wrote: ↑29 Aug 2022, 00:50
For me, /var/log/packages/ is empty - unless I activated extra modules, currently I have this is there:
reason the /var/log/packages/ is empty would be that your older modules ie. fbreader and geany have overwritten the symlink(/var/log/packages/) that links to /var/lib/pkgtools/packages ..
which has been the slackware package database directory for at least a couple of years
[INFO] Why is my /var/log/packages/ empty but for few non-standard module info?
Posted: 29 Aug 2022, 04:34
by Rava
ncmprhnsbl wrote: ↑29 Aug 2022, 02:36
reason the /var/log/packages/ is empty would be that your older modules ie. fbreader and geany have overwritten the symlink(/var/log/packages/) that links to /var/lib/pkgtools/packages ..
which has been the slackware package database directory for at least a couple of years
Sounds like the very reason. Both are older modules I keep cause they work and especially fbreader is able to be with small minimal dependency, and I have no need for features never versions supply.
Reason must be they are so outdated that they use the old /var/log/packages/ as folder and not the new /var/lib/pkgtools/packages
I presume when creating a module - always use /var/lib/pkgtools/packages as the path for the package info, even when it's self-compiled or from a non Slackware source, cause /var/lib/
pkgtools/packages is the path for the package info.