Re: [ptxdist] Python handling was changes in the past, so remove a leftover as well

On Fri, Apr 03, 2020 at 07:21:08PM +0200, Uwe Kleine-König wrote: > On Thu, Apr 02, 2020 at 05:03:29PM +0200, Michael Olbrich wrote: > > Thanks, applied as 70e95734668542ac638d5cb8a759ad402d678ff4. > > Sad that the two typos I indicated were not fixed :-| Actually I fixed one of them, but lost

Re: [ptxdist] Python handling was changes in the past, so remove a leftover as well

On Thu, Apr 02, 2020 at 05:03:29PM +0200, Michael Olbrich wrote: > Thanks, applied as 70e95734668542ac638d5cb8a759ad402d678ff4. Sad that the two typos I indicated were not fixed :-| Best regards Uwe -- Pengutronix e.K. | Uwe Kleine-König| Industrial Linux

Re: [ptxdist] Python 3.7.3 with ptxdist-2015.05.0

Thanks for the information.I already tried to merge the make and in files without success, so it seems as Michael said, there are more advanced adaptions needed.Regards___ ptxdist mailing list ptxdist@pengutronix.de

Re: [ptxdist] Python 3.7.3 with ptxdist-2015.05.0

On Thu, May 02, 2019 at 02:42:53PM +0200, Roland Hieber wrote: > On Tue, Apr 30, 2019 at 04:45:09PM +0200, webmas...@zutroll.de wrote: > > Hello, > > > > I am trying to get the new 3.7.3 python running with the older ptxdist, but > > I cannot get it working. I tried to merge from the latest

Re: [ptxdist] Python 3.7.3 with ptxdist-2015.05.0

On Tue, Apr 30, 2019 at 04:45:09PM +0200, webmas...@zutroll.de wrote: > Hello, > > I am trying to get the new 3.7.3 python running with the older ptxdist, but > I cannot get it working. I tried to merge from the latest ptxdist but still > fails. It would help if you said what exactly fails :-)

[ptxdist] Python 3.7.3 with ptxdist-2015.05.0

Hello, I am trying to get the new 3.7.3 python running with the older ptxdist, but I cannot get it working. I tried to merge from the latest ptxdist but still fails. Has someone done this before and could help me? What files need to be adapted to get the python 3.7.3 to work with the

Re: [ptxdist] Python 3.5 and the use of getrandom() system call

Hi, On Tue, Nov 29, 2016 at 09:56:59AM +0100, Alexander Dahl wrote: > On Fri, Nov 18, 2016 at 02:21:36PM +0100, David Jander wrote: > > Or is there a way (that I ignore) to speed-up the generation of > > entropy in the Linux kernel? > > I heard other people use haveged for this. I have two

Re: [ptxdist] Python 3.5 and the use of getrandom() system call

Hi, On Tue, Nov 29, 2016 at 09:56:59AM +0100, Alexander Dahl wrote: > On Fri, Nov 18, 2016 at 02:21:36PM +0100, David Jander wrote: > > Or is there a way (that I ignore) to speed-up the generation of > > entropy in the Linux kernel? I agree with the other that such a patch is not a good idea for

Re: [ptxdist] Python 3.5 and the use of getrandom() system call

Hei hei, On Fri, Nov 18, 2016 at 02:21:36PM +0100, David Jander wrote: > Or is there a way (that I ignore) to speed-up the generation of > entropy in the Linux kernel? I heard other people use haveged for this. I have two experimental patches for adding a haveged package, but did not test it

Re: [ptxdist] Python 3.5 and the use of getrandom() system call

On Fri, 18 Nov 2016 18:15:58 +0100 Clemens Gruber wrote: > Hi, > > On Fri, Nov 18, 2016 at 02:21:36PM +0100, David Jander wrote: > > Or is there a way (that I ignore) to speed-up the generation of entropy in > > the > > Linux kernel? > > Did you build your

Re: [ptxdist] Python 3.5 and the use of getrandom() system call

On 18.11.2016 18:15, Clemens Gruber wrote: > It's probably a bad idea to just patch python for every PTXdist user. > Not everybody is willing to trade security for faster start times. Judging from Python-3.5.0/Python/random.c:118, it will use the getrandom() syscall with flags=0, and according to

Re: [ptxdist] Python 3.5 and the use of getrandom() system call

Hi, On Fri, Nov 18, 2016 at 02:21:36PM +0100, David Jander wrote: > Or is there a way (that I ignore) to speed-up the generation of entropy in the > Linux kernel? Did you build your kernel with CONFIG_CRYPTO_JITTERENTROPY=y and CONFIG_CRYPTO_DRBG_HASH=y ? Also, depending on your platform, there

[ptxdist] Python 3.5 and the use of getrandom() system call

Hi all, I have noticed that on embedded Linux systems, the kernel can apparently take a significant amount of time to gather enough entropy to successfully initialize the "nonblocking random pool". This leads to any python (3.5) scripts or applications started on boot to hang for that time,

Re: [ptxdist] Python module installation on target

Hi Arpit, On Friday 05 September 2014 07:12:20 Arpit Jain (RBEI/EEB2) wrote: I have a python module which comes with setup.py, how can I install this module on target ? Running python setup.py install on target won't work as install tools are not available with python installed on board. The

Re: [ptxdist] Python module installation on target

Hi Juergen, On Fri, Sep 05, 2014 at 09:21:36AM +0200, Juergen Borleis wrote: Hi Arpit, On Friday 05 September 2014 07:12:20 Arpit Jain (RBEI/EEB2) wrote: I have a python module which comes with setup.py, how can I install this module on target ? Running python setup.py install on target

[ptxdist] Python module installation on target

Hi, I have a python module which comes with setup.py, how can I install this module on target ? Running python setup.py install on target won't work as install tools are not available with python installed on board. The module I am trying to install is pyOwnCloud

Re: [ptxdist] python: don't create '$(PTXCONF_SYSROOT_CROSS)/bin/python' link

On Fri, Nov 30, 2012 at 04:55:40PM -0600, George McCollister wrote: On 11/30/2012 04:11 PM, Michael Olbrich wrote: The problem is, that this link hides the system python ($PTXDIST_TOPDIR}/bin/python). So packages that need python for building sometimes get the wrong python (if python is built

Re: [ptxdist] python: don't create '$(PTXCONF_SYSROOT_CROSS)/bin/python' link

On 11/30/2012 04:11 PM, Michael Olbrich wrote: The problem is, that this link hides the system python ($PTXDIST_TOPDIR}/bin/python). So packages that need python for building sometimes get the wrong python (if python is built first). Also, I don't see why it should break you packages. There is

Re: [ptxdist] python: don't create '$(PTXCONF_SYSROOT_CROSS)/bin/python' link

On 11/30/2012 04:11 PM, Michael Olbrich wrote: The problem is, that this link hides the system python ($PTXDIST_TOPDIR}/bin/python). So packages that need python for building sometimes get the wrong python (if python is built first). Also, I don't see why it should break you packages. There is

Re: [ptxdist] python: don't create '$(PTXCONF_SYSROOT_CROSS)/bin/python' link

Why did you decide to remove this link? This breaks several of my package rules that use the waf build system. Specifically talloc and tevent. Is there a case when you don't want to use CROSS_PYTHON? If you did this to solve a specific problem let me know because I was having some python related

Re: [ptxdist] Python problems on RHEL5

Are those patches acceptable ? - Erwin mailingli...@erwinrol.com wrote: On RHEL5 there is a python version 2.4, which is to old for xcb-proto and libxcb. The following 3 patches try to fix that problem, but need some help. [PATCH 1/3] [python] remove broken 3.1 to make host-python work

[ptxdist] Python problems on RHEL5

On RHEL5 there is a python version 2.4, which is to old for xcb-proto and libxcb. The following 3 patches try to fix that problem, but need some help. [PATCH 1/3] [python] remove broken 3.1 to make host-python work With the selection 2.6 or 3.1 setup the host-python packet would not work,

Re: [ptxdist] Python problems on RHEL5

mailingli...@erwinrol.com wrote: On RHEL5 there is a python version 2.4, which is to old for xcb-proto and libxcb. The following 3 patches try to fix that problem, but need some help. [PATCH 1/3] [python] remove broken 3.1 to make host-python work With the selection 2.6 or 3.1 setup the

Re: [ptxdist] python package problem/questions

Hi, I used ptxdist 1.99.11 but I compared the rules and patches with the trunk and they are the same. The problem is that I didn't understand how the current rule activates the compilation, as the compilation part is comented out... Best regards, Claudio Leonel Robert Schwebel wrote: On

Re: [ptxdist] python package problem/questions

On Freitag, 17. April 2009, Claudio Leonel wrote: I used ptxdist 1.99.11 but I compared the rules and patches with the trunk and they are the same. The problem is that I didn't understand how the current rule activates the compilation, as the compilation part is comented out... When there is

Re: [ptxdist] Python

On Tue, Nov 25, 2008 at 08:50:46AM -0700, Gary Thomas wrote: What's the reason for having the version of Python tied to the configuration symbol, e.g. PYTHON24 vs PYTHON30? I'm not ready to use Python 3.0, but I would like to move forward to Python 2.5.1. Having this configuration coupling

Re: [ptxdist] Python

Robert Schwebel wrote: On Tue, Nov 25, 2008 at 08:50:46AM -0700, Gary Thomas wrote: What's the reason for having the version of Python tied to the configuration symbol, e.g. PYTHON24 vs PYTHON30? I'm not ready to use Python 3.0, but I would like to move forward to Python 2.5.1. Having this

Re: [ptxdist] Python packages

On Fri, Aug 22, 2008 at 01:19:46PM +0200, Robert Schwebel wrote: On Fri, Aug 22, 2008 at 05:16:57AM -0600, Gary Thomas wrote: Perhaps you have a package that you could share the actual files for? One that's not in the SVN tree... I'll see what I can do with these ideas. We could add

Re: [ptxdist] Python packages

On Thu, Aug 21, 2008 at 03:03:04PM -0600, Gary Thomas wrote: I'd like to add a python package to my PTXdist tree. The key thing will be to run python setup.py install in the target-install step in such a way that any non-python pieces get built correctly. For example, trying to install

Re: [ptxdist] Python packages

Hi, On Thu, Aug 21, 2008 at 03:03:04PM -0600, Gary Thomas wrote: I'd like to add a python package to my PTXdist tree. The key thing will be to run python setup.py install in the target-install step in such a way that any non-python pieces get built correctly. For example, trying to

Re: [ptxdist] Python packages

Michael Olbrich wrote: Hi, On Thu, Aug 21, 2008 at 03:03:04PM -0600, Gary Thomas wrote: I'd like to add a python package to my PTXdist tree. The key thing will be to run python setup.py install in the target-install step in such a way that any non-python pieces get built correctly. For

Re: [ptxdist] Python packages

On Fri, Aug 22, 2008 at 05:16:57AM -0600, Gary Thomas wrote: This is a great start, thanks. Note, nevertheless, that my comments stay true even with the above. It somehow works, but is not reliable. Perhaps you have a package that you could share the actual files for? One that's not in the

Re: [ptxdist] Python packages

Robert Schwebel wrote: On Fri, Aug 22, 2008 at 05:16:57AM -0600, Gary Thomas wrote: This is a great start, thanks. Note, nevertheless, that my comments stay true even with the above. It somehow works, but is not reliable. Fair enough. I'm only interested in x86 - PPC, so I should be OK.

Re: [ptxdist] Python packages

On Fri, Aug 22, 2008 at 05:37:07AM -0600, Gary Thomas wrote: Note, nevertheless, that my comments stay true even with the above. It somehow works, but is not reliable. Fair enough. I'm only interested in x86 - PPC, so I should be OK. Hmm, please report back if it works for LE - BE cases. We

[ptxdist] Python packages

I'd like to add a python package to my PTXdist tree. The key thing will be to run python setup.py install in the target-install step in such a way that any non-python pieces get built correctly. For example, trying to install Cheetah requires the use of the target GCC in order to build a