Parsing recipes: 0% | - hangs for a while
Sergey Ivanov <icegood1980@...>
Since today i encountered issue in the topic. I had this issue before when i forgot to turn on vpn (somehow parsing depends on it). But today is everything is OK and i wonder what went wrong. More precisely, i'm interested in two points:-- Kind regards, Sergey Ivanov
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Error when building eSDK for a "linux-dummy"
Andrej Valek <andrej.valek@...>
Hello Khem,
I was, that you were trying to figure you, what’s going wrong with “linux-dummy” kernel in eSDK case. Did you or somebody else find something?
I have the same problem as described here https://lists.yoctoproject.org/g/yocto/topic/78096462#51336.
Regards, Andrej
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: Problem with recipe that depends on a binary that is generated during its build
Ok I've found a solution by myself. Basically I just used the trick showed in the Technical FAQ and put a bunch of install commands in the do_install task.
Now the only problem I have is that the do_install task for target complains that needs administrative privileges (maybe I'm just doing it wrong, I'm still not that experienced with Yocto). | [100%] Built target boosttest-test-livestatus | make[1]: Leaving directory '/home/matteo/boxio/toradex/colibri-imx6ull/build-boxio-colibri-imx6ull/tmp-glibc/work/cortexa7t2hf-neon-angstrom-linux-gnueabi/icinga-core/2.12.0-r0/build' | /home/matteo/boxio/toradex/colibri-imx6ull/build-boxio-colibri-imx6ull/tmp-glibc/work/cortexa7t2hf-neon-angstrom-linux-gnueabi/icinga-core/2.12.0-r0/recipe-sysroot-native/usr/bin/cmake -E cmake_progress_start /home/matteo/boxio/toradex/colibri-imx6ull/build-boxio-colibri-imx6ull/tmp-glibc/work/cortexa7t2hf-neon-angstrom-linux-gnueabi/icinga-core/2.12.0-r0/build/CMakeFiles 0 | make -f CMakeFiles/Makefile2 preinstall | make[1]: Entering directory '/home/matteo/boxio/toradex/colibri-imx6ull/build-boxio-colibri-imx6ull/tmp-glibc/work/cortexa7t2hf-neon-angstrom-linux-gnueabi/icinga-core/2.12.0-r0/build' | make[1]: Nothing to be done for 'preinstall'. | make[1]: Leaving directory '/home/matteo/boxio/toradex/colibri-imx6ull/build-boxio-colibri-imx6ull/tmp-glibc/work/cortexa7t2hf-neon-angstrom-linux-gnueabi/icinga-core/2.12.0-r0/build' | Install the project... | /home/matteo/boxio/toradex/colibri-imx6ull/build-boxio-colibri-imx6ull/tmp-glibc/work/cortexa7t2hf-neon-angstrom-linux-gnueabi/icinga-core/2.12.0-r0/recipe-sysroot-native/usr/bin/cmake -P cmake_install.cmake | -- Install configuration: "Release" | CMake Error at cmake_install.cmake:36 (file): | file cannot create directory: /usr/share/doc/icinga2. Maybe need | administrative privileges. | | | Makefile:74: recipe for target 'install' failed | make: *** [install] Error 1 | ERROR: oe_runmake failed | WARNING: exit code 1 from a shell command. | ERROR: Function failed: do_install (log file is located at /home/matteo/boxio/toradex/colibri-imx6ull/build-boxio-colibri-imx6ull/tmp-glibc/work/cortexa7t2hf-neon-angstrom-linux-gnueabi/icinga-core/2.12.0-r0/temp/log.do_install.25788) ERROR: Task (/home/matteo/boxio/toradex/colibri-imx6ull/build-boxio-colibri-imx6ull/../layers/meta-boxio-colibri-imx6ull/recipes-extended/icinga-core/icinga-core_2.12.0.bb:do_install) failed with exit code '1' NOTE: Tasks Summary: Attempted 3457 tasks of which 3447 didn't need to be rerun and 1 failed. NOTE: Writing buildhistory The recipe that now compiles ok is attached here. Thanks Matteo Iervasi
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
M+ & H bugs with Milestone Movements WW47
Stephen Jolley
All,
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Enhancements/Bugs closed WW47!
Stephen Jolley
All,
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Current high bug count owners for Yocto Project 3.3
Stephen Jolley
All,
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Yocto Project Newcomer & Unassigned Bugs - Help Needed
Stephen Jolley
All,
The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on the triage page under the appropriate heading: https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs Also please review: https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded and how to create a bugzilla account at: https://bugzilla.yoctoproject.org/createaccount.cgi The idea is these bugs should be straight forward for a person to help work on who doesn't have deep experience with the project. If anyone can help, please take ownership of the bug and send patches! If anyone needs help/advice there are people on irc who can likely do so, or some of the more experienced contributors will likely be happy to help too.
Also, the triage team meets weekly and does its best to handle the bugs reported into the Bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 328 unassigned or newcomer bugs.
We're hoping people may be able to spare some time now and again to help out with these. Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system. There are also roughly four different "priority" classes right now, “3.2”, “3.3, "3.99" and "Future", the more pressing/urgent issues being in "3.2" and then “3.3”.
Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (sjolley.yp.pm@...) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a Bugzilla account). The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer_Bugs
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Yocto Project Status WW47'20
Stephen Jolley
Current Dev Position: YP 3.3 M1 development Next Deadline: 7th December 2020 YP 3.3 M1 build
Next Team Meetings:
Key Status/Updates:
Ways to contribute:
YP 3.3 Milestone Dates:
Planned upcoming dot releases:
Tracking Metrics:
The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at: https://wiki.yoctoproject.org/wiki/TSC
The Status reports are now stored on the wiki at: https://wiki.yoctoproject.org/wiki/Weekly_Status
[If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!]
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: How to add python application into the build.
#python
#toolchain
Nicolas Jeker
On Tue, 2020-11-24 at 04:33 -0800, vijayrakeshmunganda@... wrote:
Hi,Hi Vijay I'm new to the Yocto Project, trying to include my python applicationReading and following the section about "Writing a New Recipe" in the manual is probably a good starting point: https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#new-recipe-writing-a-new-recipe I usually look at related recipes that already exist (in your case some other python recipe) and try to start with a minimal recipe and fix build errors/missing dependencies/etc. iteratively. Thank & Regards,
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
How to add python application into the build.
#python
#toolchain
Vijay Rakesh Munganda
Hi,
I'm new to the Yocto Project, trying to include my python application into the build. Can anyone guide me how to write a bitbake recipe .bb file or any example recipe would be helpful. Thank & Regards, Vijay.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: Yocto Project Outreachy interns
Dorinda
Thank you all, I appreciate the opportunity given to me to intern with the Yocto Project. I am excited about this internship and I look forward to working with you on my project. Sincerely, Dorinda.
On Nov 24, 2020 08:47, "Nicolas Dechesne" <nicolas.dechesne@...> wrote: Dear all,
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: Python function caching question
Quentin Schulz
Hi Michael,
On Mon, Nov 23, 2020 at 04:49:30PM -0700, Michael Callahan wrote: I do not want do_compile to run again, it rebuilds the whole image.Use an anonymous python function that sets VERSION, e.g.: python __anonymous() { d.setVar('VERSION', find_version(d)) } as anonymous python functions are always executed during parsing. Then add the following to your recipe: do_compile[vardepsexclude] += "VERSION" VERSION will always be set appropriately every time the recipe is parsed but do_compile will only be rerun when a change in the task has occurred to the exception of the VERSION variable. No idea if that works as I don't use those, but that's an hint. Anyway, you probably want a behavior similar to DATETIME's. Cheers, Quentin On Sun, Nov 22, 2020 at 7:53 PM Khem Raj <raj.khem@...> wrote: -- StreamUnlimited Engineering GmbH High Tech Campus Vienna, Gutheil-Schoder-Gasse 10, 1100 Vienna, Austria Fax: +43 1 667 20 02 4401 quentin.schulz@..., www.streamunlimited.com
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: Yocto Project Outreachy interns
Meh Mbeh Ida Delphine <idadelm@...>
Thank you all so much for having us. I learned so much about embedded linux and the Yocto Project in a very short while. I can't wait to start working with you and on my project. Cheers, Ida.
On Tue, 24 Nov 2020, 8:47 am Nicolas Dechesne, <nicolas.dechesne@...> wrote: Dear all,
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: Disable systemd-timesyncd.service in image
Damien LEFEVRE
Yes SYSTEMD_AUTO_ENABLE_${PN} doesn't apply to systemd recipe core services as they are not installed as separate packages. The default enable/disable service are defined in https://github.com/systemd/systemd/blob/master/presets/90-systemd.preset So do_configure_append() { sed -i -e "s/enable systemd-timesyncd.service/disable systemd-timesyncd.service/g" ${S}/presets/90-systemd.preset } does the trick Cheers, -Damien
On Mon, Nov 23, 2020 at 10:42 PM Konrad Weihmann <kweihmann@...> wrote: The service is deployed with standard systemd package, which doesn't
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Yocto Project Outreachy interns
Dear all,
We are very excited to be part of the Outreachy program again for the December round this year, let me congratulate Ida and Dorinda for being accepted as interns for the next three months. I want to give a warm thank you to our mentors as well, Paul, Ross, Tim. Without mentors there isn't much we can do, so this is very much appreciated. A big thank you to Microsoft and Arm who are sponsoring the internships. Ida and Dorinda will engage on the following topics: == Enhance Yocto Project License Tracing The Yocto Project build system is typically used to build customised Linux images from source for embedded applications. Along with the image, a manifest of packages and their corresponding licenses is prepared, however the accuracy of the license information in the manifest is dependent on the accuracy of the metadata we have for each package (i.e. what is in the recipe file). As part of the build, we have an internal mapping from output files to source files which is currently used to prepare source packages to aid in debugging, however with the increasing presence of SPDX headers in source files it could also be used to allow tracing the license of sources used in building a package/image to help improve our metadata and future license manifests. == Add support for elfutils debug info server" The Yocto Project build system is typically used to build customised Linux images from source for embedded applications. debuginfod (part of elfutils 0.178 onwards) is a way to share debuginfo files, which provide debugging symbols for gdb to enable it to debug a running program on a target device. Users of the Yocto Project would benefit from integrating support for debuginfod such that binaries in an image produced by the Yocto Project build system could be debugged more easily. Ida and Dorinda, welcome into our open source community, you can count on everyone's support during your internship! cheers nico
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: Python function caching question
Richard Purdie
On Sun, 2020-11-22 at 19:16 -0700, Michael Callahan wrote:
I am having trouble with sstate caching of my os-release.bbappend andIf you set BB_DONT_CACHE = "1" in the recipe, it will force the recipe to reparse each time. That should cause it to rerun find_version and then change hash when the value changes. Its how SRCREV = "${AUTOREV}" works behind the scenes. Cheers, Richard
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: Python function caching question
Michael Callahan <coder.callahan@...>
I do not want do_compile to run again, it rebuilds the whole image.
toggle quoted messageShow quoted text
What is the best way to always run find_version?
On Sun, Nov 22, 2020 at 7:53 PM Khem Raj <raj.khem@...> wrote:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: OE/YP equivalent to 'mtree'?
On 2020-11-23 2:26 p.m., Robert P. J. Day wrote:
colleague wants to know if there is something availableIt don't see anything in the layer index: https://layers.openembedded.org/layerindex/branch/master/recipes/?q=mtree but the source has a configure file: (Ubuntu: apt-get source mtree-netbsd) so they should write a recipe and send it to meta-oe. ../Randy rday -- # Randy MacLeod # Wind River Linux
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: Disable systemd-timesyncd.service in image
Konrad Weihmann <kweihmann@...>
The service is deployed with standard systemd package, which doesn't have that set as far as I see it (no SYSTEMD_AUTO_ENABLE_${PN} in the latest recipe revision)
toggle quoted messageShow quoted text
I think, after browsing through the code of systemd - this "autostart" behavior comes from [1]. So I would say you can disable it with a drop-in file at /etc/systemd/system/systemd-timesyncd.service.d/disable.conf [Install] WantedBy= which also would be charming in a way that it isn't that invasive in the build system [1] https://github.com/systemd/systemd/blob/5b639090d0b4a49d77ba58bebe180b2a6f8da322/units/systemd-timesyncd.service.in#L55 haven't tested it though, but you might wanna give that a shot, if Aaron's approach doesn't work.
On 23.11.20 21:21, Joel A Cohen wrote:
I think you need to set SYSTEMD_AUTO_ENABLE = “disable” (actually any value other than “enable”) in your bbappend.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: Disable systemd-timesyncd.service in image
Joel A Cohen
I think you need to set SYSTEMD_AUTO_ENABLE = “disable” (actually any value other than “enable”) in your bbappend. (It looks like SYSTEMD_AUTO_ENABLE_${PN} is intended to work too, but I can’t verify it at the moment and reading over systemd.bbclass I’m not sure if it works or not) —Aaron
On Mon, Nov 23, 2020 at 11:51 AM Damien LEFEVRE <lefevre.da@...> wrote:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|