which release of yocto are you on ? secondly which OS is on the host? you might want to install python2 perhaps on it.

#python #yocto

Hi, if I try to add a layer like this: bitbake-layers add-layer ../layers/meta-openembedded/meta-oe (also for other layers) I get following error: The following required tools (as specified by HOSTTOO

#python #yocto

Thank you all. The new layer did the trick for me also. Regards, Mike

#python

FYI, we’re doing the same internally (vendor supplied FIPS supported openssl 1.0.2), and the layer Armin suggests worked for us on zeus with minimal additional tweaking. Good luck! -Sean

#python

Have had a chance to look at this layer? http://git.yoctoproject.org/cgit/cgit.cgi/meta-openssl102-fips/ - armin

#python

I think python2 *recipe* requires openssl 1.1, but python2 itself will work just fine with openssl 1.0. So you only need to adjust the dependency, there are several ways to do that. Alex

#python

I'm working on a set of platforms that have a FIPs certified OpenSSL. We are at version 1.0.2l. I've found that the new version of python in Zeus (2.7.17) requires a newer version of OpenSSL (1.1). We

#python

Numpy is already part of oe-core: http://layers.openembedded.org/layerindex/recipe/51338/ Why not just use the existing recipe?

#yocto #python

Hello, I am trying to install numpy module in my image using "pipoe". When i bitbake my recipe i got this : Log data follows: | DEBUG: Executing shell function do_compile | ERROR: python3 setup.py bui

#yocto #python

Looks good to me. Lucky you :) -Mikko

#yocto #python

OK, I read some code and I added the next line: --- a/bitbake/lib/bb/fetch2/svn.py +++ b/bitbake/lib/bb/fetch2/svn.py @@ -145,6 +145,7 @@ class Svn(FetchMethod): if not ("externals" in ud.parm and ud.

#yocto #python

Ah, indeed. svn is supported and for me it's working quite well. It has some issues like download cache locking when multiple recipes include the same URLs. Where possible, I've switched to using http

#yocto #python

Hi Mikko, Your patch is upstreamed and...It is actually released. If you see the error output you will see your codeline. I decided to try with your old version but the result is the same. Can you say

#yocto #python

Hmm. Rings a bell. I run builds with a local non-upstreamed patch: Author: Mikko Rapeli <mikko.rapeli@...> AuthorDate: Fri Sep 6 14:15:20 2019 +0200 Commit: Mikko Rapeli <mikko.rapeli@...> Commi

#yocto #python

Another serious issue with svn fetcher, always occurring when doing incremental builds. I am putting it here because I think both issues are related. Please suggest what to do. The error we get is sho

#yocto #python

Sorry Khem, With esc character '\' before & it can't take the full path. So briefly: Yocto build with char '\' before & in SRC_URI: online - OK offline - Error - svn: E170013: Unable to connect to a r

#yocto #python

Hi Khem, Yes, no issues with that. When I am connected to network it fetches the code with and without escape character before & in the path. svn co " http://cocosubversion/svn/Embedded/Valve&Actuator

#python #yocto

svn: E170013: Unable to connect to a repository at URL 'http://cocosubversion/svn/Embedded/Valve&Actuator/DVPII/trunk/SOCPACManEnvEngKeys/trunk' svn: E670003: Temporary failure in name resolution can

#yocto #python

Hi, I can't comment on svn fetcher but I use subversion via http fetcher. This way the local download cache can have the exact same file and builds can continue off line. One major gotcha is that all

#yocto #python

Hello Community, This is the third time I am asking for support on this issue. This time I decided to use the web form. In our project we have a requirement to be able to build the project offline. E.

#yocto #python