Package Details: linuxcnc 2.9.4-1

Git Clone URL: https://aur.archlinux.org/linuxcnc.git (read-only, click to copy)
Package Base: linuxcnc
Description: Controls CNC machines. It can drive milling machines, lathes, 3d printers, laser cutters, plasma cutters, robot arms, hexapods, and more (formerly EMC2)
Upstream URL: https://linuxcnc.org/
Keywords: 3d cnc printing
Licenses: GPL2, custom: unredestributable
Submitter: GPereira
Maintainer: FabioLolix
Last Packager: FabioLolix
Votes: 9
Popularity: 0.000066
First Submitted: 2018-11-24 01:49 (UTC)
Last Updated: 2025-03-07 18:42 (UTC)

Dependencies (47)

Required by (1)

Sources (3)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 .. 10 Next › Last »

Tweety commented on 2024-08-12 14:38 (UTC)

Hi Fabio,

your impression seem to be wrong but I don't want to start a bigger discussion on that.

Python2-yapps2 was already off my system since 2023. I only had python-yapps2 (not python2-*) since then.

For people who run into the same build errors as I did, may find help, if they simply uninstall all python2- packages and reinstall python-yapps2. Followed by a clean install of python2- in case they are still needed.

greez2all

Tweety

FabioLolix commented on 2024-08-11 22:53 (UTC)

The build environment will be as clean as the package manager will make it.

Then it is dirty

I'm not a developer and expect a package defining files to instruct the package manager on how to cleanly build the software.

pkgbuild will never instruct the package manager (btw the build is done by an AUR helper) to do a clean build; don't even makepkg do

Neither I am a developer and sometimes packaging is hard

InnerBushman commented on 2024-08-11 22:47 (UTC)

The build environment will be as clean as the package manager will make it. I don't have immediate control over what pamac does when I click "build" in the GUI. I'm not a developer and expect a package defining files to instruct the package manager on how to cleanly build the software. Time spent on debugging installation process could be spent on CNC-ing stuff! :)

FabioLolix commented on 2024-08-11 22:31 (UTC)

Just wanted to mention that all my problems with building and missing gi module stemmed from improperly detected highest version of python. After I removed python 2.x and 3.9, the installation (build) finished without issues.

Learning to build in clean chroot solved that

https://aur.archlinux.org/packages/linuxcnc#comment-986138

https://aur.archlinux.org/packages/linuxcnc#comment-985912

InnerBushman commented on 2024-08-11 22:28 (UTC)

Just wanted to mention that all my problems with building and missing gi module stemmed from improperly detected highest version of python. After I removed python 2.x and 3.9, the installation (build) finished without issues. My current version of python is 3.12. From what I can see the prepare() only checks for 3.11 and lower, that's why it found 3.9 in my system instead. Here's the log: https://pastebin.com/jUftCxGT I know nothing about python so can't really dig into this in any helpful manner. I'm here for the CNC :D

FabioLolix commented on 2024-08-11 22:11 (UTC)

I used a yay/pacman -Qs python2 and got no further results. Started linuxcnc setup and got that yapps error.

If you removed python2 that would remove python2-yapps and then the old linuxcnc build

Started linuxcnc setup and got that yapps error.

Which 'that yapps error'

My impression is that you don't keep your system up-to-date anyway I don't have time or energy to provide tips on system maintainance; look into the forum for that

Tweety commented on 2024-08-11 18:20 (UTC)

Hi Fabio,

thanks for the hint. I used a yay/pacman -Qs python2 and got no further results. Started linuxcnc setup and got that yapps error. Any hints how to find residuals?

greez2all

Tweety

FabioLolix commented on 2024-08-11 18:09 (UTC)

Finally it seems, that there is a mismatch with python-2 packages and current linuxcnc libs. I uninstalled all of them and ended up in a "yapps" conflict.

This isn't using python2 since v2.9.1 update on 2023-10-30

If you had removed all the python2 packages and still had "yapps" conflict you hadn't removed all python2 packages

tclx packages are also tied to tcl version

Tweety commented on 2024-08-11 17:02 (UTC)

Hi all,

in my hopeless situation I started to clean up and did crazy things. Finally it seems, that there is a mismatch with python-2 packages and current linuxcnc libs. I uninstalled all of them and ended up in a "yapps" conflict. Reinstalling that too did the trick. Everything installed nicely. TCL/TK is on its latest version 8.6.

Hope that helps others to find the error. Running the lcnc installation from scratch seems to make a clean python environment necessary.

greez2all

and good luck Tweety

FabioLolix commented on 2024-08-11 13:35 (UTC)

I am also not sure if tcl/tk version 8.6 is ok or if it should be 8.4.

Check on https://archlinux.org/packages/ (8.6), fully update you system before dealing with AUR pkgbuilds

Look into building in a clean chroot with for example paru --chroot for an easy way

« First ‹ Previous 1 2 3 4 5 6 7 .. 10 Next › Last »