Thanks, it was the virtual memory. The swap solution worked perfectly fine.


On August 30, 2016 3:50:14 PM GMT+02:00, Chen Chengxi 
<[email protected]> wrote:
>What is your error in detail? If it run out of memory, you can make a
>swap to solve this issue.
>
>-Chengxi
>
>> On 30 Aug, 2016, at 4:27 am, Alexander Rössler
><[email protected]> wrote:
>> 
>> What was the solution for the Python Boost problem? I have the same
>problem on the CHIP running Debian Jessie.
>> 
>> Am Montag, 8. Dezember 2014 12:56:11 UTC+1 schrieb euerka:
>>> 
>>> Dear all,
>>> 
>>> Recently I would like to update machinekit to latest version, so I
>tried to compile from source code on beaglebone black. 
>>> 
>>> When I start ./configure 
>>> checking whether the Boost::Python headers are available... no
>>> configure: error: boost::python is required to build LinuxCNC
>>> 
>>> Any idea? since I re-install libboost-python-dev already.
>>> 
>>> Thanks! 
>>> Best regards
>>> -chengxi
>> 
>> -- 
>> website: http://www.machinekit.io blog: http://blog.machinekit.io
>github: https://github.com/machinekit
>> --- 
>> You received this message because you are subscribed to a topic in
>the Google Groups "Machinekit" group.
>> To unsubscribe from this topic, visit
>https://groups.google.com/d/topic/machinekit/3BzbZ3d9TWM/unsubscribe.
>> To unsubscribe from this group and all its topics, 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.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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.

Reply via email to