eliranl@...
Thanks Matt!! This solved it.
And yes, the branch is thud-l4t-r32.3.1.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
WIC cp is not copying files to ext4 partition
#yocto
mail2uvijay@...
Hi Team, Able to create image for using Yocto. After creating the image, I am trying to copy one file using 'wic cp' to 'extt4' partition. while copying i am not getting any error, after flashing the image on board copied file was not present. Is there any other ways to copy a file to ext4 partition. Where as in case vfat partition i could able to copy the file successfully. Regards, Vijay
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
M+ & H bugs with Milestone Movements WW37
Stephen Jolley
All,
YP M+ or high bugs which moved to a new milestone in WW37 are listed below:
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Enhancements/Bugs closed WW37!
Stephen Jolley
All,
The below were the owners of enhancements or bugs closed during the last week!
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Current Autobuilder Intermittent bugs by the WW created or closed.
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.2
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 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 338 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@...
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: Patching file contained in downloaded recipe
On Mon, Sep 14, 2020 at 3:05 PM Greg Wilson-Lindberg <GWilson@...> wrote:
In that case, your best bet is to probably write a do_*_append() function into the bbappend recipe so you can jump in after one of the build steps and apply your patch during the appropriate stage. Refer to section 28.1 of the Mega Manual for all of the build tasks, and pick one that seems sensible. For example, you can write a do_install_append() function, and then prepend ${B} to the path that the service file typically shows up at to access it. From there, it is a simple matter of using typical commands to apply whatever patch you want. I have no doubt that other, more experienced people on the Yocto project, may suggest a better target than do_install, so listen to them if any should jump in and offer sensible correction to what I am saying.
Given the example above, you would simply use ${B}/lib/systemd/system/file.service and use garden variety command line tools to apply the patch.
No worries. I used to use mutt and pine, which were really good at inline posting. Alas, I have moved on to gmail, which is not so good, and comes into conflict in places such as this. We make-do of course... ..Ch:W.. -- "Perfection must be reached by degrees; she requires the slow hand of time." - Voltaire
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: Patching file contained in downloaded recipe
Greg Wilson-Lindberg
Hi Chuck,
From: Chuck Wolber <chuckwolber@...>
Sent: Monday, September 14, 2020 12:48 PM To: Greg Wilson-Lindberg <GWilson@...> Cc: Yocto list discussion <yocto@...> Subject: Re: [yocto] Patching file contained in downloaded recipe
On Mon, Sep 14, 2020 at 10:50 AM Greg Wilson-Lindberg <gwilson@...> wrote:
Are you patching an existing upstream recipe? Or your own recipe? In the former case, you would use a .bbappend recipe.
<reply> I am patching a recipe that is included with the Yocto system that I download. The .system file that I need to modify is in one of the file directories that are part of the recipe.
I have a .bbappend recipe that is being picked up, but because the file that I want to patch is part of the recipe and not part of what a recipe would download if it were building something from source, the patch system is not finding it.
<reply/>
In either case, it all depends on how the service file is generated. If it is part of the source code, then you just create a patch against the source tree and reference that patch in a recipe as a SRC_URI_append. If you generate it as part of a build, then you would either patch the build product (less desirable), or patch the code that generates the service file (more desirable).
<reply> Part of my question was, could I use the PATCHDIR option to specify the /lib/systemd/system/file.service file to get the patch to run against the ‘copied’ version of the file?
Sorry for the weird “<reply>…<reply\>” blocks, I’m stuck with Outlook for email and I can’t figure out how to get it to indent the email I’m replying to and let me comment in line without indenting my replies also.
Regards, Greg <reply\>
..Ch:W..
-- "Perfection must be reached by degrees; she requires the slow hand of time." - Voltaire
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
On Mon, Sep 14, 2020 at 11:31 AM eliranl via lists.yoctoproject.org
<eliranl=amazon.com@...> wrote: Which of the meta-tegra branches is it? thud-l4t-r32.3.1? It has an eth0 device which is configured (with a config file in /etc/systemd/network) with a static IP address. The Xavier's Ethernet port is connected directly to another Ubuntu PC, which is also on the same subnet with a different static IP address.[...] The following is the non-working systemd network device configuration file:There was an issue with NVIDIA's eqos driver in older BSPs. I know it affected the TX2, with the exact same symptoms It could affect Xavier modules as well. The workaround is to disable LLDP on by adding LLDP=no to the [Network] section for the interface. See https://github.com/OE4T/meta-tegra/issues/146 The workaround didn't get back-ported to the thud-l4t-r32.3.1 branch. [...] Please accept my apologies if this isn't the right forum, i wasn't sure where to sent it to.Since this is BSP-related, opening an issue at https://github.com/OE4T/meta-tegra/issues might work better. Regards -Matt
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: Patching file contained in downloaded recipe
On Mon, Sep 14, 2020 at 10:50 AM Greg Wilson-Lindberg <gwilson@...> wrote:
Are you patching an existing upstream recipe? Or your own recipe? In the former case, you would use a .bbappend recipe. In either case, it all depends on how the service file is generated. If it is part of the source code, then you just create a patch against the source tree and reference that patch in a recipe as a SRC_URI_append. If you generate it as part of a build, then you would either patch the build product (less desirable), or patch the code that generates the service file (more desirable). ..Ch:W.. "Perfection must be reached by degrees; she requires the slow hand of time." - Voltaire
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
eliranl@...
Hi,
(since this is a long post, i divided it to sections) TL;DR I have a networking issue in my Yocto dist; Somehow, my ethernet device won't work with systemd-networkd, but will work with /etc/network/interfaces. It has an eth0 device which is configured (with a config file in /etc/systemd/network) with a static IP address. The Xavier's Ethernet port is connected directly to another Ubuntu PC, which is also on the same subnet with a different static IP address. I cannot get the Xavier's network device to work with systemd-networkd; Once the device boots into the initrd, it appears as if the network device is configured correctly:
However, when I ping the Ubuntu machine on the other end of the cable, there's no response.
20:00:55.280337 ARP, Request who-has 192.168.13.10 tell 192.168.13.6, length 46
(192.168.13.0 is the address of the machine i tried to ping. as you can see its MAC address is not updated).
Using /etc/network/interface does work If i 'move' to using /etc/network/interfaces by doing: 1. Running: systemctl stop systemd-networkd.{socket,service} 2. Write an equivalent configuration in /etc/network/interfaces 3. Restart eth0: ifconfig eth0 down; ifconfig eth0 up Then, all of a sudden the ping works.
And none of it seemed to work.
---- Does anyone have an idea on how to debug this? Please accept my apologies if this isn't the right forum, i wasn't sure where to sent it to. Thanks, Eliran
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Patching file contained in downloaded recipe
Greg Wilson-Lindberg
I have a recipe that has a .service file in one of its files directories that I need to patch.
I haven’t been able to figure out how to specify the directory of the file that needs to be patched. I can’t seem to get the patch to apply to the files directory, do I need to specify the /lib/systemd/system directory into the PATCHDIR option or is there another way that would work better?
Regards Greg
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
[psplash] image format.
Mauro Ziliani
Hi all.
I'm trying to display a splash screen over a 800x600 display, on Geode LX 800 platform (Geode LX FB or Vesa). I make the image with Gimp and saved in 4 version to try. 800x600 in png 16bit rgb, png 16bit rgba, png 8bit rgb, png 8bit rgba The image is not aligned with the display. 1. To "center" the splash in the screen I need to create a 800x700 image 2. this is the result on the display https://drive.google.com/file/d/1OHbUr-WxR_weU6JilhFcUO64onb7F3-f/view?usp=sharing Any idea? Best regards, MZ
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: #yocto Problem compiling binutils-2.32.0-r0 on zeus
#yocto
srijan.nandi@...
The issue got resolved after running bitbake -c cleanall binutils. After which it build successfully.
-=Srijan Nandi
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#yocto Problem compiling binutils-2.32.0-r0 on zeus
#yocto
srijan.nandi@...
I am trying to compile binutils-2.32.0-r0 on zeus. I am getting the following error:
DEBUG: Executing python function do_unpack
DEBUG: Executing python function base_do_unpack
DEBUG: Running 'export PSEUDO_DISABLED=1; unset _PYTHON_SYSCONFIGDATA_NAME; export PATH="/opt/grays-poky/build-grays/tmp/sysroots-uninative/x86_64-linux/usr/bin:/opt/grays-poky/build-grays/tmp/work/core2-64-poky-linux/binutils/2.32.0-r0/recipe-sysroot-native/usr/bin/chrpath-native:/opt/grays-poky/scripts:/opt/grays-poky/build-grays/tmp/work/core2-64-poky-linux/binutils/2.32.0-r0/recipe-sysroot-native/usr/bin/x86_64-poky-linux:/opt/grays-poky/build-grays/tmp/work/core2-64-poky-linux/binutils/2.32.0-r0/recipe-sysroot/usr/bin/crossscripts:/opt/grays-poky/build-grays/tmp/work/core2-64-poky-linux/binutils/2.32.0-r0/recipe-sysroot-native/usr/sbin:/opt/grays-poky/build-grays/tmp/work/core2-64-poky-linux/binutils/2.32.0-r0/recipe-sysroot-native/usr/bin:/opt/grays-poky/build-grays/tmp/work/core2-64-poky-linux/binutils/2.32.0-r0/recipe-sysroot-native/sbin:/opt/grays-poky/build-grays/tmp/work/core2-64-poky-linux/binutils/2.32.0-r0/recipe-sysroot-native/bin:/opt/grays-poky/bitbake/bin:/opt/grays-poky/build-grays/tmp/hosttools"; export HOME="/home/srijan.nandi"; git -c core.fsyncobjectfiles=0 branch --contains b8c1f608db9ef3edd483d21a921d1fbedc71df6f --list binutils-2_32-branch 2> /dev/null | wc -l' in /opt/grays-poky/build-grays/downloads/git2/sourceware.org.git.binutils-gdb.git
DEBUG: Running export PSEUDO_DISABLED=1; unset _PYTHON_SYSCONFIGDATA_NAME; export PATH="/opt/grays-poky/build-grays/tmp/sysroots-uninative/x86_64-linux/usr/bin:/opt/grays-poky/build-grays/tmp/work/core2-64-poky-linux/binutils/2.32.0-r0/recipe-sysroot-native/usr/bin/chrpath-native:/opt/grays-poky/scripts:/opt/grays-poky/build-grays/tmp/work/core2-64-poky-linux/binutils/2.32.0-r0/recipe-sysroot-native/usr/bin/x86_64-poky-linux:/opt/grays-poky/build-grays/tmp/work/core2-64-poky-linux/binutils/2.32.0-r0/recipe-sysroot/usr/bin/crossscripts:/opt/grays-poky/build-grays/tmp/work/core2-64-poky-linux/binutils/2.32.0-r0/recipe-sysroot-native/usr/sbin:/opt/grays-poky/build-grays/tmp/work/core2-64-poky-linux/binutils/2.32.0-r0/recipe-sysroot-native/usr/bin:/opt/grays-poky/build-grays/tmp/work/core2-64-poky-linux/binutils/2.32.0-r0/recipe-sysroot-native/sbin:/opt/grays-poky/build-grays/tmp/work/core2-64-poky-linux/binutils/2.32.0-r0/recipe-sysroot-native/bin:/opt/grays-poky/bitbake/bin:/opt/grays-poky/build-grays/tmp/hosttools"; export HOME="/home/srijan.nandi"; git -c core.fsyncobjectfiles=0 clone -s -n /opt/grays-poky/build-grays/downloads/git2/sourceware.org.git.binutils-gdb.git/ /opt/grays-poky/build-grays/tmp/work/core2-64-poky-linux/binutils/2.32.0-r0/git/
ERROR: Fetcher failure: Fetch command export PSEUDO_DISABLED=1; unset _PYTHON_SYSCONFIGDATA_NAME; export PATH="/opt/grays-poky/build-grays/tmp/sysroots-uninative/x86_64-linux/usr/bin:/opt/grays-poky/build-grays/tmp/work/core2-64-poky-linux/binutils/2.32.0-r0/recipe-sysroot-native/usr/bin/chrpath-native:/opt/grays-poky/scripts:/opt/grays-poky/build-grays/tmp/work/core2-64-poky-linux/binutils/2.32.0-r0/recipe-sysroot-native/usr/bin/x86_64-poky-linux:/opt/grays-poky/build-grays/tmp/work/core2-64-poky-linux/binutils/2.32.0-r0/recipe-sysroot/usr/bin/crossscripts:/opt/grays-poky/build-grays/tmp/work/core2-64-poky-linux/binutils/2.32.0-r0/recipe-sysroot-native/usr/sbin:/opt/grays-poky/build-grays/tmp/work/core2-64-poky-linux/binutils/2.32.0-r0/recipe-sysroot-native/usr/bin:/opt/grays-poky/build-grays/tmp/work/core2-64-poky-linux/binutils/2.32.0-r0/recipe-sysroot-native/sbin:/opt/grays-poky/build-grays/tmp/work/core2-64-poky-linux/binutils/2.32.0-r0/recipe-sysroot-native/bin:/opt/grays-poky/bitbake/bin:/opt/grays-poky/build-grays/tmp/hosttools"; export HOME="/home/srijan.nandi"; git -c core.fsyncobjectfiles=0 clone -s -n /opt/grays-poky/build-grays/downloads/git2/sourceware.org.git.binutils-gdb.git/ /opt/grays-poky/build-grays/tmp/work/core2-64-poky-linux/binutils/2.32.0-r0/git/ failed with exit code 128, output:
fatal: repository '/opt/grays-poky/build-grays/downloads/git2/sourceware.org.git.binutils-gdb.git/' does not exist
DEBUG: Python function base_do_unpack finished
DEBUG: Python function do_unpack finished
Now I checked and saw that the said directory (/opt/grays-poky/build-grays/downloads/git2/sourceware.org.git.binutils-gdb.git/) does exist. I even tried to change the permission to 777, but still the same issue. Any help will be greatly appreciated.
Thanks and Regards, -=Srijan Nandi
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Tuning 'cortexa53-crypto' has no defined features, and cannot be used.
Hello,
I am trying to get an older meta-layer (meta-maaxboard) that was developed for Sumo to work with Zeus. When I try to build “bitbake core-image-minimal” then the sanity checker gives the following error before aborting: Error, the PACKAGE_ARCHS variable (all any noarch ${PACKAGE_EXTRA_ARCHS_tune-cortexa53-crypto} maaxboard_ddr4_2g_sdcard) for DEFAULTTUNE (cortexa53-crypto) does not contain TUNE_PKGARCH (${@bb.utils.contains('TUNE_FEATURES', 'aarch64', 'aarch64', '${ARMPKGARCH_tune-cortexa53-crypto}' ,d)}).Toolchain tunings invalid: Tuning 'cortexa53-crypto' has no defined features, and cannot be used. I don’t understand what the error message actually means to know how to go about resolving it. Can anyone point me in the right direction? -Andy.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: [meta-security][master][dunfell][PATCH] clamav: update SO_VER to 9.0.4
merged to both.
toggle quoted messageShow quoted text
thanks
On 9/10/20 7:11 AM, Charlie Davies wrote:
Signed-off-by: Charlie Davies <charles.davies@...>
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: [meta-security][dunfell][PATCH] clamav: add INSTALL_CLAMAV_CVD flag to do_install
merged
toggle quoted messageShow quoted text
On 9/10/20 6:53 AM, Charlie Davies wrote:
Recipe provides INSTALL_CLAMAV_CVD flag to bypass clamav
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: [meta-security][PATCH] ibmtpm2tss: add recipe
merged
toggle quoted messageShow quoted text
thanks
On 9/11/20 12:37 AM, Jens Rehsack wrote:
From: Jens Rehsack <sno@...>
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|