Re: [yocto] net-snmp 5.8 recipe

Read the configure log and it will tell you what went wrong, which may or may not be easy to fix. Ross On 19 July 2018 at 22:01, Simon Chamlian wrote: > Hi, > > Is there any recipe for the new snmp release 5.8 ? > > I took the net-snmp_5.7.3.bb file and renamed it net-snmp_5.8.bb > removed the

Re: [yocto] Error Report Tool Purge

On Thu, Jul 19, 2018 at 11:30 AM Brindle, Amanda R wrote: > > Hello, > > > > The Error Reporting Tool’s database > (http://errors.yoctoproject.org/Errors/Latest/Autobuilder/) has grown to a > huge size, and this is affecting the performance of the application. We are > planning to run a purge

[yocto] net-snmp 5.8 recipe

Hi, Is there any recipe for the new snmp release 5.8 ? I took the net-snmp_5.7.3.bb file and renamed it net-snmp_5.8.bb removed the patches and re-entered the checksum but it still giving me errors. ERROR: net-snmp-5.8-r0 do_configure: This autoconf log indicates errors, it looked at host

Re: [yocto] QA cycle report for 2.2.4 RC1

On Thu, 2018-07-19 at 09:55 +, Yeoh, Ee Peng wrote: > This is the full report for 2.2.4.rc1: > https://wiki.yoctoproject.org/wiki/WW28_-_2018-07-13_-_Full_Test_Cycl > e_2.2.4_rc1 > > === Summary > > All planned tests were executed. There were zero high milestone > defect.

Re: [yocto] Error Report Tool Purge

Every time a specific report is visited (with the end of the URL being /Errors/Details/), we are tracking if the referrer is another website, the reporting tool itself, or unknown. If the referrer is another website or unknown, then we won’t delete it. The purge script does not look at links

Re: [yocto] Error Report Tool Purge

I'm just curious, how are you tracking which reports were viewed or linked to (and linked from where)? I often use a link to http://errors.yoctoproject.org in the mailing list or the recipes/commit message instead of copy pasting whole build error, because it already shortens the build paths and

[yocto] Error Report Tool Purge

Hello, The Error Reporting Tool's database (http://errors.yoctoproject.org/Errors/Latest/Autobuilder/) has grown to a huge size, and this is affecting the performance of the application. We are planning to run a purge to get rid of reports that we don't need. We will keep reports from the

[yocto] Minutes: Yocto Project Weekly Triage Meeting

Attendees: Kosta, Randy, Stephen, Anuj, Amanda, Richard, Ross, Joshua, Alejandro, Paul, Wiki: https://wiki.yoctoproject.org/wiki/Bug_Triage AR: Anuj – Review 12789. AR: Paul – Check with Aaron about

Re: [linux-yocto] [PATCH] cfg: Add config fragments for docker

On 2018年07月19日 22:58, Bruce Ashfield wrote: > We already carry the .cfg fragments for docker in the > meta-virtualization layer. > > Are the ones there not working ? Thanks for reminding, they're ok there. Please ignore this. Zhe > > While we could move these into the kernel-cache, it makes >

Re: [linux-yocto] [PATCH] cfg: Add config fragments for docker

We already carry the .cfg fragments for docker in the meta-virtualization layer. Are the ones there not working ? While we could move these into the kernel-cache, it makes them less visible or forces the maintenance of two copies of the same config. Bruce On 07/19/2018 10:56 AM,

Re: [linux-yocto] [PATCH] intel-x86: Add preemp-rt config entries

merged. Bruce On 07/18/2018 09:44 AM, zhe...@windriver.com wrote: From: He Zhe Signed-off-by: He Zhe --- bsp/intel-x86/intel-x86-32-preempt-rt.scc | 9 + bsp/intel-x86/intel-x86-64-preempt-rt.scc | 8 2 files changed, 17 insertions(+) create mode 100644

[linux-yocto] [PATCH] cfg: Add config fragments for docker

From: He Zhe Signed-off-by: He Zhe --- cfg/docker.cfg | 10 ++ cfg/docker.scc | 4 2 files changed, 14 insertions(+) create mode 100644 cfg/docker.cfg create mode 100644 cfg/docker.scc diff --git a/cfg/docker.cfg b/cfg/docker.cfg new file mode 100644 index 000..c678c94 ---

Re: [yocto] Setting recipe version inside an image recipe

Thank you. Your suggestion is very useful. The best choice at the end is to have one  recipe every stable version of myapp. So I can freeze the true production recipe for that version. Maybe in the future the recipe myapp could be evolve with some enhancement which could not be compatible

Re: [yocto] cannelloni.bb (Was: [Chicken and Egg problem] Defining RDEPENDS of the package itself)

On Thu, 2018-07-19 at 14:44 +0200, Zoran Stojsavljevic wrote: > Actually, I ran into this: > http://cgit.openembedded.org/meta-openembedded/tree/meta-oe/recipes- > extended/socketcan :-) I mentioned that in my original response. > > So here, I think, can-utils recipes should be revisited,

Re: [yocto] cannelloni.bb (Was: [Chicken and Egg problem] Defining RDEPENDS of the package itself)

Actually, I ran into this: http://cgit.openembedded.org/meta-openembedded/tree/meta-oe/recipes-extended/socketcan So here, I think, can-utils recipes should be revisited, cannelloni recipe added, and also another application recipe added as well: https://github.com/dschanoeh/socketcand/ Best

[yocto] Setting recipe version inside an image recipe

Hi all I'm working with Krogoth. I'd like to do this. - I have my application added to yocto tree by its own recipe myapp_git.bb This recipe get the source code from a local git repository setting  SRCREV for the last stable application source code. SRCREV is fixed in myapp_git.bb - I

Re: [yocto] [Chicken and Egg problem] Defining RDEPENDS of the package itself!

> Is your code published? (I mean not in the email, > too messy to extract it from there) Feel free to comment on it, and to elaborate better recipes. Published on my scratch pad everything/nothing git: https://github.com/ZoranStojsavljevic/cip-rt-misc/tree/master/configs/bbb/YOCTO-recipes Zoran

Re: [yocto] cannelloni.bb (Was: [Chicken and Egg problem] Defining RDEPENDS of the package itself)

> I'm happy to move cannelloni to a generic layer if there is wider interest. I did not write only the stand-alone recipe for cannelloni, since I needed the one, original one from this location: https://github.com/mguentner/cannelloni I also wrote one for can-utils, since one, residing in YOCTO

Re: [yocto] Why can diffsigs take sometimes really looooong?

On Mon, 2018-07-16 at 11:26 +0300, Uwe Geuder wrote: > On Sun, Jul 15, 2018 at 1:38 PM, Richard Purdie wrote: > > On Fri, 2018-07-13 at 19:18 +0300, Uwe Geuder wrote: > > > At times I find the diffsigs command useful/educational to > > > understand > > > what is going on in my build. > > > > > >

[yocto] QA cycle report for 2.2.4 RC1

Hello All,   This is the full report for 2.2.4.rc1: https://wiki.yoctoproject.org/wiki/WW28_-_2018-07-13_-_Full_Test_Cycle_2.2.4_rc1   === Summary   All planned tests were executed. There were zero high milestone defect. Team had found 3 new defects [1] [2] [3] where runtime

Re: [yocto] [Chicken and Egg problem] Defining RDEPENDS of the package itself!

This does work: S = "${WORKDIR}/git" inherit pkgconfig cmake inherit systemd EXTRA_OECMAKE += "-DCMAKE_BUILD_TYPE=Release" INSANE_SKIP_${PN} = "ldflags" INHIBIT_PACKAGE_STRIP = "1" INHIBIT_SYSROOT_STRIP = "1" SOLIBS = ".so" FILES_SOLIBSDEV = "" do_install_*append* () { install -d

Re: [yocto] [Chicken and Egg problem] Defining RDEPENDS of the package itself!

Hello Andre, Thank you for the tips. Tried what you have suggested. I had some errors, again in do_install(), then I read .log, and fixed the paths. This is my recipe, important part of it, as of now: ___ S = "${WORKDIR}/git" inherit pkgconfig cmake inherit systemd EXTRA_OECMAKE +=