On Mon, 23 Oct 2023 at 09:08, andy pugh wrote:
>
> > As for the failing modules, the problem is that when you build LinuxCNC
> > Debian packages, you're in the top directory of LinuxCNC, _not_ the src
> > directory. In linuxcnc/src/Makefile, the value of M is $(PWD) however when
> > you build
I thought my local changes to prevent docs from building if `no-docs` is set
was the reason for this breakage, but I reverted my doc changes and I still get
this error:
# `.../doc/linuxcnc`) because that's where the
# `linuxcnc` launcher script looks for them, and that's
# inconvenient to
By using BASEPWD, there's some magic I don't quite understand but here it is:
ifeq ($(BASEPWD),)
BASEPWD := $(shell pwd)
export BASEPWD
include Makefile.inc
else
include $(BASEPWD)/Makefile.inc
endif
M=$(PWD)/src needs to be set if you're building LinuxCNC kernel modules from
the top directory
The problem has to do with Kbuild, and I think I just found the right magic.
uspace doesn't use the M= value at all nor builds any kernel modules.
M=$(BASEPWD) seems to satisfy both ./configure builds and Debian packages.
Commit:
On Mon, 23 Oct 2023 at 04:22, Alec Ari via Emc-developers
wrote:
> As for the failing modules, the problem is that when you build LinuxCNC
> Debian packages, you're in the top directory of LinuxCNC, _not_ the src
> directory. In linuxcnc/src/Makefile, the value of M is $(PWD) however when
>
I mostly figured this out, both the docs issue and the module building issue.
As for docs, the `nodocs` option is completely ignored. When I fixed that, I
get:
# some clean-up
rm -f
/home/ntu/linuxcnc/debian/tmp/usr/share/doc/linuxcnc/examples/sample-configs/*/*position*.txt
make[1]: Leaving
On Mon, 23 Oct 2023 at 00:15, Alec Ari via Emc-developers
wrote:
>
> One thing to try, revert 3ee51e306bbe93d424dcdcc8429feaf0b9d6ef02
Yes, that looks promising.
> Thanks for the command lines, will dig soon.
You can also try ./debian/configure -r no-docs
(I tried --no-docs and that didn't
One thing to try, revert 3ee51e306bbe93d424dcdcc8429feaf0b9d6ef02
Thanks for the command lines, will dig soon.
Alec
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
On Sun, 22 Oct 2023 at 22:44, Alec Ari via Emc-developers
wrote:
>
> What on the command line do you pass to trigger building LinuxCNC against
> RTAI? I'll need the full ./debian/configure stuff and the dpkg-buildpackage
> strings and whatever else is required. Treat me like I'm a total Debian
What on the command line do you pass to trigger building LinuxCNC against RTAI?
I'll need the full ./debian/configure stuff and the dpkg-buildpackage strings
and whatever else is required. Treat me like I'm a total Debian noob :)
Alec
___
I have hardly any experience writing Debian packages, and the ones for LinuxCNC
are quite complicated. I will try building your tree on my Debian system soon
and see if I can help at all. I hope someone else can chime in.
Alec
___
Emc-developers
> On 22 Oct 2023, at 21:36, Alec Ari via Emc-developers
> wrote:
>
> As a sanity check, have you done the same to ensure your RTAI environment is
> all good? Just a quick run-in-place install for testing.
Yes, I have been building and running RIP with RTAI continuously.
Compiling works
I have no idea where your problem might be coming from but I'm guessing it
might be missing the "M" argument.
i.e.
$(PYTHON) modsilent.py $(MAKE) KBUILD_EXTRA_SYMBOLS=$(moduledir)/Module.symvers
-C $(KERNELDIR) M=$(PWD) CC=$(CC) V=$(BUILD_VERBOSE) modules
For the record, I have been able to
13 matches
Mail list logo
