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.000074
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 8 .. 10 Next › Last »

Tweety commented on 2024-08-11 13:31 (UTC)

Hi all,

I got stuck here

checking match between tk and Tkinter versions... Traceback (most recent call last):
  File "<string>", line 1, in <module>
ImportError: No module named _tkinter
Traceback (most recent call last):
  File "<string>", line 1, in <module>
ImportError: No module named _tkinter
TCL mismatch: 8.6 vs 
configure: error: Python requires use of Tcl  and Tk .
Install this version and specify --with-tclConfig and --with-tkConfig if necessary
==> ERROR: A failure occurred in prepare().
    Aborting...
 -> error making: linuxcnc-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
linuxcnc - exit status 4

I checked here backwards and generally in the internet but didn't find a solution. I am also not sure if tcl/tk version 8.6 is ok or if it should be 8.4.

Anny advise? greez2all Tweety

FabioLolix commented on 2024-08-09 12:30 (UTC) (edited on 2024-08-09 12:30 (UTC) by FabioLolix)

@simona

Solved with:
yay -Rs mingw-w64-gcc libtirpc-compat netkit-rusers nfsshell

This would have been avoided building in clean chroot, both the hassle of the error and removing the packages

I think I understand that it's about creating an independent environment and installing there.

It don't install there, it build there

you install the builded package in your system

That kind of thing that takes up your disk space and somehow dirty up your installation. No thanks.

It creates a folder which you can deleted later and is not dirtying your installation, the chroot for building gnuclad (a small cli program) is 2GB pratically all of Arch packages

It create an isolated environment and build the package there, this is the way Arch Linux packages are build

Building in chroot prevent unwanted dynamic and other quirks of users system and I know your system have several

It is the reccomended way of building compilers on AUR

It is also helpful when you need to use conflicting makedepends like the nodejs versions and the only sane way to deal with stuff like ffmpeg AUR variants, mesa AUR variants etc

I prefer things that are simple and linear. A single package shouldn't complicate your life like that.

except packaging isn't always simple

https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot

simona commented on 2024-08-09 11:20 (UTC) (edited on 2024-08-09 11:41 (UTC) by simona)

The true question is: where when I install linuxcnc, yay take the include used? Where is stored the path?
locate rpc.h
find
/opt/watcom/h/nt/rpc.h
/usr/i686-w64-mingw32/include/rpc.h
/usr/include/capnp/rpc.h
/usr/include/event2/rpc.h
/usr/include/rpc/rpc.h
/usr/include/tirpc/rpc/rpc.h

Solved with:
yay -Rs mingw-w64-gcc libtirpc-compat netkit-rusers nfsshell
/usr/include/wine/windows/rpc.h
/usr/x86_64-w64-mingw32/include/rpc.h

simona commented on 2024-08-09 09:06 (UTC) (edited on 2024-08-09 09:07 (UTC) by simona)

I've been doing some research on this chroot installation. I think I understand that it's about creating an independent environment and installing there. That kind of thing that takes up your disk space and somehow dirty up your installation. No thanks. I prefer things that are simple and linear. A single package shouldn't complicate your life like that. thx for FailFast and SkipReview.

FabioLolix commented on 2024-08-09 08:13 (UTC)

@simona yesterday forgot to specify with paru in chroot, which seems the easiest way to build the packages in chroot, in paru.conf I'm adding the options FailFast and SkipReview

simona commented on 2024-08-08 23:09 (UTC)

tryied: with paru it is the same than yay

GPereira commented on 2024-08-08 22:46 (UTC)

@FabioLolix aren't we missing an install directive to load linuxcnc.sh into profile.d that the prepare() script generates?

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

configure: error: Unable to use rpc.h

Simona, not sure what is going on in your system, please have a look at building AUR packages with paru which seems the easiest way

simona commented on 2024-08-08 18:42 (UTC) (edited on 2024-08-08 19:00 (UTC) by simona)

checking for usability of rpc/rpc.h... no
configure: error: Unable to use rpc.h
I have:
LANG=C pacman -Qo /usr/include/tirpc/rpc/rpc.h
/usr/include/tirpc/rpc/rpc.h is owned by libtirpc 1.3.5-1
tryied to use:
[[ ":$TCLLIBPATH:" != ":/usr/lib/tcltk/linuxcnc:" ]] && export TCLLIBPATH="/usr/lib/tcltk/linuxcnc:$TCLLIBPATH"
but no change.

GPereira commented on 2024-08-08 18:30 (UTC)

After thinking about it better it has another problem. During package updates the variable would be set to

"/usr/lib/tcltk/linuxcnc:/usr/lib/tcltk/linuxcnc"

and in the next update to

"/usr/lib/tcltk/linuxcnc:/usr/lib/tcltk/linuxcnc:/usr/lib/tcltk/linuxcnc"

This, although it works would make no sense. So I propose to change to:

[[ ":$TCLLIBPATH:" != *":/usr/lib/tcltk/linuxcnc:"* ]] && export TCLLIBPATH="/usr/lib/tcltk/linuxcnc:$TCLLIBPATH"

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