Gene,
Great you are making progress.
Your scripts won't work as you refer to 32 bit armhf and this is 64bit
arm64
Also Buster uses Python 2.7 which was deprecated in Bullseye. Linuxcnc now
uses Python 3.11 and 2.7 is not available.
There should not be any missing dependencies to build linuxcnc as
Sorry gremlins got in
when you run the debian/configure script do it this way
cd ~/linuxcnc-dev/debian
./configure uspace no-docs
Rod Webster
*1300 896 832*
+61 435 765 611
Vehicle Modifications Network
www.vehiclemods.net.au
On Thu, 28 Sept 2023 at 06:23, Rod Webster wrote:
> Gene,
> Great
On 9/27/23 16:23, Rod Webster wrote:
Gene,
Great you are making progress.
Your scripts won't work as you refer to 32 bit armhf and this is 64bit
arm64
Also Buster uses Python 2.7 which was deprecated in Bullseye. Linuxcnc
now uses Python 3.11 and 2.7 is not available.
There should not be any
On Thu, 28 Sept 2023 at 00:41, Alec Ari via Emc-developers
wrote:
> Would anyone be able to test LinuxCNC against the changes I'll be making to
> RTAI? I can only test the sims, I don't have any actual CNC hardware
> available.
I can.
Do I need to re-build RTAI? My current git pull is master
Hi all,
Rene said I should switch RTAI to GNU11:
https://github.com/LinuxCNC/linuxcnc/commit/3d926d87f14ada9dea313c2989ee8f24f0e54e0c#commitcomment-128557906
I suppose the above commit could be reverted.
Would anyone be able to test LinuxCNC against the changes I'll be making to
RTAI? I can
Yes, use the gnu11 branch in my RTAI tree and pick either 4.19.294 or or 5.4.256
As an additional layer of testing, revert the C89 commit in LinuxCNC to make
sure GNU11 `for` loops actually work as intended:
https://github.com/LinuxCNC/linuxcnc/commit/3d926d87f14ada9dea313c2989ee8f24f0e54e0c
