Gene, there are no buildbots for Bookworm (or Bullseye for that matter). The Bookworm package is quite old (Feb 2023 I think) So I think you have no choice but to build from source so it may not matter which OS you use. The ARM64 support is really spotty and while there are a few unofficial images, you have no idea what they are or how old they are. I outlined a known working solution using bookworm http://linuxcnc.org/docs/2.9/html/getting-started/getting-linuxcnc.html Going this way actually shortens the dependency list a lot when you build from source.
However the way you work, I would explore building the Raspberry pi Cross compiler on a X86 machine which outputs an image file you burn to the pi with the normal pi imager. I shared some links in an issue here https://github.com/LinuxCNC/linuxcnc/issues/2349 about this If you start with the upstream source and work through David Smiths git example, you will see how he patched for prempt_RT kernel and built Linuxcnc and ethercat via scripts. I link to the relevant file. I have done this and it works. Its just a bit old but it would be pretty easy to refresh it. I will have a go at this one day. My current project is a live build/installer for X86 machines using Bookworm and the buildbot debs. I got this working yesterday, it just needs a bit of rine tuning. Rod Webster *1300 896 832* +61 435 765 611 Vehicle Modifications Network www.vehiclemods.net.au On Sat, 19 Aug 2023 at 01:48, gene heskett <ghesk...@shentel.net> wrote: > On 8/18/23 10:09, gene heskett wrote: > > Several problems? this morning. > > 1. Used synaptic to fix broken-packages by removing my locally built > > linuxcnc-v2.10.0 pacakages. > > > > 1a. debians arm64 netinstall, put on an sd card doesn't even try to > > boot. Apparently no u-boot or miss-configured for a raspberry pi or a > > bananapi-m5. > > > > 2. Linuxcnc en docs could then be installed from the buildbot but > > linuxcnc-uspace had missing dependencies and would not install from the > > buildbot. > > > > 3. Made new .debs from this mornings git pull and installed them with > > dpkg -l, but dpkg claimed missing dependency's and would not finish the > > configuration. > > missing dependency's are: > > =========================== > > pi@rpi4:/media/pi/workspace $ sudo ./buster-lcnc-install.sh > > Selecting previously unselected package linuxcnc-uspace-dbgsym. > > (Reading database ... 422403 files and directories currently installed.) > > Preparing to unpack linuxcnc-uspace-dbgsym_2.10.0~pre0_armhf.deb ... > > Unpacking linuxcnc-uspace-dbgsym (1:2.10.0~pre0) ... > > Selecting previously unselected package linuxcnc-uspace-dev. > > Preparing to unpack linuxcnc-uspace-dev_2.10.0~pre0_armhf.deb ... > > Unpacking linuxcnc-uspace-dev (1:2.10.0~pre0) ... > > Selecting previously unselected package linuxcnc-uspace. > > Preparing to unpack linuxcnc-uspace_2.10.0~pre0_armhf.deb ... > > Unpacking linuxcnc-uspace (1:2.10.0~pre0) ... > > dpkg: dependency problems prevent configuration of linuxcnc-uspace: > > linuxcnc-uspace depends on python3-poppler-qt5; however: > > Package python3-poppler-qt5 is not installed. > > > > dpkg: error processing package linuxcnc-uspace (--install): > > dependency problems - leaving unconfigured > > dpkg: dependency problems prevent configuration of > linuxcnc-uspace-dbgsym: > > linuxcnc-uspace-dbgsym depends on linuxcnc-uspace (= 1:2.10.0~pre0); > > however: > > Package linuxcnc-uspace is not configured yet. > > > > dpkg: error processing package linuxcnc-uspace-dbgsym (--install): > > dependency problems - leaving unconfigured > > dpkg: dependency problems prevent configuration of linuxcnc-uspace-dev: > > linuxcnc-uspace-dev depends on linuxcnc-uspace (= 1:2.10.0~pre0); > > however: > > Package linuxcnc-uspace is not configured yet. > > > > dpkg: error processing package linuxcnc-uspace-dev (--install): > > dependency problems - leaving unconfigured > > Processing triggers for man-db (2.8.5-2) ... > > Processing triggers for libc-bin (2.28-10+rpt2+rpi1+deb10u1) ... > > Processing triggers for gnome-menus (3.31.4-3) ... > > Processing triggers for desktop-file-utils (0.23-4) ... > > Processing triggers for mime-support (3.62) ... > > Processing triggers for hicolor-icon-theme (0.17-2) ... > > Processing triggers for shared-mime-info (1.10-1) ... > > Errors were encountered while processing: > > linuxcnc-uspace > > linuxcnc-uspace-dbgsym > > linuxcnc-uspace-dev > > ======================= > > > > But it loads and apparently runs ok anyway!!!!! So I don't appear to be > > disabled. > > > > 4. figured it was probably time to update from 32 bit (armhf) buster to > > bookworm, but on arrival at raspios site, find its may '23 release is > > still bullseye. dl the 64bit desktop anyway. Put it on sd card. I can > > edit the card for network stuff etc even before 1st boot, but since its > > bullseye, linuxcnc hasn't arrived yet. > > > > 5. is it worth my time to do that and switch cards and try to build > > linuxcnc on bullseye? The last time I tried that, the python3 was too > > new so configure bailed out. I reported that 2 or 3 times here, long ago > > when bullseye was new, and was ignored. > > > > So I'm stuck all alone out here in left field and everyone has gone home > > for the rest of the month/year/whatever. > > > > Please advise. > > And I just made another discovery. My apron jog speed enable pushbuttons > have not beem working recently using the buildbot pkgs, but my locally > built debs are working as intended. That pushbutton status and handling > is all in hal, but the reporting to the screen so I'm advised of the > speed change is pyvcp. When it didn't work I was stuck in slow, both for > effect and on screen. That points at hal, but Beyond that, I have no info. > > Thanks. > > > > Cheers, Gene Heskett. > > Cheers, Gene Heskett. > -- > "There are four boxes to be used in defense of liberty: > soap, ballot, jury, and ammo. Please use in that order." > -Ed Howdershelt (Author, 1940) > If we desire respect for the law, we must first make the law respectable. > - Louis D. Brandeis > Genes Web page <http://geneslinuxbox.net:6309/> > > > > _______________________________________________ > Emc-developers mailing list > Emc-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-developers > _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
