On 26.01.22 22:30, gene heskett wrote:
On Wednesday, January 26, 2022 3:49:58 PM EST Steffen Möller wrote:
On 26.01.22 02:27, gene heskett wrote:
Greetings all;
I built a fresh pull of master earlier today, which makes installable
debs. I normally run this shell script to install them, and on buster
it Just Works.
And that is how things should also behave on Bullseye. Let's find out
what is going wrong.
But, now I have succeeded in getting a raspios bullseye to run on a
5.16.2-rt19-rt19-v7l+ #3 SMP PREEMPT_RT kernel, and that first boot
updated about 2gigs of stuff. There is about 130 pkgs to update.
I have not run bullseye on a Raspberry, yet. I would however indeed go
and update everything.
sudo apt-get -u dist-upgrade
should get you there.
But I am already there. From my running rpi4 a uname -a:
Linux rpi4 5.16.2-rt19-rt19-v7l+ #3 SMP PREEMPT_RT Tue Jan 25 01:14:16
EST 2022 armv7l GNU/Linu
I have installed about a gig of stuff dpkg
complains about but have not been able to get a working install.
yet...
The remaining errors are:
dpkg: dependency problems prevent configuration of linuxcnc-uspace:
linuxcnc-uspace depends on libboost-python1.67.0; however:
Package libboost-python1.67.0 is not installed.
linuxcnc-uspace depends on libpython3.7 (>= 3.7.0); however:
Package libpython3.7 is not installed.
linuxcnc-uspace depends on python3 (<< 3.8); however:
Version of python3 on system is 3.9.2-3.
linuxcnc-uspace depends on python3.7-tk; however:
Package python3.7-tk is not installed.
linuxcnc-uspace depends on python3.7-numpy | python-numpy; however:
Package python3.7-numpy is not installed.
Package python-numpy is not installed.
This raised some eyebrows on my end. Python 3.7 is history and
dependencies are on Python3. A grep in the debian directory of what I
have checked out from master does not have any notion of "3.7" in the
debian folder. And python-numpy (without the "3") is a Python2 version,
which is no longer needed.
But newer versions of all the above are all installed.
I do not know at this stage if I have enough to rebuild them as yet.
The debhelper suite is not yet installed.
So I need to see the /e/a/sources.list.d/linuxcnc.list file for
bullseye so I can see if those .debs will install.
Something is off with your package. Please have a second look at when
this package was built. Maybe it is an old one that was carried over
from your past with Buster?
They all were built on thst rpi4 earlier yesterday while an uptodate
buster was running.
That might explain it. My hunch is that at the time the dependencies
were determined there was an earlier version of the said library installed.
For C libraries there is a mechanism to automagically find the right
"soname"
(which basically is a name for the ABI, part of that soname is the
soversion)
and this may indeed have anchored Python3.7 in your package, which was
then updated to 3.9 or so.
I build all the makefiles say to build but only
install the english stuff, but the buster built uspace stuff won't
install on bullseye, with the above errors shown. So I guess I move them
to a buster subdir to protect them from being overwritten, and see how
far I get with a bullseye build. FWIW, they did install on buster, thats
part of my make-all.sh script.
Would you be prepared to try again? From scratch starting with a
checkout of the master branch?
Its an uptodate a/o a yesterday mornings pull & checkout, both master and
master-gtk s/b current as of then.
Please try again, even if it hurts a bit. I am confident that it will work.
I have access to an odroid on which I can otherwise prepare an ARM64
package for you.
Thank you Stephen. I'll advise if I find anything foobar as I go charging
off into new territory.
Take care and stay well.
So do you, please!
Steffen
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
