rip-environment script not running on RPi4 64bit
10 May 2021 23:56 - 10 May 2021 23:57 #208511
by mwinterm
rip-environment script not running on RPi4 64bit was created by mwinterm
Hello,
I set-up a RPi4 with a 64bit real-time kernel 5.4.61-rt37-v8+.
I also installed 2.8.1 which is running fine.
Then I got the source from github, satisfied all the dependencies and compiled successfully.
Finally to test my build I run from the src directory:and get the feedback:
Any suggestions what could be wrong?
Best regards,
Marc
PS: ...the very same procedure worked fine for me on my laptop with Debian Buster.
I set-up a RPi4 with a 64bit real-time kernel 5.4.61-rt37-v8+.
I also installed 2.8.1 which is running fine.
Then I got the source from github, satisfied all the dependencies and compiled successfully.
Finally to test my build I run from the src directory:
. ../scripts/rip-environment
This script is only useful on run-in-place systems.
Any suggestions what could be wrong?
Best regards,
Marc
PS: ...the very same procedure worked fine for me on my laptop with Debian Buster.
Last edit: 10 May 2021 23:57 by mwinterm.
Please Log in or Create an account to join the conversation.
- BeagleBrainz
-
- Offline
- User is blocked
-
Less
More
- Posts: 1437
- Thank you received: 570
11 May 2021 03:33 #208519
by BeagleBrainz
Replied by BeagleBrainz on topic rip-environment script not running on RPi4 64bit
Did you runafter your build ?
sudo make setuid
Please Log in or Create an account to join the conversation.
11 May 2021 07:52 #208526
by mwinterm
Replied by mwinterm on topic rip-environment script not running on RPi4 64bit
yes
Please Log in or Create an account to join the conversation.
11 May 2021 22:36 #208594
by andypugh
Replied by andypugh on topic rip-environment script not running on RPi4 64bit
I had this yesterday. I didn't even bother trying to work out why (it was on a VM and I have no idea what I last did in there).
Have you ever build a .deb on the machine? That can change the config away from run-in-place.
make clean
./sutogen,sh
./configure --with-realtime-uspace
make
sudo make setuid
Should get you back to a run-in-place.
Have you ever build a .deb on the machine? That can change the config away from run-in-place.
make clean
./sutogen,sh
./configure --with-realtime-uspace
make
sudo make setuid
Should get you back to a run-in-place.
Please Log in or Create an account to join the conversation.
13 May 2021 16:11 #208740
by mwinterm
Replied by mwinterm on topic rip-environment script not running on RPi4 64bit
Hello Andy,
you were exactly right. Had built a .deb package before and make clean solved it.
Thanks a lot![:) :)](/media/kunena/emoticons/smile.png)
Regards,
Marc
you were exactly right. Had built a .deb package before and make clean solved it.
Thanks a lot
![:) :)](/media/kunena/emoticons/smile.png)
Regards,
Marc
Please Log in or Create an account to join the conversation.
23 May 2021 18:23 #209935
by cakeslob
I use the linuxcnc prebuilt images provided on the downloads page, when ever I build a run-in-place version of linuxcnc, the first time I usually need to install all the dependencies/library manually despite having linuxcnc already installed globally.
Why is that? Is there a configuration option Im not using properly?
Replied by cakeslob on topic rip-environment script not running on RPi4 64bit
make clean
./sutogen,sh
./configure --with-realtime-uspace
make
sudo make setuid
I use the linuxcnc prebuilt images provided on the downloads page, when ever I build a run-in-place version of linuxcnc, the first time I usually need to install all the dependencies/library manually despite having linuxcnc already installed globally.
Why is that? Is there a configuration option Im not using properly?
Please Log in or Create an account to join the conversation.
23 May 2021 18:55 - 23 May 2021 19:03 #209940
by Grotius
Replied by Grotius on topic rip-environment script not running on RPi4 64bit
Hi Cakeslob,
That is normal. I understand your question.
For building lcnc from source you actually need all the libraries it depends on only at compile time.
But you also need a few extra's like build-essentials, gcc (the compiler itself), etc.
Some of the dependencies will be compiled into the lcnc code. Some will stay out like python.
After compiling you have a closed source, if you delete the src folder.
The process of compiling lcnc is quite complicated.
A trick for enabling "ripping the environment"
:
That is normal. I understand your question.
For building lcnc from source you actually need all the libraries it depends on only at compile time.
But you also need a few extra's like build-essentials, gcc (the compiler itself), etc.
Some of the dependencies will be compiled into the lcnc code. Some will stay out like python.
After compiling you have a closed source, if you delete the src folder.
The process of compiling lcnc is quite complicated.
A trick for enabling "ripping the environment"
![:evil: :evil:](/media/kunena/emoticons/devil.png)
# solve sudo set setuid problems.
$ sudo chmod 777 yourpath/linuxcnc/bin/rtapi_app
$ sudo chmod 777 yourpath/linuxcnc/bin/linuxcnc_module_helper
Last edit: 23 May 2021 19:03 by Grotius.
Please Log in or Create an account to join the conversation.
23 May 2021 21:21 - 23 May 2021 21:22 #209952
by cakeslob
Ok, because I use this as my install guide forum.linuxcnc.org/32-documents/34495-in...ion-git-clone#109943 (thanks, it explains whats happening step by step , which I desperately need )
So if I understand correctly, the premade images, linuxcnc is compiled beforehand? And on any system, once linuxcnc is compiled, you can strip away (some) the things required only to build it (the things compiled into linuxcnc code)?
Replied by cakeslob on topic rip-environment script not running on RPi4 64bit
Hi Cakeslob,
That is normal. I understand your question.
For building lcnc from source you actually need all the libraries it depends on only at compile time.
But you also need a few extra's like build-essentials, gcc (the compiler itself), etc.
Some of the dependencies will be compiled into the lcnc code. Some will stay out like python.
After compiling you have a closed source, if you delete the src folder.
Ok, because I use this as my install guide forum.linuxcnc.org/32-documents/34495-in...ion-git-clone#109943 (thanks, it explains whats happening step by step , which I desperately need )
So if I understand correctly, the premade images, linuxcnc is compiled beforehand? And on any system, once linuxcnc is compiled, you can strip away (some) the things required only to build it (the things compiled into linuxcnc code)?
Last edit: 23 May 2021 21:22 by cakeslob.
Please Log in or Create an account to join the conversation.
23 May 2021 22:17 #209954
by andypugh
The ISO includes all the run-time dependencies, but does not include all the build-time dependencies.
But that as led me to wonder why linuxcnc-dev does not have all the dependencies as dependencies.
Replied by andypugh on topic rip-environment script not running on RPi4 64bit
I use the linuxcnc prebuilt images provided on the downloads page, when ever I build a run-in-place version of linuxcnc, the first time I usually need to install all the dependencies/library manually despite having linuxcnc already installed globally.
Why is that? Is there a configuration option Im not using properly?
The ISO includes all the run-time dependencies, but does not include all the build-time dependencies.
But that as led me to wonder why linuxcnc-dev does not have all the dependencies as dependencies.
Please Log in or Create an account to join the conversation.
- BeagleBrainz
-
- Offline
- User is blocked
-
Less
More
- Posts: 1437
- Thank you received: 570
24 May 2021 04:40 #210001
by BeagleBrainz
Replied by BeagleBrainz on topic rip-environment script not running on RPi4 64bit
I really don’t want to be installing all the dependencies to build Linuxcnc from source to for the bits needed to build a custom module.
If I remember correctly up to about 6 -12 months there was a script in the source tree that used to help with dependencies.
Building Linuxcnc itself is not at all difficult once all the build deps are there.
I used to supply a “build dev package” along with the regular Linuxcnc updates when I had the Mint repo. TBH I don’t think anyone actually downloaded or used the package.
If I remember correctly up to about 6 -12 months there was a script in the source tree that used to help with dependencies.
Building Linuxcnc itself is not at all difficult once all the build deps are there.
I used to supply a “build dev package” along with the regular Linuxcnc updates when I had the Mint repo. TBH I don’t think anyone actually downloaded or used the package.
Please Log in or Create an account to join the conversation.
Time to create page: 0.168 seconds