So,
have been doing some more testing with Debian Jessie and Xenomai kernel
from Machinekit repository.
When compiling the Machinekit 0.1 (single repository), there was not any
problem. (Or at least I could not stumble upon one.) However, when
compiling the Machinekit 0.2 (Machinekit-HAL and Machinekit-CNC) and then
running it, I have seen it. The realtime and halcmd still ran, but there
were complaints.
Looking at ZeroMQ Github, there were some postings about memory leakage and
such, which got me thinking about the version of ZeroMQ in Debian Jessie
repository.
So, I uninstalled the installed versions (installed by sudo mk-build-deps
-ir) by:
de@debianJessieIDE32:~$ apt list --installed *zmq*
Listing... Done
libczmq-dev/stable,now 4.0.2-10~jessie i386 [installed]
libczmq4/stable,now 4.0.2-10~jessie i386 [installed,automatic]
libzmq3/oldstable,oldstable,now 4.0.5+dfsg-2+deb8u1 i386 [installed,
automatic]
libzmq3-dev/oldstable,oldstable,now 4.0.5+dfsg-2+deb8u1 i386 [installed,
automatic]
python-zmq/oldstable,now 14.4.0-1 i386 [installed]
de@debianJessieIDE32:~$ sudo apt remove --purge libczmq-dev libczmq4
libzmq3 libzmq3-dev python-zmq
and installed everything from source:
git clone git://github.com/zeromq/libzmq.git
cd libzmq
./autogen.sh
./configure
make check
sudo make install
sudo ldconfig
cd ..
git clone git://github.com/zeromq/czmq.git
cd czmq
./autogen.sh && ./configure && make check
sudo make install
sudo ldconfig
cd ..
git clone https://github.com/zeromq/pyzmq
cd pyzmq
python setup.py configure --zmq=/usr/local
python setup.py install
Ran the compilation of Machinekit 0.2 again and everything seems to work
without this error.
So, I guess that the building container for machinekit Debian package uses
the standard packages from Debian repository.
Also, the builder for Machinekit-hal-xenomai (and probably other flavors)
builds packages which require as sub-packages versions which are not
installable from Debian Jessie Repository:
The following packages have unmet dependencies:
machinekit-hal-xenomai : Depends: libboost-python1.62.0 but it is not
installable or
libboost-python1.62.0 but it is not installable
Depends: libboost-system1.62.0 but it is not installable or
libboost-system1.67.0 but it is not installable
Depends: libboost-thread1.62.0 but it is not installable or
libboost-thread1.62.0 but it is not installable
Depends: libprotobuf10 but it is not installable or
libprotobuf17 but it is not installable
Depends: libstdc++6 (>= 5.2) but 4.9.2-10+deb8u2 is to be installed
Depends: libtinfo5 (>= 6) but 5.9+20140913-1+deb8u3 is to be installed
E: Unable to correct problems, you have held broken packages.
The boost ends with 1.55, libprotobuf with 9 and others have lower
versions. I don't think that these higher versions are necessarily needed.
Cern.
Dne úterý 23. dubna 2019 20:35:29 UTC+2 mngr napsal(a):
>
>
>
> Il giorno mercoledì 17 aprile 2019 00:12:12 UTC+2, [email protected] ha
> scritto:
>>
>>
>>
>> Dne úterý 16. dubna 2019 23:41:48 UTC+2 mngr napsal(a):
>>>
>>>
>>>
>>> Il giorno martedì 16 aprile 2019 23:19:52 UTC+2, [email protected] ha
>>> scritto:
>>>>
>>>> OK,
>>>> on freshly installed Debian Jessie from minimal netinst ISO with
>>>> Ciannmon and basic tools selected during installation (and one partition)
>>>> on P5K Deluxe, e7200 and 6GB RAM system. Added the Machinekit repository,
>>>> contrib and non-free, installed the Machinekit Xenomai Jessie kernel
>>>> package, upgraded system to latest.
>>>>
>>>> Then I did the RIP install of obsolete machinekit git repository and
>>>> everything works. (GUI and simple test of creating thread, adding function
>>>> and running it).
>>>>
>>>> Then I tried on the same system install packages machinekit and
>>>> machinekit-xenomai and the error occurred. So the problem is either in
>>>> packaging, installation or building.
>>>>
>>>> Questing is if it is worth to resolve as it's EOL for the machinekit
>>>> package.
>>>>
>>>
>>> If my issue is the only reason to do that I think that this bug can stay.
>>> I tried jessie-xenomai because with stretch-preempt I had bad latency.
>>>
>>> Is there any way to improve the latency for a specific installation?
>>>
>>
>> You can always try to play with kernel configuration parametres (based on
>> your system).
>>
>> Interesting thing is that you could not run RIP installation and I could.
>> Could you please confirm it?
>>
>
> Sorry for the delay,
> Yes, I can confirm that the
> Unfortunately I formatted the SSD with Machinekit on jessie, so I cannot
> give you any more details than what I have already sent.
> I agree with your question about the utility of focusing on a soon EOL
> package, so I am working on improving the configuration of the rt kernel.
>
>
>
>
>> Cern.
>>
>>
>>>
>>>
>>>>
>>>> BTW, I will try the machinekit-hal RIP build tomorrow. The package
>>>> machinekit-hal-xenomai is not installable as it has unresolvable
>>>> dependency
>>>> issues.
>>>>
>>>> Dne úterý 16. dubna 2019 19:18:16 UTC+2 [email protected] napsal(a):
>>>>>
>>>>> That's not actually what I had on my mind. Looking at the Machinekit
>>>>> repository on http://deb.machinekit.io/debian/pool/main/m/machinekit/
>>>>> there is machinekit-xenomai_0.1.1536596683.gitb879205-1~jessie_amd64.deb
>>>>> file from 2018-09-17 and what I meat is that if I can get the older
>>>>> prebuild packages? (I don't know how to get the number of package - for
>>>>> example 1536596683 - to try to download it.)
>>>>>
>>>>> However today I discovered something interesting. After multiple
>>>>> reinstalls and so on but the RIP build from master on Debian Jessie AMD64
>>>>> with Xenomai kernel from Machinekit repository works. But installing it
>>>>> as
>>>>> package from Machinekit repository shows the aforementioned error.
>>>>>
>>>>> I will try it on clean Debian Jessie + MK Xenomai later.
>>>>>
>>>>> Cern.
>>>>>
>>>>> Dne úterý 16. dubna 2019 8:43:49 UTC+2 Schooner napsal(a):
>>>>>>
>>>>>> All packages in the repo can be downloaded over html or wget and
>>>>>> installed with 'dpkg -i'
>>>>>> On 4/15/2019 8:54 PM, [email protected] wrote:
>>>>>>
>>>>>>
>>>>>> Hi,
>>>>>> doing some testing I discovered that the problem is present on
>>>>>> http://deb.machinekit.io/debian/pool/main/m/machinekit/machinekit-xenomai_0.1.1536596683.gitb879205-1~jessie_amd64.deb
>>>>>>
>>>>>> package but RIP on randomly chosen build of
>>>>>> f59143cce34cdac3bd75aae4b95b8e43a6540a61
>>>>>> works (I wanted to try something before warning silencing patch).
>>>>>>
>>>>>> However to find the exact border between working and nonworking will
>>>>>> be even with halving method tideous without prebuild packages, so is
>>>>>> there
>>>>>> a way how to get these older packages from repository or are they
>>>>>> forever
>>>>>> deleted?
>>>>>>
>>>>>> Thanks
>>>>>> Cern.
>>>>>>
>>>>>> Dne čtvrtek 21. března 2019 10:47:44 UTC+1 mngr napsal(a):
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I am on
>>>>>>> Linux debian 3.8-1-xenomai.x86-amd64 #1 SMP Debian
>>>>>>> 3.8.13-12~1jessie~1da x86_64 GNU/Linux
>>>>>>>
>>>>>>> with machinekit installed
>>>>>>> marco@debian:~/log$ dpkg --list | grep machinekit
>>>>>>> ii machinekit 0.1.1552558261.git355496b-
>>>>>>> 1~jessie amd64 PC based motion controller for real-time
>>>>>>> Linux
>>>>>>> ii machinekit-xenomai 0.1.1552558261.git355496b-
>>>>>>> 1~jessie amd64 PC based motion controller for real-time
>>>>>>> Linux
>>>>>>>
>>>>>>> from (apt)
>>>>>>> deb http://deb.machinekit.io/debian jessie main
>>>>>>>
>>>>>>> So, I think the installation is good, but whatever (I tried some)
>>>>>>> configuration I try to run I get errors.
>>>>>>> I have attached in print.txt the terminal output
>>>>>>>
>>>>>>> Looking in the log I see that at some point it decides to unload the
>>>>>>> modules, but I can't understand the reason.
>>>>>>>
>>>>>>> Maybe it is the
>>>>>>> FATAL ERROR: OUT OF MEMORY (epoll.cpp:55)
>>>>>>> that it keeps throwing on the terminal.
>>>>>>>
>>>>>>> Is there anything I can do to better debug this?
>>>>>>>
>>>>>> --
>>>>>> website: http://www.machinekit.io blog: http://blog.machinekit.io
>>>>>> github: https://github.com/machinekit
>>>>>> ---
>>>>>> You received this message because you are subscribed to the Google
>>>>>> Groups "Machinekit" group.
>>>>>> To unsubscribe from this group and stop receiving emails from it,
>>>>>> send an email to [email protected].
>>>>>> Visit this group at https://groups.google.com/group/machinekit.
>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>
>>>>>>
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
You received this message because you are subscribed to the Google Groups
"Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.
